DevToolsmith

Browser-based tools

DevOps Tools

Check a schedule, inspect Unix permissions or turn a Docker command into Compose configuration. Prepare and review changes in your browser before applying them to a real system.

Containers

CI and Git

Schedules and permissions

Common DevOps workflows

These tools calculate and translate; they do not connect to servers, change permissions or run containers. Generated commands still need review for your operating system and deployment. A syntactically valid schedule or container configuration can have consequences that depend on its runtime environment.

Review a deployment configuration

Check a Compose document against the official schema and Kubernetes manifests against versioned schemas, then validate the final merged configuration with the native tools.

Check repository ignore rules

Generate a starting rule set, then test representative paths and negated exceptions. Verify the final result with Git in your repository, including nested rules and tracked files.

Review a scheduled job

Build or explain a cron expression and inspect upcoming run times in the chosen time zone. Pay attention to day-of-month and day-of-week semantics, daylight-saving changes, and whether the destination accepts five or six fields.

Set file permissions

Translate between octal and symbolic modes and see what owner, group and others can do. Permission effects differ between files and directories, and special bits such as setuid need care.

Move a local command into configuration

Convert a Docker run command into Compose YAML, transform environment variables and select gitignore templates. Check paths, secrets and unsupported flags before committing the generated files.

Read the actual schedule, not only its description

A step such as */45 in the minute field runs at :00 and :45 each hour, not at evenly spaced 45-minute intervals. Inspect next-run times and test with the scheduler that will run the job. Different cron implementations also differ in supported extensions.

Generated configuration does not validate a deployment

Compose conversion cannot determine whether an image exists, a mount path is correct or a published port should be exposed. Likewise, gitignore rules do not remove files already tracked by Git. Review output with the native tools before applying it.

Frequently asked questions

Will these tools execute commands on my server?

No. They run calculations and conversions inside your browser. Copying and running generated commands is a separate action that you perform in your own environment.

Does adding a rule to .gitignore remove a committed file?

No. Git keeps tracking files that are already committed. Remove them from the index with git rm --cached, then commit, and rotate any secret that was pushed.

Tools process your input on this device. Read the privacy policy, or save the tool library for offline use.