Chmod calculator
Toggle Unix permission bits and inspect exact octal, symbolic and special-bit representations.
← All tools
DevOps tools
Inspect infrastructure configuration before it reaches a server.
Cron expression builder
Build a five-field UTC cron expression with presets and an interactive map of matching values.
Cron next-run preview
See the next UTC dates for a numeric five-field cron schedule with a bounded, explicit search window.
CSP policy builder
Draft a Content Security Policy header with editable source lists and an explicit fallback preview.
Docker Compose validator
Inspect a supported Compose subset for service types, dependencies and structural issues entirely locally.
Docker run to Compose
Convert supported static docker run arguments into Compose YAML without executing any commands.
Gitignore builder
Combine project presets and custom rules with a local path-matching preview and downloadable ignore content.
Nginx config formatter
Format supported Nginx configuration tokens while preserving quoted content and checking balanced structure.
Build and preview cron schedules, compose Content Security Policies, check Docker Compose and Nginx files, format configuration, and generate gitignore and Docker conversions. Every tool reports the subset it supports.
No command is executed, no container is started, and no server is contacted.
Check before you deploy
The DevOps tools catch configuration mistakes while they are still cheap to fix. Build a cron expression and preview its next run times before a job fires at the wrong moment. Draft a Content Security Policy in report-only mode before enforcing it. Validate a Docker Compose file's structure and dependencies, or convert a long docker run command into a Compose service. Format an Nginx configuration so nested blocks are easy to review, and calculate chmod modes from permission checkboxes.
The gitignore builder combines presets for common stacks with your own rules and previews which paths would be ignored, including tricky negations such as keeping .env.example while ignoring .env.
What these tools do not do
Nothing is executed and nothing is contacted: no command runs, no container starts, no server is reloaded. That keeps pasted configuration private, including hostnames, paths, and secrets in environment variables. It also means the tools check structure, not reality. They cannot know whether an image exists, a port is free, or a directive is supported by your Nginx build.
Use them as a first pass, then confirm with the real tooling before shipping: nginx -t, docker compose config, and a dry run of your scheduler. Each tool states the subset it supports and reports anything outside it instead of approving it silently.