world.git - nix configuration for my machines

	Commit message (Collapse)	Author	Age	Files	Lines
*	nix libraries and modules will be under `nix/`	Franck Cuny	2024-03-04	1	-101/+0
\|
*	print various environments variable from CI	Franck Cuny	2024-01-26	1	-0/+8
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	CI is currently failing with the following error: ``` go: errors parsing go.mod: /home/runner/work/world/world/go.mod:3: invalid go version '1.21.4': must match format 1.23 ``` From [1]: > Before Go 1.21, the initial release of a Go toolchain was version 1.N, not 1.N.0 which makes me think that I'm CI is running with a version of go older than 1.21, while I specify 1.21 in my nix config. If that's the case, something is not correct in the CI environment and I should fix it. Hopefully the script will give me the information I need to debug this. [1] https://go.dev/doc/toolchain#version
*	add more commands to devshell's menu	Franck Cuny	2024-01-22	1	-0/+12
\|
*	disable linter for yaml	Franck Cuny	2024-01-21	1	-1/+5
\| \| \| \| \| \| \|	This is causing `nix flake check` to fail on CI, and I don't know why. I don't have issues locally. Commenting this out until I have a fix.
*	install some go related programs	Franck Cuny	2024-01-21	1	-2/+9
\|
*	enable deadnix for pre-commit hook	Franck Cuny	2023-12-14	1	-2/+1
\| \| \| \|	Now that I've deleted all unused code, I can run this properly.
*	use devshell to build / switch the configuration	Franck Cuny	2023-12-14	1	-0/+18
\|
*	pre-commit delegates all the work to treefmt	Franck Cuny	2023-12-14	1	-2/+6
\| \| \| \|	Clean up the yaml file for the GHA.
*	test	Franck Cuny	2023-12-14	1	-0/+1
\|
*	additional cleanup for flakes	Franck Cuny	2023-12-04	1	-24/+31
\| \| \| \| \|	Move the host configuration to `flake/hosts.nix` to follow what we did with `devshell`.
*	update to 23.11 and break down flakes	Franck Cuny	2023-12-04	1	-0/+41
	Update to 23.11 for both nix and home-manager. Break down the flake in multiple parts (hosts, devshell) so that they are easier to maintain. The main reason to start this is because `nix flake check` was failing, the flake was not correct.