Hello friends,

Today, we’re diving into the world of dotfiles.

If you’ve ever customized your terminal, text editor, or shell, you’ve likely encountered the concept of managed dotfiles. Let’s explore why managing these configuration files is essential, how to handle them locally with stow and symlinks, and how to sync them remotely to a remote dedicated machine we create using Coder.

What Are Dotfiles?

Dotfiles are a collection of configuration files that allow you to configure applications using code. They get their name from the Unix convention of hiding files by prefixing them with a dot, such as .zshrc, .bashrc, .vimrc, etc. These hidden files store your custom settings and preferences, enabling you to tailor your environment to your liking.

Why Manage Dotfiles?

1. Recoverability: If something goes wrong with your machine, having your dotfiles backed up means you can quickly recover your configuration.
2. Portability: Easily configure other working environments using your dotfiles. Simply clone your repo and you’re set.
3. Version Control: By using Git, you can maintain a history of changes made to your configuration files. This acts as a series of “snapshots” that you can revert to if needed.

Managing Dotfiles Locally with Stow and Symlinks

Using stow, a Unix command to manage symlinks, helps you keep a separate repo that links specific configuration files to the $HOME/.config directory.
​
This method allows you to manage only the apps you care about, without committing and pushing your entire .config directory publicly.

Organize Your Dotfiles: Create a directory structure for your dotfiles. Each configuration should have its own folder. Ideally, run git init and make this a git repository. You can checkout mine here:
​​
dotfiles/
├── bash/
│ └── .bashrc
├── vim/
│ └── .vimrc
└── git/
└── .gitconfig
​

Use Stow to Create Symlinks: Navigate to your dotfiles repo and run Stow to create symlinks in your home directory:

stow --target ~/.config .
​

Working with a .stowrc File

To improve the process above, let’s customize Stow’s behavior, you can use a .stowrc file to ignore certain files and configure the target directory for Stow. Here’s my .stowrc that’s pushed to my repo:
​​
--target=~/.config
--ignore=.stowrc
--ignore=DS_Store
​

Syncing Dotfiles Remotely with Coder

Coder (coder.com) provides cloud-based development environments, perfect for maintaining consistency across your devices. Here’s how to sync your dotfiles with Coder.

Coder got templates for pretty much every option you can think of, including syncing your dotfiles repo to an instance you provision with them.

To use their dotfiles template all you have to do is add startup_script under resource "coder_agent" "main" like so:
​​
resource "coder_agent" "main" {
startup_script = coder dotfiles -y https://github.com/<myname>/dotfiles
}
​

If you’re subscribed to DevOps ToolBox on Youtube there’s a video coming out soon going through this entire process step by step!

Hopefully this helped you come up with ideas behind the reasoning and application of my flow to improve yours.

While I know this can be improved with projects like chezmoi, or Nix’s home manager, I’m really curious to hear your thoughts! Please reply to this email with feedback / ideas and let’s chat!

Until next week, have a great reset of your day.