Update home authored by Lars Florian Meiendresch's avatar Lars Florian Meiendresch
......@@ -106,6 +106,19 @@ To make your application accessible, you'll want to route external traffic to th
A GitLab pipeline was developed inside the `.gitlab-ci.yml` for automatic testing and deploying on a stage and production server. After installing a GitLab runner with the `stage` and `main` tags on the according server and starting it with `cd / && gitlab-runner run`, code will be tested and deployed fully automated.
## Proposed (V-)Server Setup Guide
Assuming no existing server infrastructure is available, a Linux virtual private server (VPS) can be rented to host 19squared for approximately €4-11 per month. Such a VPS can effortlessly accommodate a larger 19squared instance.
The following steps outline a suggested installation process on a fresh VPS. It's important to note that this guide provides a general approach and there are other viable configuration options depending on specific requirements and preferences.
1. Install [Debian LTS](https://wiki.debian.org/LTS) on the VPS
2. Update Package List: `apt-get update`
3. Install Sudo: `apt-get install sudo`
4. Install [Docker Engine](https://docs.docker.com/engine/install/debian/)
5. Install [GitLab Runner](https://docs.gitlab.com/runner/install/)
6. Install Firewall: sudo apt-get install ufw && sudo ufw allow 5001 && sudo ufw enable && sudo ufw status
# Garbage Collector
The asset management system includes a garbage collector, accessible via the endpoint `/garbage_collector`. This mechanism is designed to reclaim storage capacity by periodically purging unreferenced assets. Integrating the garbage collector into a routine cron job schedule can optimise server storage utilisation.
......
......