about summary refs log tree commit diff
path: root/hosts/carmel (follow)
Commit message (Collapse)AuthorAgeFilesLines
* profiles/default: move stuff related to bootFranck Cuny2023-05-022-2/+0
|
* profiles: move things around for btrfsFranck Cuny2023-05-021-1/+0
|
* profiles/hardware: create a few profiles related to hardwareFranck Cuny2023-05-022-3/+1
|
* profiles: create default and serverFranck Cuny2023-05-021-3/+8
| | | | | | | | | | The NAS and the router are "servers", and we create a base profile for them. We add a default profile that will set things that are common to all my hosts, and we start with the locales. Update tahoe/carmel to use the server profile.
* hosts/carmel: enable promtailFranck Cuny2023-04-231-1/+5
|
* modules/monitoring: consolidate all monitoring services togetherFranck Cuny2023-04-231-1/+1
| | | | | This will help to organize and structure monitoring modules a bit better.
* hosts/carmel: don't log dns queries in dnsmasqFranck Cuny2023-04-151-1/+0
| | | | This is way too verbose
* hosts/carmel: start dnsmasq once network interfaces are onlineFranck Cuny2023-04-151-0/+7
|
* hosts/carmel: don't release DHCP lease on wan interfaceFranck Cuny2023-04-151-0/+3
| | | | No need to release the lease if we are rebooting.
* hosts/carmel: serve the leases on port 8067Franck Cuny2023-04-061-4/+7
| | | | | Bind to the wireguard interface, and use the port 8067 (67 is the port used for DHCP requests).
* hosts/carmel: run dnsmasql-to-html when leases changeFranck Cuny2023-04-061-1/+4
| | | | | | The option `dhcp-script` can be used to run a script every time a new lease is added or deleted. We configure this option to run the script that generates a static HTML file with the leases.
* hosts/carmel: the wireguard interface is trustedFranck Cuny2023-04-051-1/+1
|
* hosts/carmel: add wireguard keyFranck Cuny2023-04-053-0/+23
|
* hosts/carmel: drop checkReversePathFranck Cuny2023-04-051-3/+0
| | | | This is managed in the tailscale module.
* hosts/carmel: enable tailscaleFranck Cuny2023-04-051-0/+2
|
* hosts/carmel: more options for dnsmasqFranck Cuny2023-04-031-0/+2
|
* hosts/carmel: add a few more options for dnsmasqFranck Cuny2023-04-031-0/+6
|
* hosts/carmel: enable prometheus exporter for DNSmasqFranck Cuny2023-04-031-0/+5
|
* hosts/carmel: reconfigure the host as a routerFranck Cuny2023-04-037-113/+204
| | | | | | | | | | | | I'm not using it as a desktop, and the current router is getting old and will likely fail in the near future. It's also a debian machine configured manually, so let's reconfigure carmel as our new router. There are three NICs in the host: 2 are 10Gb and one is 1Gb. The 1Gb will be used as the upstream interface, and one of the 10Gb will be for the LAN. There are 2 VLANs to configure: one for IoT devices and one for guest.
* fix(hosts): the WM manager needs to be in home.nixFranck Cuny2022-09-232-3/+4
|
* ref(home-manager): don't use home-manager when building the hostFranck Cuny2022-09-221-8/+2
| | | | | | | | | | | | | | | | | | | When rebuilding the host (through `nixos-rebuild switch --flake`) I don't want to rebuild also my home-manager configuration. I want these to be two different steps. I rebuild the home-manager configuration more frequently and it's a waste of time and CPU to rebuild the world every time. This is a pretty large refactoring: - move checks back into the flake: if I modify a check, the configuration for `pre-commits` is not regenerated, as the file with the checks is not monitored with `direnv` (I could probably configure it for it, but not now) - remove `home.nix` from the host level configuration - introduce a `mkHomeManagerConfiguration` function to manage the different user@host - fix a warning with the rust overlay
* fix(new-lines): add or remove new lines where neededFranck Cuny2022-07-021-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>
* feat(hosts/home): use fish as my default shell everywhereFranck Cuny2022-06-231-1/+1
| | | | | | | Change-Id: I75df9d3ba133e3f7380a518e1b8c70a564f60482 Reviewed-on: https://cl.fcuny.net/c/world/+/481 Tested-by: CI Reviewed-by: Franck Cuny <franck@fcuny.net>
* ref(home/shell): make it easier to share common things between shellsFranck Cuny2022-06-201-1/+1
| | | | | | | | | | | | | | | | | | | | 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>
* ref(profiles): get rid of all the profilesFranck Cuny2022-06-093-6/+17
| | | | | | | | | | | | | | All the modules that are setup by the profiles are now managed at the host level. This simplify some configuration, and will make it easier to adjust things at the host instead of trying to squeeze everything into profiles. This will also help the refactoring later, when I'll split nixos and home-manager configuration. Change-Id: I17ffda8b0b5d15bf1915c6fae5030380523d74b5 Reviewed-on: https://cl.fcuny.net/c/world/+/297 Reviewed-by: Franck Cuny <franck@fcuny.net>
* ref(GTK): remove the profile for GTKFranck Cuny2022-06-092-0/+4
| | | | | | | | All the configuration is done at the host level. Change-Id: Ib5ef71ea7955f6872fb08f576e48b24a70600693 Reviewed-on: https://cl.fcuny.net/c/world/+/296 Reviewed-by: Franck Cuny <franck@fcuny.net>
* ref(home): structure and add commentsFranck Cuny2022-06-091-17/+32
| | | | | | Change-Id: I9abd49136df79a9ed040c9ec0e12eea30736c9ff Reviewed-on: https://cl.fcuny.net/c/world/+/295 Reviewed-by: Franck Cuny <franck@fcuny.net>
* ref(desktop): move all the modules for home-manager to host levelFranck Cuny2022-06-091-0/+9
| | | | | | Change-Id: I92abe7d6c9a1f7c5ef3f157137c59cde751d50f0 Reviewed-on: https://cl.fcuny.net/c/world/+/294 Reviewed-by: Franck Cuny <franck@fcuny.net>
* ref(trusted): consume modules within host's configurationFranck Cuny2022-06-091-0/+10
| | | | | | | | | Remove the trusted profiles, the modules are installed directly within the host configuration. Change-Id: I0566fb359803da16bdd3a38e2901deac477fb078 Reviewed-on: https://cl.fcuny.net/c/world/+/293 Reviewed-by: Franck Cuny <franck@fcuny.net>
* ref(multimedia): move multimedia modules to hostsFranck Cuny2022-06-091-3/+6
| | | | | | | | | Consume the modules related to multimedia applications at the host level, instead of having a level of indirection with a profile. Change-Id: I567f0e01cbfe591beaa2e9086e33434402a4a002 Reviewed-on: https://cl.fcuny.net/c/world/+/292 Reviewed-by: Franck Cuny <franck@fcuny.net>
* zsh: switch to zsh as the default shellFranck Cuny2022-05-151-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.
* carmel: configure the desktop properlyFranck Cuny2022-04-083-1/+22
|
* hosts: rename hardware-configuration to hardwareFranck Cuny2022-04-082-1/+1
|
* hosts: add services to tahoeFranck Cuny2022-04-081-3/+0
|
* enable AMD module correctlyFranck Cuny2022-04-061-1/+1
|
* refactor boot configuration to a moduleFranck Cuny2022-04-062-10/+15
| | | | | | | | | 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).
* refactor configuration for AMDFranck Cuny2022-04-061-28/+26
|
* refactor network configurationFranck Cuny2022-04-051-1/+19
|
* carmel: enable the soundFranck Cuny2022-04-051-0/+1
|
* network: move tailscale in modulesFranck Cuny2022-04-052-16/+18
| | | | Move the networking configuration for the hosts to its own file.
* sound: add a new moduleFranck Cuny2022-04-051-13/+11
| | | | | | | | | | This is the start of yet another refactoring of the configuration. Sound configuration is moving to a module, and we enable it as needed at the host level. It takes care of configuring pipewire and install the packages needed too. This module is applied to the laptop and the desktop.
* boot: reorganize and add commentsFranck Cuny2022-02-181-11/+8
| | | | Most of the options for booting are common to all hosts.
* hosts: remove btrfs subvolume 'media'Franck Cuny2022-02-161-6/+0
| | | | | The host would not boot successfully with that, I'm doing something wrong.
* hosts: add a new subvolumes to carmelFranck Cuny2022-02-141-0/+6
| | | | | Create a subvolume named 'media' that we will mount under /home/fcuny/media so we can snapshots /home/fcuny without the medias.
* hosts: load igb kernel module for initrdFranck Cuny2022-02-131-0/+1
| | | | We need to load the driver for the NIC.
* hosts: unlock disks remotely on bootFranck Cuny2022-02-131-16/+4
| | | | | Enable a SSH daemon in initrd, with our keys, so we can unlock remotely the disk on reboot.
* hosts: remove configuration for ssh keys in initrdFranck Cuny2022-02-131-1/+0
| | | | This is not working yet, we will figure this out later.
* hosts: decrypt root disk via ssh on bootFranck Cuny2022-02-131-0/+21
|
* hosts: import common modulesFranck Cuny2022-02-121-2/+1
| | | | | | Update the `mkSystem` function to include the proper common module, and fix the path to import the common configuration for a desktop into `carmel`.
* hosts: centralize network configurationFranck Cuny2022-02-121-10/+15
|
* hosts: set hostname from configurationFranck Cuny2022-02-101-6/+2
|
* fix a few errorsFranck Cuny2022-02-101-0/+1
|
* nix: fix a bunch of stuffFranck Cuny2022-02-101-1/+0
|
* hosts: use systemd-resolved on carmelFranck Cuny2022-02-091-0/+6
|
* hosts: remove usersFranck Cuny2022-02-091-1/+0
|
* hosts: remove / clean codeFranck Cuny2022-02-091-44/+5
| | | | | | There's a lot of commented stuff I don't need, and move things that are configured in the host into modules, which will improve re-usability and readability of this configuration.
* home-manager: simplify the configurationFranck Cuny2022-02-091-0/+3
| | | | | | | | | | | | | 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").
* hosts: remove unneeded commentsFranck Cuny2022-02-081-6/+0
|
* systems: move some packages out of host configFranck Cuny2022-02-081-5/+0
|
* carmel: use DHCP on the wireless interfaceFranck Cuny2022-02-081-1/+2
|
* xserver: initial configurationFranck Cuny2022-02-081-8/+0
| | | | Enable it for the desktop.
* systems: default configuration for all systemsFranck Cuny2022-02-081-3/+0
|
* carmel: initial host configurationFranck Cuny2022-02-072-0/+144
Initial configuration for the desktop (carmel).
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-12-26 15:38:02 +0000