Quickly create your daily-driver workstation setup from a simple-to-read configuration file
forge tends to provide a way to quickly configure a Linux (or UNIX-like) setup by automating the process of setting up package repositories, installing software packages, creating users, and other steps involved in setting up a typical daily driver.
This project takes birth from one of my oldest projects that I've used as a central repository to store not only my shared workstation configuration but also setup scripts for multiple operating systems, even further down to tweaks for specific computer hardware. I extracted all possible setup-related scripts into a re-usable program (just the way I did with my .emacs.d so that it lives as a standalone and dedicated project to hold my Emacs configuration) and I hope to create forge as a re-usable setup tool driven with a minimal configuration file and the least number of external dependencies.
- Void (TESTED)
- Arch (untested)
- Fedora (untested)
- Pop!_OS (untested)
- Debian (untested)
- macOS (untested)
- more (untested)
Dependencies that are (mostly) installed automatically:
Rest of the dependencies that are also needed:
forge can be used with your configuration file written in a Lisp-like format, specifying information about supported operating systems, software packages to be installed, and custom scripts to be executed in order to personalize the machine for one's own needs. forge can be started by executing start located at the root of the project and passing to it a run mode and a configuration file. Below is an example:
./start debug ~/.setup/forge-config.lisp
The above assumes that you are running the command at the root of the project directory cloned in a local workspace.
Please refer to the example config file for the basic layout or view one that is being used for a more detailed example.
- Fix execution of interactive scripts as setup steps