aboutsummaryrefslogtreecommitdiff
path: root/hosts/tahoe (unfollow)
Commit message (Collapse)AuthorFilesLines
2022-07-08fix(tahoe/backups): don't backup some directoriesFranck Cuny1-0/+1
I don't need to backup these directories in my home. Change-Id: Ia2302f2ebe74033090b86b52864787d2a63ecb4b Reviewed-on: https://cl.fcuny.net/c/world/+/620 Tested-by: CI Reviewed-by: Franck Cuny <franck@fcuny.net>
2022-07-02fix(new-lines): add or remove new lines where neededFranck Cuny1-1/+0
The pre-commit hook for new lines reported and correct a number of issues, so let's commit them now and after that we ca enable the hook for the repository. Change-Id: I5bb882d3c2cca870ef94301303f029acfb308740 Reviewed-on: https://cl.fcuny.net/c/world/+/592 Tested-by: CI Reviewed-by: Franck Cuny <franck@fcuny.net>
2022-06-23feat(hosts/home): use fish as my default shell everywhereFranck Cuny1-1/+1
Change-Id: I75df9d3ba133e3f7380a518e1b8c70a564f60482 Reviewed-on: https://cl.fcuny.net/c/world/+/481 Tested-by: CI Reviewed-by: Franck Cuny <franck@fcuny.net>
2022-06-20ref(home/shell): make it easier to share common things between shellsFranck Cuny1-2/+2
I'm considering trying again fish, and there are a number of things that should be common between zsh and fish (aliases, environment variables, ...). Instead of duplicating these settings multiple time, I'm consolidating the shell configurations under `home/shell`, and I can set the shell I want to use with `my.home.shell.name`. The first step is to move the modules for fish and zsh under `home/shell`, add an interface to pick which one I want to use, and modify the `host/home.nix` configuration to keep using zsh with the new interface. Change-Id: Idb66b1a6fcc11a6eeaf5fd2d32dd3698d2d85bdf Reviewed-on: https://cl.fcuny.net/c/world/+/455 Tested-by: CI Reviewed-by: Franck Cuny <franck@fcuny.net>
2022-06-11ref(drone): remove all modules and configurationsFranck Cuny2-5/+0
I do not use drone anymore, no need to keep this around. Change-Id: I8f9564747939a6d1a2b95bcfe8e2c70e46d8bc1e Reviewed-on: https://cl.fcuny.net/c/world/+/411 Tested-by: CI Reviewed-by: Franck Cuny <franck@fcuny.net>
2022-06-10fix(fmt): correct formatting for all nix filesFranck Cuny2-2/+4
This was done by running `nixpkgs-fmt .'. Change-Id: I4ea6c1e759bf468d08074be2111cbc7af72df295 Reviewed-on: https://cl.fcuny.net/c/world/+/404 Tested-by: CI Reviewed-by: Franck Cuny <franck@fcuny.net>
2022-06-09fix(secrets): buildKite agents can read gerrit secretsFranck Cuny1-0/+4
We need to ensure the agents can read the secrets / tokens to vote after a build. Change-Id: I066c2482a795b21badaa9cc3c525373d7945b084 Reviewed-on: https://cl.fcuny.net/c/world/+/341 Reviewed-by: Franck Cuny <franck@fcuny.net>
2022-06-09ref(home): structure and add commentsFranck Cuny1-2/+11
Change-Id: I9abd49136df79a9ed040c9ec0e12eea30736c9ff Reviewed-on: https://cl.fcuny.net/c/world/+/295 Reviewed-by: Franck Cuny <franck@fcuny.net>
2022-06-04fix(gerrit-hook): update the configuration with correct URLFranck Cuny1-10/+12
Change-Id: Iae8860631a9d313d5b4f78d171d0dfebc6ef6ff9 Reviewed-on: https://cl.fcuny.net/c/world/+/283 Reviewed-by: Franck Cuny <franck@fcuny.net>
2022-06-04fix(secrets): set the owner for buildkite agent secretsFranck Cuny1-0/+1
There's one user per agent. If we don't set an owner for that file, it will be owned by root. Let's set the ownership to the first builder. Change-Id: I1270e6858c0bf2797bd12c2557d84a494cef5081 Reviewed-on: https://cl.fcuny.net/c/world/+/281 Reviewed-by: Franck Cuny <franck@fcuny.net>
2022-06-04ref(drone): remove secret and CLI for droneFranck Cuny1-5/+0
I'm not using drone anymore. I don't need the CLI and the secret to be installed. Change-Id: I9c8ecfe5f051fd70d78f0e2e9aaa705e48627714 Reviewed-on: https://cl.fcuny.net/c/world/+/261 Reviewed-by: Franck Cuny <franck@fcuny.net>
2022-06-04feat(gerrit): add secret for gerrit-hookFranck Cuny2-0/+16
The secret is the configuration for the gerrit-hook tool. It contains the URL to our gerrit instance, the username/password for the gerrit user used by the tool, the API token for buildKite and the name of the organization in buildKite. Change-Id: I58233e085c92d4c5db5635eb9942a5e87ee9e55d Reviewed-on: https://cl.fcuny.net/c/world/+/204 Reviewed-by: Franck Cuny <franck@fcuny.net>
2022-05-30feat(hosts/tahoe): enable buildkite agentFranck Cuny1-0/+1
Change-Id: I12cc741bdfb074f7d2a006547860362176afe372 Reviewed-on: https://cl.fcuny.net/c/world/+/169 Reviewed-by: Franck Cuny <franck@fcuny.net>
2022-05-30feat(buildkite): add the auth tokenFranck Cuny2-0/+7
Change-Id: I652a3326caf8f949e9734849d1492f7b9764a766 Reviewed-on: https://cl.fcuny.net/c/world/+/167 Reviewed-by: Franck Cuny <franck@fcuny.net>
2022-05-29ref(tahoe): remove droneFranck Cuny1-9/+1
I will not be using drone anymore, and will likely replace it with buildkite. Change-Id: I45d91c43090aaba119855158e071dae377c1897f Reviewed-on: https://cl.fcuny.net/c/world/+/162 Reviewed-by: Franck Cuny <franck@fcuny.net>
2022-05-27feat(hosts/tahoe): replace gitea by cgitFranck Cuny1-2/+1
Change-Id: I3b00408d7550d7660fb33940ae2cd0806076f4d2 Reviewed-on: https://cl.fcuny.net/c/world/+/62 Reviewed-by: Franck Cuny <franck.cuny@gmail.com>
2022-05-26feat(tahoe): enable gerritFranck Cuny1-0/+4
2022-05-22feat(tahoe): enable sourcegraphFranck Cuny1-0/+4
2022-05-15zsh: switch to zsh as the default shellFranck Cuny1-1/+1
`zsh' is available everywhere and is compatible with bash. When using `fish' I need to remember how to do things. While the completion style is nicer, I don't care about the rest. I prefer to have a consistent experience in the shell, no matter where am I. This is an initial configuration, I might need to make a few changes as I go.
2022-05-02tahoe: enable exec runner for droneFranck Cuny1-1/+1
2022-04-24backups: do backups for the laptopFranck Cuny1-1/+2
From the laptop I only backup /home/fcuny, as the rest should be straightforward to rebuild with nix. I run that backup as my own user, since I need my ssh key to use the remote repository (which is on the NAS). I also need a new secret for it (I might have been able to use `pass' for this, but well, that's easy enough). For the NAS, I update the list of directories to backup to include home, this will be on the systems backup.
2022-04-21syncthing: don't run from homeFranck Cuny1-1/+0
2022-04-21syncthing: configure the keys for tahoeFranck Cuny3-0/+20
2022-04-21syncthing: enable on tahoeFranck Cuny1-0/+1
2022-04-21syncthing: let's run it from home-managerFranck Cuny1-0/+1
2022-04-13drone: configuration fixesFranck Cuny1-1/+1
2022-04-13drone: initial attempt at configuring itFranck Cuny4-0/+16
2022-04-13modules: make the vhost be configurableFranck Cuny1-3/+9
2022-04-13grafana: correct domain name ...Franck Cuny1-1/+1
2022-04-13grafana: the vhost is configurableFranck Cuny1-1/+4
2022-04-13tahoe: set owner for secret related to ACMEFranck Cuny1-1/+4
2022-04-13secrets: re-key all secrets for tahoeFranck Cuny8-30/+27
2022-04-13grafana: try to configure the domain with acme+dnsFranck Cuny3-1/+9
2022-04-13nginx: get a simple solution to work firstFranck Cuny1-13/+1
2022-04-13nginx: add nginx as a reverse proxyFranck Cuny1-1/+14
This will ultimately replace traefik.
2022-04-13secrets: move the actual secrets with hosts configFranck Cuny7-0/+39
Having the secrets closer to the host is easier to manage. At the moment I don't have secrets that are shared across multiple hosts, so that's an OK approach.
2022-04-11tahoe: fix backup configurationFranck Cuny1-2/+3
2022-04-10secrets: move all the secrets under module/Franck Cuny1-3/+3
Refactor a bit the configuration, which should simplify the management and usage of secrets from now on.
2022-04-10add a module for backup with resticFranck Cuny1-10/+4
Do a single backup for the host, instead of running multiple ones.
2022-04-09tahoe: enable network with early bootFranck Cuny2-11/+19
So we can unlock the disks remotely.
2022-04-08hosts: rename hardware-configuration to hardwareFranck Cuny2-1/+1
2022-04-08hosts: add services to tahoeFranck Cuny2-1/+45
2022-04-07initial attempt to reconfigure home-managerFranck Cuny2-0/+18
All the modules that are needed for home-manager should be under `home/`, and each host will have a `host.nix` where the modules are enabled as needed. Later on we can create some profiles to make it easier to consume the configuration. I apply this only to tahoe for now, as the amount of packages needed for my user are pretty limited.
2022-04-06enable AMD module correctlyFranck Cuny1-1/+1
2022-04-06refactor boot configuration to a moduleFranck Cuny1-1/+4
We don't need the previous `hosts/common/system` configs anymore, as everything has been moved out. We keep some boot configuration for carmel in the host configuration for now, but I need to check why I don't have similar settings for tahoe (since I also need to unlock the host remotely).
2022-04-06refactor configuration for AMDFranck Cuny1-38/+39
2022-04-05refactor network configurationFranck Cuny1-3/+19
2022-04-05network: move tailscale in modulesFranck Cuny2-20/+23
Move the networking configuration for the hosts to its own file.
2022-04-03Revert "create a new role for navidrome"Franck Cuny1-4/+2
This reverts commit 814a495e9c74e3211c6b6640397111115832207b.
2022-04-03create a new role for navidromeFranck Cuny1-2/+4
Apply the role to tahoe.
2022-03-12hosts: add profilesFranck Cuny1-1/+1
Profiles contain a collection of modules.
2022-03-06tahoe: enable tailscaleFranck Cuny1-0/+1
2022-03-05tahoe: remove creation of some directoriesFranck Cuny1-29/+9
2022-03-05tahoe: new hardware configuratioFranck Cuny1-21/+13
2022-03-02tahoe: enable wireguardFranck Cuny1-0/+1
2022-02-27tahoe: create some directoriesFranck Cuny1-0/+15
Ensure at least /data/media/music is created with the proper ownership.
2022-02-27tahoe: include NAS profileFranck Cuny1-0/+1
2022-02-27hosts: add tahoe, the new NASFranck Cuny2-0/+111