bekkalokk/nginx: host .well-known #79

oysteikt · 2024-09-14T21:52:16+02:00

oysteikt commented

2024-09-14 21:52:16 +02:00

Moar bekkalokk mohoahaoha

Fixes: #100
Fixes: #153

Moar bekkalokk mohoahaoha Fixes: #100 Fixes: #153

oysteikt added 1 commit 2024-09-14 21:52:16 +02:00

bekkalokk/nginx: host .well-known 4e5093618e

felixalb requested changes 2024-09-14 22:16:37 +02:00

hosts/bekkalokk/configuration.nix Outdated

						
				@ -16,6 +16,7 @@

				    ./services/vaultwarden.nix

				    ./services/webmail

				    ./services/website

				    ./services/well-known

felixalb commented

2024-09-14 22:16:33 +02:00

I think this should be a part of the main ./services/website, as that is a more common / familiar way to think of and configure .well-known, rather than as a separate "service". This makes more sense semantically, though, as it doesn't really have anything to do with the website content

I think this should be a part of the main `./services/website`, as that is a more common / familiar way to think of and configure .well-known, rather than as a separate "service". This makes more sense semantically, though, as it doesn't really have anything to do with the website content

danio commented

2024-10-12 21:55:18 +02:00

I'm fine with it being like this. well-known is kind of a "thing" administrators have to manage

👍 1

hosts/bekkalokk/services/well-known/default.nix Outdated

						
				@ -0,0 +1,18 @@

				{ ... }:

				{

				  services.nginx.virtualHosts."www.pvv.ntnu.no".locations = {

felixalb commented

2024-09-14 22:08:56 +02:00

This should be served on all four www.pvv.ntnu.no pvv.ntnu.no www.pvv.org pvv.org, like the main website

This should be served on all four `www.pvv.ntnu.no pvv.ntnu.no www.pvv.org pvv.org`, like the main website

felixalb commented

2024-09-14 22:20:14 +02:00

Oops, nevermind, this is already handled because these other domains are already in the virtualHosts aliases, because this happens to be served from bekkalokk as well.
Might still want to specify aliases here as well, in case the http ingress is moved to another host than the main PHP app in the future.

Oops, nevermind, this is already handled because these other domains are already in the virtualHosts aliases, because this happens to be served from bekkalokk as well. Might still want to specify aliases here as well, in case the http ingress is moved to another host than the main PHP app in the future.

felixalb marked this conversation as resolved

hosts/bekkalokk/services/well-known/root/matrix/server Outdated

						
				@ -0,0 +1,3 @@

				{

				"m.server": "matrix.pvv.ntnu.no:443"

felixalb commented

2024-09-14 22:12:10 +02:00

This is currently unused, curl https://www.pvv.ntnu.no/.well-known/matrix/server is served by synapse itself, without the newlines.
Maybe it should exist as a fallback, in case synapse is down for some reason, to keep federation a little more happy?
I think we would need an nginx upstream acting like a load-balancer that prefers synapse but falls back to this static file somehow?

This is currently unused, `curl https://www.pvv.ntnu.no/.well-known/matrix/server` is served by synapse itself, without the newlines. Maybe it should exist as a fallback, in case synapse is down for some reason, to keep federation a little more happy? I think we would need an nginx `upstream` acting like a load-balancer that prefers synapse but falls back to this static file somehow?

danio commented

2024-10-12 22:00:14 +02:00

I dont think it matters in any case for keeping other servers happy, so we should just delete this

👍 1