Update PostgreSQL port configuration for deployment

Modify docker-compose.yml and DOCKER.md to map PostgreSQL host port 4523 to container port 4523, updating the DATABASE_URL environment variable accordingly.

Replit-Commit-Author: Agent
Replit-Commit-Session-Id: ae4037a0-2a6f-4530-9bac-79b543286bda
Replit-Commit-Checkpoint-Type: full_checkpoint
Replit-Commit-Screenshot-Url: https://storage.googleapis.com/screenshot-production-us-central1/397bca8c-984f-43ff-841a-10897aeb8140/ae4037a0-2a6f-4530-9bac-79b543286bda/rBcOjHB

.env.example

@@ -2,11 +2,11 @@
 PGDATABASE=socialflow
 PGUSER=socialflow
 PGPASSWORD=changeme
-PGPORT=5432
+PGPORT=4523
 PGHOST=postgres
 
 # URL de connexion complète (générée automatiquement dans Docker)
-DATABASE_URL=postgresql://socialflow:changeme@postgres:5432/socialflow
+DATABASE_URL=postgresql://socialflow:changeme@postgres:4523/socialflow
 
 # Configuration de l'application
 PORT=5555

DOCKER.md

@@ -47,7 +47,7 @@ docker-compose down
 
 ## 🌐 Accès
 
-- **PostgreSQL** : Accessible sur le port **4523** (mappé vers 5432 interne)
+- **PostgreSQL** : Accessible sur le port **4523** (interne et externe)
 - **Application** : Accessible via Nginx sur le réseau `nginx_default`
 
 ## 🔧 Architecture réseau
@@ -61,7 +61,7 @@ docker-compose down
 - Permet l'accès via Nginx et un domaine personnalisé
 
 ### Ports exposés
-- **PostgreSQL** : `4523:5432` (port hôte 4523 → port container 5432)
+- **PostgreSQL** : `4523:4523` (port hôte 4523 → port container 4523)
 - **Application** : Port 5555 interne (non exposé sur l'hôte, accessible via Nginx)
 
 ## 📝 Configuration Nginx

docker-compose.yml

@@ -7,11 +7,12 @@ services:
     container_name: socialflow-db
     restart: unless-stopped
     ports:
-      - "4523:5432"
+      - "4523:4523"
     environment:
       POSTGRES_DB: ${PGDATABASE:-socialflow}
       POSTGRES_USER: ${PGUSER:-socialflow}
       POSTGRES_PASSWORD: ${PGPASSWORD:-changeme}
+      PGPORT: 4523
     volumes:
       - postgres_data:/var/lib/postgresql/data
     networks:
@@ -33,7 +34,7 @@ services:
     environment:
       NODE_ENV: production
       PORT: 5555
-      DATABASE_URL: postgresql://${PGUSER:-socialflow}:${PGPASSWORD:-changeme}@postgres:5432/${PGDATABASE:-socialflow}
+      DATABASE_URL: postgresql://${PGUSER:-socialflow}:${PGPASSWORD:-changeme}@postgres:4523/${PGDATABASE:-socialflow}
       OPENROUTER_API_KEY: ${OPENROUTER_API_KEY}
       SESSION_SECRET: ${SESSION_SECRET:-your-secret-key-change-me}
       APP_URL: ${APP_URL:-http://localhost:5555}

replit.md

@@ -11,7 +11,7 @@ Preferred communication style: Simple, everyday language.
 ## Recent Changes
 
 ### October 17, 2025
-- **Docker Deployment Configuration**: Configured Docker Compose for private server deployment with PostgreSQL and application on same network. PostgreSQL exposed on port 4523:5432 for external access. Application runs on internal port 5555 (accessible via Nginx reverse proxy). Both PostgreSQL and app are on nginx_default external network and internal network for communication. Created comprehensive DOCKER.md documentation with setup instructions, network architecture explanation, and troubleshooting guide.
+- **Docker Deployment Configuration**: Configured Docker Compose for private server deployment with PostgreSQL and application on same network. PostgreSQL exposed on port 4523:4523 for external access. Application runs on internal port 5555 (accessible via Nginx reverse proxy). Both PostgreSQL and app are on nginx_default external network and internal network for communication. Created comprehensive DOCKER.md documentation with setup instructions, network architecture explanation, and troubleshooting guide.
 
 ### October 14, 2025
 - **Publication History Error Display Fix**: Fixed bug where publication history incorrectly displayed persistent errors for posts that failed initially but succeeded on retry. Problem: When a post failed, the `error` field was populated, but when the post was successfully republished, only `publishedAt` and `externalPostId` were updated without clearing the `error` field. Solution: Modified `schedulerService.publishPost()` to set `error: null` when publication succeeds, ensuring error messages are cleared from the history view after successful republication.