@@ -140,7 +140,14 @@ While very common for development, it is very uncommon for production to only mo
## Deployment
<!-- TODO -->
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.
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.
@@ -170,7 +177,7 @@ This is why we have chosen a more convoluted-looking directory structure instead
### Couldn't we have done this entirely on the client?
<!-- CORS, maybe link LiveOverflow -->
<!-- TODO: CORS, maybe link LiveOverflow -->
## License
@@ -186,3 +193,4 @@ For details and authorship information, see the linked license files.
## Footnotes
[^1]:That is, unless you make a configuration error or run a server without PHP capabilities. This means: Yes, you can technically store secrets in PHP files, they should not be sent to the client – but if you ever do that, make sure you verify everything works as it should.
[^2]:Jakob gets commission if you happen to pay for a service at lima-city via this link. Not paid, Jakob just actually likes lima-city.
