Find a file

Tristan Daniël Maat 458f6c7f7b nginx: Avoid connection issues caused by IPv6 resolution If localhost is specified in the proxyPass url, nginx will happily resolve IPv6 addresses, even if the upstream doesn't support them. This can result in connection issues, especially with containers that don't support IPv6.		2021-05-16 01:34:03 +01:00
configuration	nginx: Avoid connection issues caused by IPv6 resolution	2021-05-16 01:34:03 +01:00
keys	Start reworking the server for nix flakes	2021-04-12 01:58:03 +01:00
lib	Add support for building minecraft modpacks	2021-04-25 06:23:08 +01:00
modules	Implement podman pods option	2021-04-12 01:58:05 +01:00
pkgs	minecraft: Add supplementaries mod	2021-05-11 22:13:31 +01:00
.gitignore	Start reworking the server for nix flakes	2021-04-12 01:58:03 +01:00
flake.lock	flake.lock: Update	2021-05-15 20:57:59 +01:00
flake.nix	flake: Fix remote install	2021-04-28 00:04:30 +01:00
LICENSE	Add LICENSE	2019-11-26 23:26:10 +00:00
README.md	README: Document deployment procedure	2021-04-28 00:53:05 +01:00

README.md

tlater.net server configuration

This is the NixOS configuration for tlater.net.

Testing

Building

Build the VM with:

nixos-rebuild build-vm --flake '.#vm'

Running

Note: M-2 will bring up a console for poweroff and such

Running should mostly be as simple as running the command the build script echos.

One caveat: create a larger disk image first. This can be done by running the following in the repository root:

qemu-img create -f qcow2 ./tlaternet.qcow2 20G

Everything else should be handled by the devShell.

New services

Whenever a new service is added, append an appropriate ,hostfwd=::3<port>:<port> to the QEMU_NET_OPTS specified in flake.nix to bind the service to a host port.

There is no way to test this without binding to the host port, sadly.

Deploying

Currently the deployment process is fully manual because there is no CI system.

Nix makes this fairly painless, though, it's simply:

nixos-rebuild switch --use-remote-sudo --target-host tlater.net --build-host localhost --flake .#tlaternet

This has the added benefit of running the build on the dev machine, which is 99% of the time much faster at building than the target (though artifact upload may take some time on slow connections).

Note that this also requires the current local user to also be present on the target host, as well as for this user to be in the target host's wheel group. See nix.trustedUsers.