aboutsummaryrefslogtreecommitdiff
path: root/flake (unfollow)
Commit message (Collapse)AuthorFilesLines
2025-11-15drop terraform/terranixFranck Cuny4-90/+1
2025-11-03consolidate all modules under modules/Franck Cuny1-5/+4
2025-11-02fix remote scriptFranck Cuny1-1/+1
2025-11-02remove colmenaFranck Cuny3-75/+1
2025-11-02add helpers to build remotely with nixosFranck Cuny2-1/+137
2025-11-02simplify configuration for darwinFranck Cuny1-13/+0
2025-10-24simplify hosts managementFranck Cuny1-14/+27
2025-10-18move the disk configuration for rivendell as a profileFranck Cuny1-0/+1
2025-10-13move modules under nixosFranck Cuny1-2/+0
2025-10-13consistent home-manager configuration for all nixos hostsFranck Cuny1-8/+21
2025-10-12make the remote unlock bits a nix moduleFranck Cuny1-0/+12
Move all the hardware configuration for rivendell into the default.nix.
2025-09-12start to refactor nixos modulesFranck Cuny1-0/+1
2025-09-08move common modules together and simplify importsFranck Cuny1-4/+2
2025-09-08Revert "move droplet specific settings to its own module"Franck Cuny1-2/+6
This reverts commit 3b47113c28c5180d4d5d710e3c1fe74f95aa7226.
2025-09-08move droplet specific settings to its own moduleFranck Cuny1-6/+2
2025-09-07move deployment bits to colmena declarationFranck Cuny1-2/+24
2025-09-06move things aroundFranck Cuny4-1/+74
2025-09-04install correct version of colmenaFranck Cuny2-1/+2
2025-09-01initial attempt at using colmena to deploy nixos configurationsFranck Cuny2-0/+38
Can be used that way: ``` colmena exec --impure -v --on do-rproxy -- 'systemctl status nginx' ``` or ``` colmena --impure apply dry-activate --on synology-vm ```
2025-09-01configure keycloak with terraformFranck Cuny1-0/+2
2025-08-31my website will be managed in an external repositoryFranck Cuny2-29/+0
2025-08-31manage terraform configuration with terranixFranck Cuny2-1/+62
All the terraform configuration is managed within one state instead of having multiple state for each components. This might not be the best practice but it simplifies things for me. Now, all I need to do is to run `nix run .#tf -- plan` and I can see what will be changed for all the resources that I care about.
2025-08-24run `goget` on `go.fcuny.net`Franck Cuny2-0/+2
2025-08-21split-up firefox configurationFranck Cuny1-0/+1
Ensure we install the bin package, so that we can use the 1password extension (we need a signed binary for that).
2025-08-12more simplificationsFranck Cuny1-2/+6
2025-08-12delete LLM related stuff for nowFranck Cuny1-1/+0
2025-08-12move each machine configuration to a folderFranck Cuny1-59/+44
This will give me a bit more flexibility to configure things per machine in the future.
2025-08-10manage a DigitalOcean virtual machine with nixosFranck Cuny1-1/+1
Add a new machine on DigitalOcean and provision it using terraform + nixos-anywhere. This takes care of bringing the machine up on nixos completely, and use a static SSH host key in order to configure wireguard at the same time.
2025-07-24fix configuration for work machineFranck Cuny1-0/+2
The hostname is capitalized so let's also capitalize the filename! The overlays are not under `customPackages` anymore.
2025-07-21keep organizing into modules and profilesFranck Cuny1-3/+2
2025-07-21move all profiles, modules, and flakes to top-levelFranck Cuny7-0/+355
2024-03-04nix libraries and modules will be under `nix/`Franck Cuny2-131/+0
2024-02-02install firefoxFranck Cuny1-2/+11
The firefox packages for darwin are broken. `bandithedoge/nixpkgs-firefox-darwin` provides an overlay to install the package on darwin. Add some specific configurations to make firefox work as I want out of the box. We also add NUR to install some firefox extensions (ublock, 1password).
2024-01-26print various environments variable from CIFranck Cuny1-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
2024-01-22add more commands to devshell's menuFranck Cuny1-0/+12
2024-01-21disable linter for yamlFranck Cuny1-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.
2024-01-21install some go related programsFranck Cuny1-2/+9
2023-12-15various fixes for errors reported by deadnixFranck Cuny2-21/+1
2023-12-14enable deadnix for pre-commit hookFranck Cuny1-2/+1
Now that I've deleted all unused code, I can run this properly.
2023-12-14use devshell to build / switch the configurationFranck Cuny1-0/+18
2023-12-14pre-commit delegates all the work to treefmtFranck Cuny1-2/+6
Clean up the yaml file for the GHA.
2023-12-14testFranck Cuny1-0/+1
2023-12-04additional cleanup for flakesFranck Cuny2-24/+52
Move the host configuration to `flake/hosts.nix` to follow what we did with `devshell`.
2023-12-04update to 23.11 and break down flakesFranck Cuny2-0/+61
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.