Prepare application for production deployment with robust authentication and routing

Introduce production-specific server entry point, setup local authentication with PostgreSQL sessions, and expose the application port in the Dockerfile.

Replit-Commit-Author: Agent
Replit-Commit-Session-Id: d396e5bd-e32d-4a20-9e7d-71e7102ddc6c
Replit-Commit-Checkpoint-Type: full_checkpoint
Replit-Commit-Screenshot-Url: https://storage.googleapis.com/screenshot-production-us-central1/1957c339-2757-4d1f-8e92-e9f71a1ce58e/d396e5bd-e32d-4a20-9e7d-71e7102ddc6c/CrwFq15
This commit is contained in:
michaelschal committed 2025-08-11 15:05:19 +00:00
1 parent 6a863cdaf2
commit c764fe6c15
4 files changed
+328 -1

No files matched your search

+1 -1
View File
@@ -1965,4 +1965,4 @@ class MemStorage implements IStorage {
// Use MemStorage in development, DatabaseStorage in production
const isProduction = process.env.NODE_ENV === 'production' && process.env.DATABASE_URL;
export const storage = isProduction ? new DatabaseStorage() : new MemStorage();
console.log(isProduction ? '🐳 Using PostgreSQL storage' : '🔧 Using in-memory storage for development');
console.log(isProduction ? '🐳 PRODUCTION: Using PostgreSQL storage' : '🔧 DEV: Using in-memory storage');