aboutsummaryrefslogtreecommitdiff
path: root/hosts/carmel/services.nix (unfollow)
Commit message (Collapse)AuthorFilesLines
2023-12-08delete configuration for old machinesFranck Cuny1-18/+0
These machines are gone, no need to keep the configuration around.
2023-05-12profiles/monitoring: move promtail to a profileFranck Cuny1-6/+0
2023-05-12profiles/monitoring: move node exporter to a profileFranck Cuny1-1/+0
2023-05-12hosts/carmel: fix proxy_pass configurationFranck Cuny1-2/+2
2023-05-12home/carmel: move router's configuration to a profileFranck Cuny1-74/+0
2023-05-10hosts/tahoe: move avahi configuration hereFranck Cuny1-6/+0
2023-05-09profiles/nginx: move common configuration to a profileFranck Cuny1-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.
2023-04-23hosts/carmel: enable promtailFranck Cuny1-1/+5
2023-04-23modules/monitoring: consolidate all monitoring services togetherFranck Cuny1-1/+1
This will help to organize and structure monitoring modules a bit better.
2023-04-15hosts/carmel: don't log dns queries in dnsmasqFranck Cuny1-1/+0
This is way too verbose
2023-04-15hosts/carmel: start dnsmasq once network interfaces are onlineFranck Cuny1-0/+7
2023-04-06hosts/carmel: serve the leases on port 8067Franck Cuny1-4/+7
Bind to the wireguard interface, and use the port 8067 (67 is the port used for DHCP requests).
2023-04-06hosts/carmel: run dnsmasql-to-html when leases changeFranck Cuny1-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.
2023-04-03hosts/carmel: more options for dnsmasqFranck Cuny1-0/+2
2023-04-03hosts/carmel: add a few more options for dnsmasqFranck Cuny1-0/+6
2023-04-03hosts/carmel: enable prometheus exporter for DNSmasqFranck Cuny1-0/+5
2023-04-03hosts/carmel: reconfigure the host as a routerFranck Cuny1-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.
2022-06-09ref(profiles): get rid of all the profilesFranck Cuny1-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>