I've accumulated Bash configuration over time and recently organized it into a small dotfiles project. It mainly contains my `.bashrc`, `.inputrc`, `.bash_profile`, a modular `.bashrc.d/` directory, and a small installation script. The setup can be deployed with either Ansible or a standalone shell installer. I'd appreciate feedback from people who maintain their own dotfiles, especially regarding organization, questionable practices, portability, deployment-focused setups, and ways to improve the configuration.
3 Answers
A useful addition is keeping aliases in their own file, such as `.bash_aliases`, and sourcing it from `.bashrc`. You can also create a helper command that writes the current alias list into that file, which makes updating aliases quick. The same general structure works well for other shells too—separate aliases, functions, exports, key bindings, history settings, and plugins into focused files.
The setup looks clean and intentionally minimal. That’s a good fit for deployments, where a small predictable configuration is often better than a heavily customized interactive shell. If you want more interactive conveniences, you could keep those in optional modules rather than enabling everything by default.
If the configuration enables `globstar`, check whether `extglob` would also be useful for the patterns used elsewhere in the setup. `direxpand` may be worth considering too, depending on how you want directory names to expand during interactive completion. These options are shell-version and workflow dependent, so documenting why they’re enabled would help portability.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures