c3lf/c3lf-system-3
9
0
Fork 0
Code Issues 55 Pull requests Projects 2 Releases Wiki Activity Actions

extend information about the online instances to the README.md
All checks were successful
/ test (push) Successful in 2m21s
Details
/ deploy (push) Successful in 4m30s
Details

Browse source
This commit is contained in:
j3d1 2025-03-16 15:31:46 +01:00
parent 8d45fef627
commit 9def22a836
1 changed files with 6 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
README.md
View file

@ -127,7 +127,6 @@ docker exec -it c3lf-sys3-dev-core-1 ./manage.py test`
*will include postfix, mariadb, redis, nginx and the ability to test sending mails, receiving mail and websocket based *will include postfix, mariadb, redis, nginx and the ability to test sending mails, receiving mail and websocket based
realiteme updates in the frontend. the last step in verification before deploying to the staging system using ansible* realiteme updates in the frontend. the last step in verification before deploying to the staging system using ansible*
## Online Instances ## Online Instances
These are deployed using `deploy/ansible/playbooks/deploy-c3lf-sys3.yml` and follow a specific git branch. These are deployed using `deploy/ansible/playbooks/deploy-c3lf-sys3.yml` and follow a specific git branch.
@ -151,4 +150,9 @@ This is the **'production' system** and should strictly follow the staging syste
| **Debug Mode** | on | | **Debug Mode** | on |
This system ist automatically updated by [git.hannover.ccc.de](https://git.hannover.ccc.de/c3lf/c3lf-system-3/) whenever This system ist automatically updated by [git.hannover.ccc.de](https://git.hannover.ccc.de/c3lf/c3lf-system-3/) whenever
a commit is pushed to the 'testing' branch and the backend tests passed. a commit is pushed to the 'testing' branch and the backend tests passed.
**WARNING: allthough this is the staging system, it is fully functional and contains a copy of the 'production' data, so
do not for example reply to tickets for testing purposes as the system WILL SEND AN EMAIL to the person who originally
created it. If you want to test something like that, first create you own test ticket by sending an email to
`<event>@staging.c3lf.de`**