How riderius/dotfiles works
Project type and purpose
• This is a “dotfiles” repository: a collection of configuration files and small helper scripts to bootstrap and maintain a consistent developer workstation environment.
• Its goal is to store, version, and deploy settings for shells (fish, zsh), editors (Neovim, Emacs), window manager (i3), terminal emulator (Alacritty), Git, SSH, package-manager defaults (pacman), UFW applications, and custom helper scripts.
File structure
Top-level directories and files:
• .config/ … contains per-application subfolders (alacritty, fish, git, i3, i3status, nvim, pacman)
• .emacs.d/ … Emacs initialization and custom Lisp packages
• .local/bin/ … executable helper scripts (git-imgdiff, restart-nm, windscribe start/stop)
• .ssh/config … SSH client config
• .zshrc, .vimrc, .p10k.zsh … standalone shell and editor config
• install.sh … bootstrapping script that clones/syncs the repo and sets up symlinks
• README.md, LICENSE … metadata
• competitive/, latex_template.tex, ufw_applications/ … auxiliary resources
Architectural patterns:
• Single Git repository as the “source of truth”
• install.sh acts as orchestration layer: clones repo, creates symlinks, invokes per-tool installation steps
• Modular config: each tool’s settings live in their own subfolder under .config or top-level dotfiles
README
• Very simple: “My Dotfiles.”