Configure isolated production deployment

.gitea/workflows/deploy.yml

@@ -0,0 +1,18 @@
+name: Deploy PROD
+
+on:
+  push:
+    branches: [main]
+
+jobs:
+  deploy:
+    runs-on: prod
+    steps:
+      - name: Deploy Akademia on production host
+        run: |
+          set +e
+          /opt/akademia/deploy-prod.sh
+          rc=$?
+          echo "----- /opt/akademia/deploy.log (tail) -----"
+          tail -n 30 /opt/akademia/deploy.log
+          exit $rc

docker-compose.prod.yml

@@ -22,7 +22,6 @@
 services:
   postgres:
     image: postgres:16
-    container_name: webinar-postgres
     restart: unless-stopped
     environment:
       POSTGRES_DB: ${DB_NAME}
@@ -44,7 +43,6 @@ services:
 
   minio:
     image: minio/minio:RELEASE.2024-12-18T13-15-44Z
-    container_name: webinar-minio
     restart: unless-stopped
     command: server /data --console-address ":9001"
     environment:
@@ -70,7 +68,6 @@ services:
     build:
       context: ./backend
     image: webinar-backend:${APP_VERSION:-latest}
-    container_name: webinar-backend
     restart: unless-stopped
     depends_on:
       postgres:
@@ -123,7 +120,6 @@ services:
     build:
       context: ./frontend
     image: webinar-frontend:${APP_VERSION:-latest}
-    container_name: webinar-frontend
     restart: unless-stopped
     depends_on:
       backend:
@@ -158,7 +154,6 @@ services:
     # laczy sie sciezka `/rtc/v1`, ktorej serwer 1.8 nie zna: sala wyglada na
     # dzialajaca, ale nie plynie ani obraz, ani dzwiek.
     image: livekit/livekit-server:v1.13
-    container_name: webinar-livekit
     profiles: ["livekit"]
     restart: unless-stopped
     command: --config /etc/livekit.yaml
@@ -194,7 +189,6 @@ services:
   # timeoutem przy poprawnie dzialajacym serwerze i dzialajacych spotkaniach.
   redis:
     image: redis:7-alpine
-    container_name: webinar-redis
     profiles: ["livekit"]
     restart: unless-stopped
     command: redis-server --save "" --appendonly no
@@ -218,7 +212,6 @@ services:
     # Wersja przypieta, nie `latest`: obraz Egress zmienia sie czesto,
     # a niezgodnosc z serwerem ujawnia sie dopiero przy probie nagrania.
     image: livekit/egress:v1.9
-    container_name: webinar-livekit-egress
     profiles: ["livekit"]
     restart: unless-stopped
     depends_on:
@@ -255,7 +248,6 @@ services:
   # czesc osob dolaczy do pokoju i nie zobaczy ani nie uslyszy nikogo.
   coturn:
     image: coturn/coturn:4.6
-    container_name: webinar-coturn
     profiles: ["livekit"]
     restart: unless-stopped
     # network_mode: host, bo TURN musi widziec prawdziwe adresy IP: za NAT-em