Pick your stack, get a .dockerignore that keeps secrets, .git history, and build junk out of your image — and out of your build context, which speeds up every build. Nothing is ever uploaded.
Generated .dockerignore
How it works
Each checkbox maps to a small array of glob patterns — checking Node.js adds node_modules/ and dist/, checking "secrets" adds .env and *.pem — and the generator just concatenates the checked arrays plus your custom lines into one file, with no network request involved.
FAQ
Why does excluding files with .dockerignore actually speed up builds?
Docker sends your entire build context — every file in the directory that isn't excluded — to the build process before the first instruction even runs. Ignoring node_modules/, .git/, or other large, unneeded folders shrinks that upload, which is separate from and in addition to any caching benefit.
Does excluding .env in .dockerignore stop it from ending up in my image?
Only if your Dockerfile relies on a broad COPY like "COPY . ." — .dockerignore prevents matched files from being sent in the build context at all, so a COPY instruction can't pick them up. It won't undo an explicit "COPY .env .env" line, which bypasses the ignore file entirely.
Free, unlimited, no account. If this saved you a paid tool, a small thanks is appreciated.