Create staging deployment
we are in the doing of setting a RSD up for HIFIS Community purposes. Because Community has no capabilities to host it, I asked 2 months ago, if HIFS Technology can do this. The time has come.
This project needs a staging deployment. To do that, we probably need an auth (like for software.hifis.net) for that. The software itself has a backend, where we need to test the login, etc.
The project consists of a docker compose stack (
docker-compose up -d for deploying), which would be the only dependencies in terms of software.
Additionally there needs to be some variables deployed (.env file). This can be set up once (with rare changes) or done via CI variables. I am fine with both. A SSL cert would be mandatory as well.
Not all things need to be handled. The backup service can be ignored for staging for now.
A SSH access to the staging would be helpful, but not needed.
privacy and imprint statement needed for staging?
- if yes, which?
general basic auth for staging server
- can you do that, or is this on the application side?
@christian.meessen anything i forgot?
- set up gilab ci
- set up server with docker-compose
- create and deploy SSL cert
- decide and implement deployment of env vars
- 80 > redirect 443
- 443 (https)
- add general basic auth for staging server