A collection of configuration files that forms a unique development environment.
UI wise, dotfiles is as minimal as one can go:
- No status bar.
- No notifications.
- No wallpaper.
dotfiles is a configuration management project that allow users to easily replicate their local environment configuration.
For the architecture, please refer to ARCHITECTURE.md.
| Workspace 1 (btop) | Workspace 2 (alacritty) |
|---|---|
 |
 |
| Workspace 3 (librewolf) | Special workspace (alacritty) |
|---|---|
 |
 |
helix |
nvim |
|---|---|
 |
 |
zellij |
tmux |
|---|---|
 |
 |
Here is a list of explanation about the main programs that are used in this development environment.
dotfiles installs and configures hyprland as the main window manager.
dotfiles does not touch existing window managers during the installation and configuration of hyprland.
Status Bar
There are no status bars (e.g. waybar) in this configuration.
During the initial boot, hyprland is configured to open three programs in three seperate workspaces:
btop(1)alacritty(2)librewolf(3)
Note: User specific configurations for librewolf (e.g. extensions, themes, font, keymaps) should be done explicitly by the user.
hyprland's special workspace (scratchpad) is also configured to open alacritty.
This workspace can be used to execute less frequent commands (e.g connecting to wifi or a bluetooth device).
dotfiles installs and configures alacritty as the terminal on a given host.
It also installs and configures starship as the shell prompt.
dotfiles installs and configures either tmux or zellij to be used as the main terminal multiplexer.
dotfiles installs and configures either Neovim or Helix as the editor on a given host.
As of version 0.3.0, dotfiles is designed to support x86_64 Arch Linux hosts only.
Due to time constraints, unfortunately I can only maintain the project for the main OS I use.
However, most of the installation steps can be applied to other Linux distributions easily thanks to Ansible.
The installation is done through an Ansible playbook. Please refer here to see the tools and installation steps.
The usage of the tools are the same, regardless of the installation method. Please refer to each tool's documentation to see their usage.
- (P1) Add missing tools to the installation (recurring).
- (P1) Create an interface to verify and list the installed tools, a different playbook maybe?