| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Integrate the resume with the rest of the repository, as I did for the
blog in the previous commit.
Added a script to copy the resume in the static directory of the blog.
|
| |
|
|
|
|
| |
There's no need to have multiple `flake.nix` in the repository. Make the
blog part of the flake configuration at the root level of the
repository, delete the one in the blog, and update the documentation.
|
| |
|
|
|
| |
Running `nix run .#dnsupdate` will execute the program to ensure the
configuration is correct.
|
| |
|
|
| |
This is not working great so far.
|
| |
|
|
|
| |
home-manager configuration is used as a module, we don't have two
different ways to configure the host anymore.
|
| |
|
|
|
|
|
|
|
|
| |
Install and configure some programs only on trusted machines. On trusted
machines, my mails, GPG and a few other things are configured. A machine
where this is not needed on a regular basis to get things done don't
need that much information.
Also rename `desktop/trust` to `trusted`, in case we want these packages
on a host that is not a desktop, and `trusted` is a better description.
|
| |
|
|
|
|
|
|
| |
The variable is used to define the kind of machine we're managing.
`isDesktop` is a bit more descriptive.
We import `devel` for all machines, and we fine tune which packages we
want to install based on the value of `isDesktop`.
|
| |
|
|
| |
I don't need this for now, as I've replace music-organizer with beets.
|
| | |
|
| | |
|
| |
|
|
| |
NUR is the nux user repository, which provides additional packages.
|
| | |
|
| |
|
|
| |
This will be used to store secrets in the repository.
|
| |
|
|
|
| |
aptos is my laptop (dell xps 13'). This adds the initial configuration
for it.
|
| |
|
|
| |
We need the community overlay to get the pure GTK port of Emacs for now.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
I'm still struggling with documentation, and I'd rather have something
simple that works rather than smart and does not work.
The configuration for the host imports the modules that are relevant to
that host (in the case of carmel, desktop and systems).
For the home-manager, I create a profile "desktop" that contains stuff
related to a desktop (i3, etc), and it includes the module "common" that
contains stuff that I want on any machines (so that in the future, for
a machine that is a server, the home manager will only import "common").
|
| |
|
|
|
| |
Let's first configure the xserver in the desktop module, then we can
have a configuration for i3 in the home-manager.
|
| |
|
|
|
| |
This configuration is working, and I'm still unclear of how this is
supposed to be done correctly. Might need to iterate a few more times.
|
| | |
|
| | |
|
| | |
|
|
|
Initial configuration for the desktop (carmel).
|
