about summary refs log tree commit diff
path: root/hosts/carmel/services.nix (follow)
Commit message (Collapse)AuthorAgeFilesLines
* profiles/monitoring: move promtail to a profileFranck Cuny2023-05-121-6/+0
|
* profiles/monitoring: move node exporter to a profileFranck Cuny2023-05-121-1/+0
|
* hosts/carmel: fix proxy_pass configurationFranck Cuny2023-05-121-2/+2
|
* home/carmel: move router's configuration to a profileFranck Cuny2023-05-121-74/+0
|
* hosts/tahoe: move avahi configuration hereFranck Cuny2023-05-101-6/+0
|
* profiles/nginx: move common configuration to a profileFranck Cuny2023-05-091-6/+0
| | | | | | Both tahoe and carmel are using nginx, and we can simplify the configuration by moving common parts to the profile and have these hosts import it.
* 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: 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: 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-031-4/+77
| | | | | | | | | | | | 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.
* ref(profiles): get rid of all the profilesFranck Cuny2022-06-091-0/+9
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>