Set Up DevOps Configuration Files

Setting up a new project's DevOps configuration involves creating and validating several interconnected files: a Dockerfile for containerisation, a Docker Compose file for local development, YAML configuration for CI pipelines, and a .gitignore to keep the repository clean. Errors in any of these files can cause cryptic failures that are hard to debug without the right tooling. devtoolkit.sh provides a complete set of tools for this workflow. Generate a production-ready Dockerfile for your language and framework, validate your Docker Compose and CI YAML for syntax errors, and create a comprehensive .gitignore in one place. All tools run in your browser with no account required, making them accessible from any machine in your development workflow.

FAQ

How do I validate a Docker Compose YAML file?
Paste the contents of your docker-compose.yml into the YAML Formatter. It validates the YAML syntax and reports any indentation or structural errors before you run docker compose up.
What should a production Dockerfile include?
A production Dockerfile should use multi-stage builds to minimise image size, run as a non-root user, use a minimal base image like alpine or distroless, and pin the base image version for reproducibility.
Which files should always be in .gitignore?
Dependency directories (node_modules, vendor), build output (dist, build, target), environment files (.env), IDE configuration (.idea, .vscode), and OS files (.DS_Store, Thumbs.db) should always be gitignored.