Demo mode, read-only. Request a demo →

Readiness report · Sample app (fictional)

BrightPath Tutoring

Drafts of the files this app needs to run as a container on AWS, written for its stack (Node.js / Express). The fix for each finding is on the Findings tab.

Dockerfile AI-generated

Packages the app as one container: an official slim base image with security updates applied, an unprivileged user, and the app listening on 0.0.0.0.

FROM --platform=linux/amd64 public.ecr.aws/docker/library/node:22-slim

ENV NODE_ENV=production \
    PORT=8080

RUN apt-get update && apt-get upgrade -y && rm -rf /var/lib/apt/lists/*

WORKDIR /app
COPY package*.json ./
RUN if [ -f package-lock.json ]; then npm ci --omit=dev; else npm install --omit=dev; fi

COPY --chown=node:node . .
# Temporary support for the existing file store; migrate bookings before launch.
RUN mkdir -p /app/data && chown node:node /app/data
USER node

# server.js reads PORT; its listen call accepts connections on all interfaces.
EXPOSE 8080
CMD ["node", "server.js"]

.env.example AI-generated

Lists every setting the app reads, marked secret or setting, required or optional. Secrets go in AWS Secrets Manager, never in the code.

# The current code reads only PORT. Set environment values through your local
# runner or AWS deployment; the app does not load .env files itself.
# NODE_ENV is also set by the Dockerfile for the Node/Express runtime.
# setting, optional
PORT=8080
# setting, optional
NODE_ENV=production

# Required after implementing AUTH-01: change server.js to read this salted
# hash and verify submitted passwords. It has no effect in the current code.
# Store it in AWS Secrets Manager and inject it at deployment.
# secret, required
ADMIN_PASSWORD_HASH=

.dockerignore AI-generated

Keeps secrets, Git history and generated folders out of the container image.

.env
.env.*
!.env.example
.git
.gitignore
node_modules
__pycache__
.venv
*.log
logs/
npm-debug.log*
.DS_Store
coverage/

health route (Express) AI-generated

A /health address that answers 200, so the load balancer can tell the app is alive.

// Add in server.js before app.listen(...).
app.get('/health', (req, res) => {
  res.status(200).json({ status: 'ok' });
});