DevOps Tools
Operations work is full of small formats that are easy to get subtly wrong: a cron field off by one, a duplicated variable in an .env file, or a Dockerfile that rebuilds every layer on each commit.
7 free tools
DevOps Tools
7 tools shown
Cron Generator
Build and explain cron schedules.
Env Formatter
Tidy .env files and convert formats.
JSON to .env
Convert JSON config into .env variables.
Dockerfile Linter
Check Dockerfiles for common issues.
Git Command Helper
Find the right Git command for a task.
Docker Command Helper
Find the right Docker command for a task.
YAML Validator
Validate YAML syntax and structure.
About these devops tools
The DevOps tools here make those formats explicit. Build a cron schedule and see its next run times, normalise environment files, run a Dockerfile through a set of documented best-practice rules, validate YAML manifests, and look up the Git command for the situation you are in.
Why use them
Plain-English schedules
Every cron expression is translated into a sentence and a list of upcoming run times in your chosen time zone.
Documented lint rules
The Dockerfile linter explains each rule it checks, so you can decide which findings matter for your image.
Secrets stay local
.env files often contain credentials. The formatter runs entirely in your browser and never transmits the file.
Frequently asked questions
Which cron syntax is supported?
Standard five-field cron (minute, hour, day of month, month, day of week) as used by Linux crontab, Kubernetes CronJobs and GitHub Actions, including ranges, lists, steps and month or weekday names. An optional sixth seconds field is also accepted.
Does the YAML validator check Kubernetes schemas?
It validates YAML syntax and reports duplicate keys, indentation errors and multi-document structure. It does not validate resources against Kubernetes API schemas.