Dockerfile

.env.example

@@ -1,8 +1,12 @@
-# Server Configuration
+# Server Container Configuration (Internal application listener)
 PORT=3000
 NODE_ENV=production
 
-# PostgreSQL Connection String (Coolify / Managed Postgres / Docker)
+# Host Port Mappings for Docker / Coolify (Prevents conflict if host ports 3000 or 5432 are occupied)
+HOST_PORT=8080
+POSTGRES_HOST_PORT=5433
+
+# PostgreSQL Database Configuration
 DATABASE_URL=postgresql://postgres:postgres_secure_pass_2026@postgres:5432/balance_sheet_db
 POSTGRES_PASSWORD=postgres_secure_pass_2026
 

COOLIFY.md

@@ -2,7 +2,7 @@
 
 This application consists of:
 1. **Server Side**: Node.js + Express backend (`server.ts`) serving REST APIs, managing authentication, ledger reconciliation, audit logs, FX rates, and financial reports.
-2. **Database**: PostgreSQL (via `pg` connection pool) with automatic JSON fall-back backup.
+2. **Database**: PostgreSQL (via `pg` connection pool) with automatic JSON fallback backup.
 3. **Frontend**: React SPA served directly via Express in production.
 
 ---
@@ -19,6 +19,8 @@ This application consists of:
    ```env
    NODE_ENV=production
    PORT=3000
+   HOST_PORT=8080             # Customize if host port 3000 is occupied by another app
+   POSTGRES_HOST_PORT=5433    # Customize if host port 5432 is occupied by another database
    POSTGRES_PASSWORD=your_custom_secure_password
    ```
 3. **Deploy**:
@@ -45,9 +47,11 @@ If you prefer using Coolify's built-in managed PostgreSQL database resource:
 
 ---
 
-## 2. Server-Side Architecture Details
+## 2. Server-Side Architecture & Port Configuration
 
+- **Internal Container Port**: Application listens on `3000` inside the container.
+- **Conflict Prevention**: Host port mappings in `docker-compose.yml` use `${HOST_PORT:-8080}:3000` and `${POSTGRES_HOST_PORT:-5433}:5432`. If port 3000 or 5432 is already used by another app on your server, simply set `HOST_PORT` or `POSTGRES_HOST_PORT` in your `.env` to any available port (e.g. `8080`, `8081`, `5433`).
 - **Automatic Table Creation**: On server boot, the backend runs `initPgDatabase()` to verify/create `app_portal_state`.
-- **Automatic State Recovery**: If PostgreSQL contains existing data, the portal state is loaded directly from PostgreSQL. If empty, baseline seed data is written to PostgreSQL.
+- **Automatic State Recovery**: If PostgreSQL contains existing data, portal state is loaded directly from PostgreSQL.
 - **Resilient Fallback**: If `DATABASE_URL` is omitted, the app gracefully operates using persistent JSON storage (`/app/data/portal-data.json`).
 - **Health Check**: Express exposes `GET /api/health` for Docker container monitoring.

Dockerfile.txt

@@ -0,0 +1,55 @@
+# ==============================================================================
+# Multi-stage Dockerfile for Coolify & Containerized Environments
+# ==============================================================================
+
+# ------------------------------------------------------------------------------
+# Stage 1: Build Stage
+# ------------------------------------------------------------------------------
+FROM node:20-alpine AS builder
+
+WORKDIR /app
+
+# Copy package manifests
+COPY package*.json ./
+
+# Install dependencies needed for vite & esbuild build
+RUN npm install
+
+# Copy full application source code
+COPY . .
+
+# Run production build (vite client build + esbuild server compilation)
+RUN npm run build
+
+# ------------------------------------------------------------------------------
+# Stage 2: Production Runner Stage
+# ------------------------------------------------------------------------------
+FROM node:20-alpine AS runner
+
+WORKDIR /app
+
+ENV NODE_ENV=production
+ENV PORT=3000
+ENV DATA_PATH=/app/data/portal-data.json
+
+# Copy package manifests
+COPY package*.json ./
+
+# Install production dependencies only
+RUN npm install --omit=dev && npm cache clean --force
+
+# Copy compiled distribution output from builder stage
+COPY --from=builder /app/dist ./dist
+
+# Create persistent data directory
+RUN mkdir -p /app/data
+
+# Expose server port (default 3000)
+EXPOSE 3000
+
+# Healthcheck to verify Express server status
+HEALTHCHECK --interval=30s --timeout=5s --start-period=10s --retries=3 \
+  CMD wget --no-verbose --tries=1 --spider http://localhost:3000/api/health || exit 1
+
+# Start production application server
+CMD ["node", "dist/server.cjs"]

README.md

@@ -1,20 +1,62 @@
-<div align="center">
-<img width="1200" height="475" alt="GHBanner" src="https://ai.google.dev/static/site-assets/images/share-ais-513315318.png" />
-</div>
+# Commercial Banking Balance Sheet & Financial Reporting Portal
 
-# Run and deploy your AI Studio app
+A full-stack enterprise web application built for multi-branch balance sheet consolidation, trial balance ledger verification, automated accounting reconciliation, double-entry bookkeeping, and executive financial reporting.
 
-This contains everything you need to run your app locally.
+---
 
-View your app in AI Studio: https://ai.studio/apps/1d635da8-bc7b-4711-8a8b-119cb50ea598
+## 🚀 Key Features
 
-## Run Locally
+- **Multi-Branch Operations**: Head Office Admin, Branch Users, Maker-Checker authorization matrix.
+- **Server-Side Architecture**: Express backend (`server.ts`) handling state management, calculations, audit logging, and email dispatches.
+- **PostgreSQL & Fallback Storage**: Connects to PostgreSQL via `pg` connection pool with automatic fallback to JSON data persistence (`/app/data/portal-data.json`).
+- **Containerized Deployment**: Ready for Docker, Docker Compose, and **Coolify** self-hosting.
 
-**Prerequisites:**  Node.js
+---
 
+## 📁 Repository Structure & Key Configuration Files
 
-1. Install dependencies:
-   `npm install`
-2. Set the `GEMINI_API_KEY` in [.env.local](.env.local) to your Gemini API key
-3. Run the app:
-   `npm run dev`
+| File | Description |
+| :--- | :--- |
+| `Dockerfile` & `dockerfile` | Multi-stage production container build (Vite client + Express CJS server). |
+| `docker-compose.yml` | Full-stack orchestration (App container + PostgreSQL 16 container with configurable host port mapping). |
+| `.dockerignore` | Defines context exclusions for slim Docker image builds. |
+| `.env.example` | Template environment variables (`DATABASE_URL`, `PORT`, `HOST_PORT`, `POSTGRES_HOST_PORT`, `DATA_PATH`). |
+| `COOLIFY.md` | Complete deployment guide for Coolify platform & managed databases. |
+| `server.ts` | Express server entry point with PostgreSQL initialization and REST API routes. |
+
+---
+
+## 🛠️ Local Development & Running via Docker
+
+### 1. Run via Docker Compose (With PostgreSQL & Configurable Host Ports)
+```bash
+docker-compose up --build -d
+```
+By default, the application will be accessible on host port `http://localhost:8080` (mapped to internal container port `3000`), and PostgreSQL on host port `5433` (mapped to internal container port `5432`).
+
+If host ports `3000` or `5432` are already used by another application, set custom host ports in `.env`:
+```env
+HOST_PORT=8080
+POSTGRES_HOST_PORT=5433
+```
+
+### 2. Run via Docker CLI
+```bash
+docker build -t balance-sheet-portal .
+docker run -p 8080:3000 -v portal_data:/app/data balance-sheet-portal
+```
+
+### 3. Native Node.js Development
+```bash
+# Install dependencies
+npm install
+
+# Start development server (Express + Vite hot reload)
+npm run dev
+```
+
+---
+
+## ☁️ Deployment on Coolify
+
+Refer to [`COOLIFY.md`](./COOLIFY.md) for step-by-step instructions on deploying via Docker Compose or Coolify Managed PostgreSQL.

docker-compose.yml

@@ -11,7 +11,8 @@ services:
       POSTGRES_USER: postgres
       POSTGRES_PASSWORD: ${POSTGRES_PASSWORD:-postgres_secure_pass_2026}
     ports:
-      - "5432:5432"
+      # Use POSTGRES_HOST_PORT (default 5433) to prevent conflicts if host port 5432 is already occupied
+      - "${POSTGRES_HOST_PORT:-5433}:5432"
     volumes:
       - postgres_db_data:/var/lib/postgresql/data
     healthcheck:
@@ -32,7 +33,8 @@ services:
       postgres:
         condition: service_healthy
     ports:
-      - "${PORT:-3000}:3000"
+      # Use HOST_PORT (default 8080) to prevent conflicts if host port 3000 is already occupied by another app
+      - "${HOST_PORT:-8080}:3000"
     environment:
       - NODE_ENV=production
       - PORT=3000