world.git - nix configuration for my machines

	Commit message (Collapse)	Author	Age	Files	Lines
*	tools(govanity): add the tool to flake.nix	Franck Cuny	2022-05-29	1	-1/+4
\| \| \| \|	Change-Id: Ib2792fa8c3f861d290f2495a10672cdfd11c48d9
*	ref(dnsupdate): move under tools	Franck Cuny	2022-05-25	1	-7/+1
\| \| \| \| \| \| \| \| \|	Integrate properly the tool `dnsupdate` with flake.nix, by adding a default.nix inside its directory. Having all the tools under a directory named `tools` is easier to reason about. I don't need a go.mod at the top level directory either, each tool will have its own.
*	ref(notes): drop flake.nix	Franck Cuny	2022-05-25	1	-0/+1
\| \| \| \| \| \| \|	There's no need to have a flake.nix for the notes, we can use the same mechanism as for the blog and resume. Add a README so I remember how to use this in the future.
*	ref(resume): remove flake.nix	Franck Cuny	2022-05-25	1	-1/+4
\| \| \| \| \| \| \|	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.
*	ref(blog): drop the flake configuration	Franck Cuny	2022-05-25	1	-0/+2
\| \| \| \| \| \|	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.
*	nix: add a command `dnsupdate` to update the DNS	Franck Cuny	2022-05-07	1	-1/+13
\| \| \| \| \|	Running `nix run .#dnsupdate` will execute the program to ensure the configuration is correct.
*	flake: add checks	Franck Cuny	2022-04-13	1	-0/+12
\| \| \| \|	This is not working great so far.
*	remove `mkHome` from lib	Franck Cuny	2022-04-09	1	-22/+0
\| \| \| \| \|	home-manager configuration is used as a module, we don't have two different ways to configure the host anymore.
*	home-manager: add `isTrusted`	Franck Cuny	2022-04-03	1	-0/+2
\| \| \| \| \| \| \| \| \| \|	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.
*	rename `desktop` to `isDesktop`	Franck Cuny	2022-04-03	1	-2/+2
\| \| \| \| \| \| \| \|	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`.
*	remove mytools	Franck Cuny	2022-04-03	1	-7/+0
\| \| \| \|	I don't need this for now, as I've replace music-organizer with beets.
*	nas: install music-organizer from the main branch	Franck Cuny	2022-03-27	1	-1/+1
\|
*	nas: install music-organizer	Franck Cuny	2022-03-27	1	-5/+16
\|
*	flake: add new overlay: NUR	Franck Cuny	2022-02-27	1	-0/+2
\| \| \| \|	NUR is the nux user repository, which provides additional packages.
*	hosts: add tahoe, the new NAS	Franck Cuny	2022-02-27	1	-0/+9
\|
*	agenix: add flake for agenix	Franck Cuny	2022-02-21	1	-0/+5
\| \| \| \|	This will be used to store secrets in the repository.
*	hosts: add aptos	Franck Cuny	2022-02-21	1	-0/+10
\| \| \| \| \|	aptos is my laptop (dell xps 13'). This adds the initial configuration for it.
*	emacs: pull community's overlay	Franck Cuny	2022-02-13	1	-0/+2
\| \| \| \|	We need the community overlay to get the pure GTK port of Emacs for now.
*	fix a few errors	Franck Cuny	2022-02-10	1	-1/+0
\|
*	nix: fix a bunch of stuff	Franck Cuny	2022-02-10	1	-2/+5
\|
*	home-manager: split the configuration	Franck Cuny	2022-02-10	1	-16/+31
\|
*	home-manager: simplify the configuration	Franck Cuny	2022-02-09	1	-4/+1
\| \| \| \| \| \| \| \| \| \| \| \| \|	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").
*	i3: separate configuration for xserver and i3	Franck Cuny	2022-02-08	1	-5/+1
\| \| \| \| \|	Let's first configure the xserver in the desktop module, then we can have a configuration for i3 in the home-manager.
*	home-manager: fix initial configuration	Franck Cuny	2022-02-08	1	-0/+9
\| \| \| \| \|	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.
*	carmel: apply systems and desktop modules	Franck Cuny	2022-02-08	1	-0/+2
\|
*	flake: pull home-manager and unstable	Franck Cuny	2022-02-07	1	-1/+10
\|
*	flake: install my user on carmel	Franck Cuny	2022-02-07	1	-0/+1
\|
*	carmel: initial host configuration	Franck Cuny	2022-02-07	1	-0/+21
	Initial configuration for the desktop (carmel).