add coreos deployment

Author: Toni000

.env.dev

@@ -4,14 +4,14 @@ IMAGE_TAG=dev
 
 # backend config for local development (also: see backend/dps_training_k/.env)
 DEBUG=True
-SECRET_KEY=abcdefg
+SECRET_KEY=replace-me-with-a-long-random-secret
 ALLOWED_HOSTS=*,
 INTERNAL_IPS=127.0.0.1
-DATABASE_URL=postgres://dps:dps@K-dPS-postgres:5432/dps
+DATABASE_URL=postgres://dps:replace-me-with-a-db-password@K-dPS-postgres:5432/dps
 REDIS_URL=redis://K-dPS-redis:6379
 CACHE_URL=redis://K-dPS-redis:6379
 CHANNEL_REDIS=True
 
 POSTGRES_DB=dps
 POSTGRES_USER=dps
-POSTGRES_PASSWORD=dps
+POSTGRES_PASSWORD=replace-me-with-a-db-password

.env.prod

@@ -4,14 +4,14 @@ IMAGE_TAG=latest
 
 # backend config for production
 DEBUG=False
-SECRET_KEY=0Lf6rayQccUBK7GxM32HZCTj995bFij3
+SECRET_KEY=replace-me-with-a-long-random-secret
 ALLOWED_HOSTS=*,
 INTERNAL_IPS=127.0.0.1
-DATABASE_URL=postgres://dps:ozuCk0rrF6nzkzcR1TQMR93m3iYUzMBG@K-dPS-postgres:5432/dps
+DATABASE_URL=postgres://dps:replace-me-with-a-db-password@K-dPS-postgres:5432/dps
 REDIS_URL=redis://K-dPS-redis:6379
 CACHE_URL=redis://K-dPS-redis:6379
 CHANNEL_REDIS=True
 
 POSTGRES_DB=dps
 POSTGRES_USER=dps
-POSTGRES_PASSWORD=ozuCk0rrF6nzkzcR1TQMR93m3iYUzMBG
+POSTGRES_PASSWORD=replace-me-with-a-db-password

.gitignore

@@ -3,3 +3,4 @@ backend/.vscode/settings.json
 .idea/
 .vscode/launch.json
 backend/dps_training_k/restart_backend.sh
+deployment/coreos/secrets/

backend/README.md

@@ -46,7 +46,7 @@ docker compose --env-file .env.<prod/dev> up --build
 Optionally, to access the database, create a superuser account:
 
 ```bash
-docker exec -it K-dPS-django python manage.py createsuperuser
+docker exec -it kdps-django python manage.py createsuperuser
 ```
 
 Afterwards, you can log into the admin interface at e.g. `http://localhost:80/admin/`<br/>
@@ -58,25 +58,25 @@ Note: this is only available if DEBUG = true, which is the case in the dev envir
 
 When changing models, you need to create migrations in order to update existing databases.
 
-- Create new migrations: `docker exec -it K-dPS-django python manage.py makemigrations`
-- Optionally, if you have conflicting migrations: `docker exec -it K-dPS-django python manage.py migrate --merge`
-- Execute these migrations to update the database: `docker exec -it K-dPS-django python manage.py migrate`
+- Create new migrations: `docker exec -it kdps-django python manage.py makemigrations`
+- Optionally, if you have conflicting migrations: `docker exec -it kdps-django python manage.py migrate --merge`
+- Execute these migrations to update the database: `docker exec -it kdps-django python manage.py migrate`
 
 ### Running Tests
 
 - start docker container with docker compose(see Running the project using Docker)
 - wait until Application Startup is Completed
-- run: `docker exec -it K-dPS-django python manage.py test`
+- run: `docker exec -it kdps-django python manage.py test`
 
 ### Working with Fixtures
 
 Example given for creating the "patient_states.json" fixture containing all patientstates, statetransitions, subconditions and logicnodes.
 
-- clear database of the wanted models via e.g. `docker exec -it K-dPS-django python manage.py flush`
-- fill database with data you want to export as fixture: `docker exec -it K-dPS-django python manage.py import_patient_states`
+- clear database of the wanted models via e.g. `docker exec -it kdps-django python manage.py flush`
+- fill database with data you want to export as fixture: `docker exec -it kdps-django python manage.py import_patient_states`
 - create fixture:
-    - `docker exec -it K-dPS-django bash`
+    - `docker exec -it kdps-django bash`
     - `export PYTHONIOENCODING=utf8`
     - `python manage.py dumpdata template.patientstate template.statetransition template.subcondition template.logicnode > 
     data/fixtures/patient_states.json`
-- now you can load it: `docker exec -it K-dPS-django python manage.py loaddata patient_states.json`
+- now you can load it: `docker exec -it kdps-django python manage.py loaddata patient_states.json`

backend/dps_training_k/.env.dev

@@ -2,14 +2,14 @@
 RUN_CONFIG=dev
 
 DEBUG=True
-SECRET_KEY=abcdefg
+SECRET_KEY=replace-me-with-a-long-random-secret
 ALLOWED_HOSTS=*,
 INTERNAL_IPS=127.0.0.1
-DATABASE_URL=postgres://dps:dps@K-dPS-postgres:5432/dps
-REDIS_URL=redis://K-dPS-redis:6379
-CACHE_URL=redis://K-dPS-redis:6379
+DATABASE_URL=postgres://dps:replace-me-with-a-db-password@kdps-postgres:5432/dps
+REDIS_URL=redis://kdps-redis:6379
+CACHE_URL=redis://kdps-redis:6379
 CHANNEL_REDIS=True
 
 POSTGRES_DB=dps
 POSTGRES_USER=dps
-POSTGRES_PASSWORD=dps
+POSTGRES_PASSWORD=replace-me-with-a-db-password

backend/dps_training_k/.env.prod

@@ -2,14 +2,14 @@
 RUN_CONFIG=prod
 
 DEBUG=False
-SECRET_KEY=0Lf6rayQccUBK7GxM32HZCTj995bFij3
+SECRET_KEY=replace-me-with-a-long-random-secret
 ALLOWED_HOSTS=*,
 INTERNAL_IPS=127.0.0.1
-DATABASE_URL=postgres://dps:ozuCk0rrF6nzkzcR1TQMR93m3iYUzMBG@K-dPS-postgres:5432/dps
-REDIS_URL=redis://K-dPS-redis:6379
-CACHE_URL=redis://K-dPS-redis:6379
+DATABASE_URL=postgres://dps:replace-me-with-a-db-password@kdps-postgres:5432/dps
+REDIS_URL=redis://kdps-redis:6379
+CACHE_URL=redis://kdps-redis:6379
 CHANNEL_REDIS=True
 
 POSTGRES_DB=dps
 POSTGRES_USER=dps
-POSTGRES_PASSWORD=ozuCk0rrF6nzkzcR1TQMR93m3iYUzMBG
+POSTGRES_PASSWORD=replace-me-with-a-db-password

backend/dps_training_k/configuration/settings.py

@@ -34,7 +34,6 @@
 CORS_ORIGIN_ALLOW_ALL = DEBUG
 CORS_ALLOWED_ORIGINS = [
     "https://klinik-dps.de",
-    "https://www.klinik-dps.de",
     "http://localhost",
 ]
 RUN_CONFIG = env.str("RUN_CONFIG", default="dev")
@@ -189,6 +188,6 @@
 DATA_ROOT = os.path.join(BASE_DIR, "data")
 
 # Redis connection settings
-REDIS_HOST = "K-dPS-redis"
+REDIS_HOST = "kdps-redis"
 REDIS_PORT = 6379
 REDIS_DB = 0

backend/dps_training_k/deployment/nginx/nginx.conf

@@ -2,15 +2,15 @@ server {
     listen 80;
 
     location /api {
-        proxy_pass http://django:8000/api;
+        proxy_pass http://kdps-django:8000/api;
         proxy_set_header Host $host;
         proxy_set_header X-Real-IP $remote_addr;
         proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
         proxy_set_header X-Forwarded-Proto $scheme;
     }
 
     location /ws {
-        proxy_pass http://django:8000/ws;
+        proxy_pass http://kdps-django:8000/ws;
         proxy_http_version 1.1;
         proxy_set_header Upgrade $http_upgrade;
         proxy_set_header Connection "Upgrade";
@@ -22,7 +22,7 @@ server {
 
     # For the admin interface
     location /admin {
-        proxy_pass http://django:8000/admin;
+        proxy_pass http://kdps-django:8000/admin;
         proxy_set_header Host $host;
         proxy_set_header X-Real-IP $remote_addr;
         proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
@@ -31,4 +31,4 @@ server {
     location /static/ {
         alias /app/staticfiles/;
     }
-}
+}

backend/dps_training_k/deployment/nginx/nginx_deploy_dev.conf

@@ -2,23 +2,23 @@ server {
     listen 80;
 
     location / {
-        proxy_pass http://frontend:5173;
+        proxy_pass http://kdps-frontend:5173;
         proxy_set_header Host $host;
         proxy_set_header X-Real-IP $remote_addr;
         proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
         proxy_set_header X-Forwarded-Proto $scheme;
     }
 
     location /api {
-        proxy_pass http://django:8000/api;
+        proxy_pass http://kdps-django:8000/api;
         proxy_set_header Host $host;
         proxy_set_header X-Real-IP $remote_addr;
         proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
         proxy_set_header X-Forwarded-Proto $scheme;
     }
 
     location /ws {
-        proxy_pass http://django:8000/ws;
+        proxy_pass http://kdps-django:8000/ws;
         proxy_http_version 1.1;
         proxy_set_header Upgrade $http_upgrade;
         proxy_set_header Connection "Upgrade";
@@ -30,7 +30,7 @@ server {
 
     # For the admin interface
     location /admin {
-        proxy_pass http://django:8000/admin;
+        proxy_pass http://kdps-django:8000/admin;
         proxy_set_header Host $host;
         proxy_set_header X-Real-IP $remote_addr;
         proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
@@ -39,4 +39,4 @@ server {
     location /static/ {
         alias /app/staticfiles/;
     }
-}
+}

backend/dps_training_k/deployment/nginx/nginx_deploy_prod.conf

@@ -1,33 +1,33 @@
 server {
     listen 80;
-    server_name klinik-dps.de www.klinik-dps.de;
+    server_name klinik-dps.de;
     location / {
         return 301 https://$host$request_uri;
     }
 }
 server {
     listen 443 ssl;
-    server_name klinik-dps.de www.klinik-dps.de;
+    server_name klinik-dps.de;
 
-    ssl_certificate /etc/nginx/ssl/fullchain.pem;
-    ssl_certificate_key /etc/nginx/ssl/privkey.pem;
+    ssl_certificate /etc/letsencrypt/live/klinik-dps.de/fullchain.pem;
+    ssl_certificate_key /etc/letsencrypt/live/klinik-dps.de/privkey.pem;
 
     location / {
-        proxy_pass http://frontend:5173;
+        proxy_pass http://kdps-frontend:5173;
         proxy_set_header Host $host;
         proxy_set_header X-Real-IP $remote_addr;
         proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
         proxy_set_header X-Forwarded-Proto $scheme;
     }
     location /api {
-        proxy_pass http://django:8000/api;
+        proxy_pass http://kdps-django:8000/api;
         proxy_set_header Host $host;
         proxy_set_header X-Real-IP $remote_addr;
         proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
         proxy_set_header X-Forwarded-Proto $scheme;
     }
     location /ws {
-        proxy_pass http://django:8000/ws;
+        proxy_pass http://kdps-django:8000/ws;
         proxy_http_version 1.1;
         proxy_set_header Upgrade $http_upgrade;
         proxy_set_header Connection "Upgrade";
@@ -36,4 +36,4 @@ server {
         proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
         proxy_set_header X-Forwarded-Proto $scheme;
     }
-}
+}