@@ -143,14 +143,13 @@ While very common for development, it is very uncommon for production to only mo
## Deployment
For deployment to production, we actually use a more “classic” way (not Docker), namely webspace provided by the hoster lima-city, accessible via FTP. This means we get username and password from our hoster, log in using an FTP client (e.g. Filezilla) and copy all the files over.
For deployment to production, we actually use a more “classic” way (not Docker), namely webspace provided by the hoster lima-city, accessible via FTP. This means we get username and password from our hoster, log in using an FTP client and copy all the files over.
Why do we do it this way and not using Docker? Because the “classic” is what lima-city offers for free: They probably host one large Apache webserver, use the Apache feature of “virtual hosts“ to create a subdirectory for every user and hand out access to this. That way, they don't have to bother with Docker.
Why didn't we host the status page on our own infrastructure (and then using Docker)? Because it would be nice if the status page were still available even when the Fachschaft server is down.
