Home / Configs / Developer tools

Developer tools

Git, .gitignore, SSH, editors, GitHub Actions, shell shortcuts and environment files.

These generators write the small files that every project needs: Git and SSH settings, .gitignore, editor settings, environment files, package.json, tsconfig.json, GitHub Actions workflows and shell shortcuts. They are short, but one wrong line can cost an hour.

Which one should I pick?

Starting a new project

Create the .gitignore and .editorconfig first, then package.json and tsconfig.json, so the first commit is already clean and consistent.

Keeping secrets safe

The .env page builds an environment file and reminds you to keep it out of Git. Add it to .gitignore before the first commit, since deleting a pushed secret later is not enough.

Working with GitHub

The SSH config pages cover several accounts on one computer, and the Actions page writes a workflow that installs, tests and builds a Node project on every push.

Speeding up the terminal

The alias and shell pages turn long commands you retype into short ones.

All developer tools generators

• SSH config fileGive servers short names and choose the right key for each.
• .gitconfig setupSet your name, email, default branch and shortcuts once.
• .env file exampleCreate a .env file for your app: port, database address and a secret key.
• VS Code settings.jsonSet font, tab size, format on save and theme in your VS Code settings.
• .bashrc and .zshrc aliasesAdd handy shortcuts and settings to your terminal.
• .gitignore fileTick your languages and tools to get a .gitignore that keeps build files and secrets out of Git.
• .editorconfig fileMake every editor on your team use the same indent, line endings and encoding.
• GitHub Actions workflow for Node.jsA ci.yml file that installs, lints, builds and tests your Node.js project on GitHub.
• package.json fileCreate a package.json with the right name, version, module type, scripts and Node version.
• tsconfig.json fileCreate a tsconfig.json for a Node or browser TypeScript project, with strict mode, target and output folder.
• SSH config for multiple GitHub accountsUse two or three GitHub accounts on one computer with separate SSH keys and host names.

Before you use any config

• Commit the generated file, review the diff, and only then change it by hand.
• Version numbers (Node, Python, actions) move on. Check the one you pick against the project’s own support page.
• Keep a .env.example with fake values so a teammate knows which variables the app expects.

The values you type stay in your browser. Nothing is sent to this site. Missing a file? Ask for it.