tlaternet/tlaternet-server
1
0
Fork 0
Code Issues 9 Pull requests Releases Activity
107 commits 4 branches 0 tags 154 MiB
Nix 94.8%
Rust 4.2%
Shell 1%
Find a file
Tristan Daniël Maat b6f39969cc
Fix podman hostnames 
It seems that with the newest version of podman container names are no
longer added as hostnames, meaning that any attempt to resolve
hostnames with the current config will fail. `localhost` is probably
more robust anyway, so we switch to that.

The bug manifests as broken services because nextcloud/gitea cannot
resolve their databases and nextcloud fails to resolve the php
server. To fix this a running system, the gitea and nextcloud database
configurations will need to be hand-edited, since those values are
only set on initialization, and not updated when changed later.
2022-01-08 02:19:04 +00:00
configuration Fix podman hostnames 2022-01-08 02:19:04 +00:00
keys Start reworking the server for nix flakes 2021-04-12 01:58:03 +01:00
lib voor-kia: Add client mods 2021-07-31 00:55:14 +01:00
modules nginx: Make VM testing easier by binding virtualHosts to localhost 2021-05-17 00:13:38 +01:00
pkgs update-mods.py: Fix issues revealed by 1.17 updates 2021-10-06 01:22:24 +01:00
.gitignore Start reworking the server for nix flakes 2021-04-12 01:58:03 +01:00
flake.lock Update to NixOS 21.11 2021-12-17 18:40:59 +00:00
flake.nix Update to NixOS 21.11 2021-12-17 18:40:59 +00: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.