WIP: Update forge server sha

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.

configuration/services/gitea.nix

@@ -24,7 +24,7 @@
 
         environment = {
           DB_TYPE = "postgres";
-          DB_HOST = "gitea-postgres:5432";
+          DB_HOST = "localhost:5432";
           DB_NAME = "gitea";
           DB_USER = "gitea";
 

configuration/services/nextcloud.nix

@@ -19,7 +19,7 @@
         environment = {
           POSTGRES_DB = "nextcloud";
           POSTGRES_USER = "nextcloud";
-          POSTGRES_HOST = "nextcloud-postgres";
+          POSTGRES_HOST = "localhost";
           OVERWRITEPROTOCOL = "https";
           TRUSTED_PROXIES = "127.0.0.1";
         };

pkgs/minecraft/forge-server.nix

@@ -9,7 +9,7 @@ let
     url = "${mirror}/${version}/forge-${version}-installer.jar";
     curlOpts = "--globoff";
     # Forge doesn't seem to like newer shas
-    sha1 = "e97821e5431bdcaa46e12048769922e2cdb5e2e1";
+    sha1 = "sha1-oHNpyrgHluRrAXWZJg9j+OInAwA=";
   };
 
   unpackCmd = "mkdir -p src; cp $curSrc src/forge-${version}-installer.jar";