- create your partitions
- fork this project
- create your user or rename mine
You need to deactivate the xfdestop on the first boot.
To do that, go to the xfce settings (Settings -> Settings Manager), then to Session and Startup.
From there, you will go to the Current Session tab.
On this tab you will see a list of processes.
For the xfdestop process, switch the Restart Style from Immediately to Never.
Make sure you have the xfdesktop selected and then tap on Quit Program on the bottom left.
Don't forget to transfer your SSH keys.
You can transfer your firefox profile to the new machine/setup.
To do this, you can simply transfer the ~/.mozilla/firefox folder.
If it does not work, open an issue.
You have to install doom emacs yourself.
If you kept my user config, then the .doom.d folder is already present,
so you just have to do the installation (clone + doom install)
If you have any, open an issue! If it's not clear, it can be made better so just open an issue 😄
Following is DevOS readme. it covers how devos works, what it does and what is the installation process.
DevOS grants a simple way to use, deploy and manage NixOS systems for personal and productive use. A sane repository structure is provided, integrating several popular projects like home-manager, devshell, and more.
Striving for nix first™ solutions with unobstrusive implementations, a flake centric approach is taken for useful conveniences such as automatic source updates.
Skip the indeterminate nature of other systems, and the perceived tedium of bootstrapping Nix. It's easier than you think!
A lot of the implementation is less than perfect, and huge redesigns will happen. There are unstable versions (0.x.x) to help users keep track of changes and progress.
Check out the guide to get up and running.
The author maintains his own branch, so you can take inspiration, direction, or make critical comments about the code. 😜
NixOS provides an amazing abstraction to manage our environment, but that new power can sometimes bring feelings of overwhelm and confusion. Having a turing complete system can easily lead to unlimited complexity if we do it wrong. Instead, we should have a community consensus on how to manage a NixOS system and its satellite projects, from which best practices can evolve.
The future is declarative! 🎉
I'd love to see this in the nix-community should anyone believe its reached a point of maturity to be generally useful, but I'm all for waiting until 1.0#121 to save the cache work, too.
There are two branches from which to choose: core and community. The community branch builds on core and includes several ready-made profiles for discretionary use.
Every package and NixOS profile declared in community is uploaded to cachix, so everything provided is available without building anything. This is especially useful for the packages that are overridden from master, as without the cache, rebuilds are quite frequent.
DevOS is licensed under the MIT License.