remove truelove-specific workadventure

This removes the special configuration to make our workadventure useable
for the truelove event and reverts it to just run at void.hacc.space
without authentication etc.

Tbh, not sure if that's actually what we want — do we need a running
workadventure instance at all? Or should we just remove the entire container?
keep-around/16245e830fc9eeb078c051fb3960c6d2e780d9b9
stuebinm 2022-01-01 20:03:32 +01:00
parent 9b38e5fba1
commit 16245e830f
No known key found for this signature in database
GPG Key ID: 8FBE8AAD32FA12B7
1 changed files with 3 additions and 8 deletions

View File

@ -37,17 +37,12 @@ in
locations."/" = {
proxyPass = "http://192.168.150.3";
proxyWebsockets = true;
extraConfig = ''
allow 23.88.116.81;
allow 2a01:4f8:c17:86ba::1;
deny all;
'';
};
enableACME = true;
forceSSL = true;
};
containers.wa-truelove = {
containers.wa-void = {
autoStart = true;
privateNetwork = true;
@ -65,13 +60,13 @@ in
((import sources.nix-hexchen) {}).profiles.nopersist
];
services.workadventure."truelove" = {
services.workadventure."void" = {
packageset = (import wapkgs {inherit pkgs;}).workadventure-xce;
nginx = {
default = true;
domain = "https://true-love.world.hacc.space";
domain = "https://void.hacc.space";
};
frontend.startRoomUrl = "/_/global/localhost/maps/main.json";