Projects:Server Migration: verschil tussen versies

Naar navigatie springen Naar zoeken springen
geen bewerkingssamenvatting
Geen bewerkingssamenvatting
Geen bewerkingssamenvatting
 
(4 tussenliggende versies door dezelfde gebruiker niet weergegeven)
Regel 3: Regel 3:
A quick summary:
A quick summary:


== The old server (corvus) ==
==The old server (corvus)==


*40GB HDD (yes, not SSD) and 2GB RAM
*40GB HDD (yes, not SSD) and 2GB RAM
*Runs mailu as the mailserver (basically a flask webapp managing postfix and dovecot), picked at the time because it was light on resources
*Runs mailu as the mailserver (basically a flask webapp managing postfix and dovecot), picked at the time because it was light on resources. Slightly modified to play ball with the mailinglist, making upgrades painful.
*Mailman3, running the mailing list. There are problems as sqlite has been chosen, again, due to resouce constraints. Migrating this to mysql or postgres will be either a headache or next to impossible (within a reasonable timeframe).
*Mailman3, running the mailing list. There are problems as sqlite has been chosen, again, due to resouce constraints. Migrating this to mysql or postgres will be either a headache or next to impossible (within a reasonable timeframe).
*Docker, minus iptables
*Docker, minus iptables
Regel 13: Regel 13:
*Webhosting using php-fpm (7.3) and nginx
*Webhosting using php-fpm (7.3) and nginx


== The new server (altair) ==
==The new server (altair)==


*80GB SSD, 8GB RAM
*80GB SSD, 8GB RAM
Regel 22: Regel 22:
*BIND for dynamic updates of the space connection
*BIND for dynamic updates of the space connection
*A proxy method delivering the DNS-traffic for the respective zones to the right server
*A proxy method delivering the DNS-traffic for the respective zones to the right server
*Webhosting using php-fpm (8.2) and nginx  
*Webhosting using php-fpm (8.2) and nginx


== Trivia ==
==Trivia==


* The new server hostname's FQDN is altair.hackerspacenijmegen.nl
*The new server hostname's FQDN is altair.hackerspacenijmegen.nl
* stichtinghackerspacenijmegen.nl was only used in the previous setup, meaning this domain could potentially be ditched
*stichtinghackerspacenijmegen.nl was only used in the previous setup, meaning this domain could potentially be ditched
* hsnmgn.nl is also not (widely) known, meaning that we also might consider to ditch that one as well
*hsnmgn.nl is also not (widely) known, meaning that we also might consider to ditch that one as well
*This combined will save us '''€254 a year'''.


Update: the migration is complete, but there are some quirks:


At the time of writing, only the website part needs to be moved. The mail setup has already been synchronized; when the reverse DNS has been updated I will pull the plug.
* <s>For some reason, MediaWiki doesn't send emails anymore. There are no logs, there are no delivery attempts at the mailserver and the debug log doesn't even mention the email module being invoked. I triple checked the configuration, but it's seems okay. I am clueless at this point.</s>  28-02-2023: mrngm and I looked into this issue again and it has now been solved.
* The spacestate still uploads the json file to the old server. We need to migrate that ASAP, I proposed a new solution to Sjors.
* The mailing list should work, but needs to be tested thoroughly.
 
 
docs.hackerspacenijmegen.nl, the old WordPress homepage and the unused WordPress at stichtinghackerspacenijmegen.nl have been retired. A copy of the webroot and database of the respective websites can be found on the new server.☃☃


If everything goes to plan, we can cancel the old server contract within 14 days.
If everything goes to plan, we can cancel the old server contract within 14 days.
<br />
<br />

Navigatiemenu