Move web server definition to infra #67

Niols · 2025-01-16T13:30:58+01:00

Niols commented

2025-01-16 13:30:58 +01:00

No description provided.

fricklerhandwerk approved these changes

2025-01-20 09:36:40 +01:00

fricklerhandwerk requested changes

2025-01-20 11:11:49 +01:00

infra/vm02117/website.nix Outdated

					
				@ -0,0 +41,4 @@

				  services.nginx.virtualHosts."www.fediversity.eu" = {

				    enableACME = true;

				    forceSSL = true;

				    root = "${(import ../../website { }).build}";

Actually this doesn't apply any more since wordpress. @bjornw where's the infra code for that btw? It should actually live here, otherwise the next deployment will iron over that config.

Yes, I indeed only moved the configuration, but I didn't try to update it. It had been said that this VM and this infrastructure would still be used for dev documentation, or something like that. I think the Wordpress VM hosting www.fediversity.eu is somewhere else. @bjornw > Can you confirm?

@fricklerhandwerk> What's your preferred way to handle this? Should I just remove everything from the configuration, like the whole website.nix file, basically, and make it only a regular VM waiting for a purpose? Should I also remove the website/ directory at the root?

@fricklerhandwerk> What's your preferred way to handle this? Should I just remove everything from the configuration, like the whole `website.nix` file, basically, and make it only a regular VM waiting for a purpose? Should I also remove the `website/` directory at the root?

The WordPress website is run on vm02211. WordPress uses wp-config.php for settings such as the db. The theme we're using is a the default theme "designed" inside of WordPress' editor. I presume the config for this is part of the db. Afaik there is no infra code, deployment was done by Koen. @koen did you add infra code to the repo for the Fediversity website?

@fricklerhandwerk> WDYT, can we merge this in the meantime, as the PR achieves its purpose, namely to move the code from one place to the other while keeping it working just the same, and we can change things later when @koen answers and we know better what to do with vm02117?

Let's just remove the nginx config for the website and wire up the rest later.

Happy with 0cf82bcf4efca209d19bfcc3423476bbb0afe89f?

I think so. Just mentioning @kevin @koen that the OIDF DNS seems to have been running on that and it currently doesn't work. I doubt it should be on that machine managed by Fediversity, and would prefer not to have it so we don't break unrelated things as we do things.

I think so. Just mentioning @kevin @koen that the OIDF DNS seems to have been running on that and it currently doesn't work. I doubt it *should* be on that machine managed by Fediversity, and would prefer not to have it so we don't break unrelated things as we do things.

Rows
Columns

Move web server definition to infra #67

Move web server definition to `infra` #67