Open the generator

Free. No sign-up. Nothing you enter is stored on the server.

Docker & CI/CD file generator

Pick a stack and get a Dockerfile, docker-compose, CI/CD pipeline and deployment config for your new project, ready to copy or download.

Open the generatorSee sample output

12 stacks · 7 CI providers · 7 deploy options

Dockerfile
# syntax=docker/dockerfile:1
FROM node:24-alpine AS base
WORKDIR /app

FROM base AS deps
COPY package.json package-lock.json* ./
RUN npm ci --omit=dev && mkdir -p node_modules

FROM base AS build
COPY package.json package-lock.json* ./
RUN npm ci
COPY . .
RUN npm run build
RUN rm -rf node_modules && mkdir -p .next/cache && mv .next /next

FROM base AS runtime
ENV NODE_ENV=production PORT=3000
# The code and its dependencies belong to root: the app can read them, not rewrite them.
COPY --from=build /app ./
COPY --from=deps /app/node_modules ./node_modules
# Next.js writes its cache under .next: the only folder of the app the node user can write (it is empty for other apps).
COPY --from=build --chown=1000:1000 /next ./.next
USER 1000:1000
EXPOSE 3000
CMD ["npm","start"]
Generated by Dockcrate for a Node.js project with npm.

Everything a new project needs

One set of choices, every file consistent with the others.

  • Dockerfile and .dockerignore

    Multi-stage builds for twelve stacks, on an alpine or slim base, with healthcheck, OS packages and build arguments.

    Dockerfile generator guide

  • Docker Compose

    Postgres, MySQL, MariaDB, MongoDB, Redis, RabbitMQ and more, health-gated, with a compose override per environment.

    Docker Compose generator guide

  • CI/CD for seven providers

    Tests, image build, registry push and deploy in each provider's own syntax, with the triggers you switch on.

    CI/CD pipeline generator guide

  • Safer pipelines

    GitHub actions pinned to commit SHAs and limited token permissions, plus optional Trivy, SBOM, cosign, Hadolint and CodeQL.

    GitHub Actions workflow generator guide

  • Deployment config

    Kubernetes manifests, an ECS task definition, fly.toml, or an SSH deploy with compose. Each target brings the files it needs.

  • Several services, one repo

    A Dockerfile per service folder, one compose file, one pipeline, and optional runs only for the services that changed.

How it works

  1. Pick your stack

    Choose a stack, runtime and the options you need. Nothing is read from an existing project.

  2. Preview every file

    See the Dockerfile, compose file, pipeline and deploy config live. Edit or switch off any block.

  3. Take the files

    Copy them or download a zip. The CLI can also write them straight into a project folder.

Stacks, providers and targets

Stacks

  • Node.js
  • React
  • Vue
  • Angular
  • FastAPI
  • Django
  • .NET
  • Java
  • Go
  • Rust
  • PHP
  • Ruby

CI providers

  • GitHub Actions
  • GitLab CI
  • Gitea / Forgejo
  • Jenkins
  • Bitbucket Pipelines
  • Azure DevOps
  • CircleCI

Deploy to

  • Registry only
  • SSH + Compose
  • Kubernetes
  • Cloud Run
  • AWS ECS
  • Azure Web App
  • Fly.io

Guides

  • Dockerfile generator

    Pick a stack and a few options and get a Dockerfile and a matching .dockerignore, ready to copy or download. Nothing is read from an existing project: you describe the new one.

  • Docker Compose generator

    Build a docker-compose.yml for your app and the services it needs. Databases come with health checks, volumes and connection URLs already wired in.

  • GitHub Actions workflow generator

    Get a ci.yml that tests your code, builds the image and pushes it to a registry, with the security options you pick. You choose the triggers, nothing is fixed for you.

  • CI/CD pipeline generator

    Choose your CI provider and get a pipeline that tests the project, builds the Docker image, pushes it to a registry and optionally deploys it.

The developer and related tools

Questions

Does it read my existing project?

No. You choose the stack and the options and the files are generated from that, so it works for a project that does not exist yet.

How accurate are the files?

A very good first draft, not a guarantee. Dockerfiles and compose files are usually right for standard projects. Pipelines are checked as text but not run on your CI, and deploy files are templates never run against a real account, so expect small edits.

Is it free?

Yes. There is no sign-up. You can use the website, or run the same generator as a command line tool or a local web UI.

Which CI providers and deploy targets are supported?

GitHub Actions, GitLab CI, Gitea and Forgejo Actions, Jenkins, Bitbucket Pipelines, Azure DevOps and CircleCI; and Kubernetes, SSH, Cloud Run, ECS, Azure and Fly, or a plain registry push.

Open the generator