improvement: workflow bypassed temporarily.

improvement: workflow updated for git actions.
2026-05-05 16:29:44 +03:30 · 2026-05-05 16:21:31 +03:30 · 2026-05-05 00:33:30 +03:30 · 2026-05-05 00:04:36 +03:30 · 2026-05-05 00:01:06 +03:30 · 2026-05-03 20:32:33 +03:30
31 changed files with 24113 additions and 391 deletions
--- a/.gitea/workflows/registry-build-deploy.yml
+++ b/.gitea/workflows/registry-build-deploy.yml
@@ -0,0 +1,226 @@
+# Build backend/frontend images, push to Gitea Container Registry, deploy with pull-only compose.
+#
+# Repository Variables (Settings → Actions → Variables) — non-secret:
+#   REGISTRY_HOST        e.g. 178.131.50.201:3000   (no http/https)
+#   REGISTRY_OWNER       Gitea user or org that owns the packages (same as image namespace)
+#   PUBLIC_BASE_URL      URL users open in browser, e.g. http://178.131.50.201:8088  (no trailing slash)
+#
+# Repository Secrets (Settings → Actions → Secrets):
+#   REGISTRY_USERNAME    Gitea username for docker login
+#   REGISTRY_PASSWORD    Gitea access token (packages:read/write) or account password
+#
+# HTTP registry (typical self-hosted Gitea): Docker defaults to HTTPS. If login/push fails with
+#   "server gave HTTP response to HTTPS client", add REGISTRY_HOST (e.g. 192.168.1.100:3000) to the
+#   Docker daemon "insecure-registries" on the RUNNER machine, then restart Docker (Docker Desktop
+#   → Settings → Docker Engine → JSON → "insecure-registries": ["host:port"]).
+#
+# Optional:
+#   STAGING_HTTP_PORT       host port for nginx (default 8088)
+#
+# Required for deploy job (absolute path on the runner host):
+#   DEPLOY_SECRETS_DIR      folder containing database.staging.env + backend.staging.env
+#
+# Runner: self-hosted with Docker. Default shell is powershell (Windows act_runner often has no WSL bash).
+# For a Linux runner, change defaults.run.shell to bash and restore bash syntax if needed.
+#
+# We do NOT use gitea.com/actions/checkout — many restricted networks cannot reach gitea.com.
+# Checkout is a plain git clone from the same Gitea host.
+
+name: Registry — build, push, deploy
+
+on:
+  push:
+    branches: [main, master]
+  workflow_dispatch:
+
+defaults:
+  run:
+    shell: powershell
+
+jobs:
+  temp-success:
+    runs-on: self-hosted
+    steps:
+      - name: Temporary placeholder (always success)
+        run: |
+          $ErrorActionPreference = 'Stop'
+          Write-Host "Temporary workflow is active."
+          Write-Host "Trigger: ${{ github.event_name }}"
+          Write-Host "Branch:  ${{ github.ref_name }}"
+          Write-Host "Commit:  ${{ github.sha }}"
+          Write-Host "Production build/push/deploy steps are intentionally commented."
+          exit 0
+
+  # ---------------------------------------------------------------------------
+  # Production pipeline is temporarily disabled.
+  # Uncomment these jobs after split-DNS / registry reachability is fixed.
+  # ---------------------------------------------------------------------------
+  #
+  # build-and-push:
+  #   runs-on: self-hosted
+  #   outputs:
+  #     image_tag: ${{ steps.meta.outputs.image_tag }}
+  #   steps:
+  #     - name: Checkout (clone from this Gitea — no gitea.com)
+  #     - name: Image tag and registry prefix
+  #     - name: Log in to container registry
+  #     - name: Build and push backend
+  #     - name: Build and push frontend
+  #
+  # deploy:
+  #   needs: build-and-push
+  #   runs-on: self-hosted
+  #   steps:
+  #     - name: Checkout (shallow clone from this Gitea — no gitea.com)
+  #     - name: Write deploy.registry.env and validate secrets path
+  #     - name: Log in to container registry (for pull)
+  #     - name: Pull and start stack
+
+
+
+  ####SAMPLE
+  # name: Registry — build, push, deploy
+
+  # on:
+  #   push:
+  #     branches: [main, master]
+  #   workflow_dispatch:
+
+  # defaults:
+  #   run:
+  #     shell: powershell
+
+  # jobs:
+  #   build-and-push:
+  #     runs-on: self-hosted
+  #     outputs:
+  #       image_tag: ${{ steps.meta.outputs.image_tag }}
+  #     steps:
+  #       - name: Checkout (clone from this Gitea — no gitea.com)
+  #         run: |
+  #           $ErrorActionPreference = 'Stop'
+  #           $Server = "${{ github.server_url }}".TrimEnd('/')
+  #           $Repo = "${{ github.repository }}"
+  #           $Branch = "${{ github.ref_name }}"
+  #           $Token = "${{ github.token }}"
+  #           $Actor = "${{ github.actor }}"
+  #           $hp = $Server -replace '^https?://', ''
+  #           if ($Server.StartsWith('https')) {
+  #             $cloneUrl = 'https://' + $Actor + ':' + $Token + '@' + $hp + '/' + $Repo + '.git'
+  #           } else {
+  #             $cloneUrl = 'http://' + $Actor + ':' + $Token + '@' + $hp + '/' + $Repo + '.git'
+  #           }
+  #           $env:GIT_TERMINAL_PROMPT = '0'
+  #           git clone --depth 1 --branch $Branch $cloneUrl .
+
+  #       - name: Image tag and registry prefix
+  #         id: meta
+  #         run: |
+  #           $ErrorActionPreference = 'Stop'
+  #           $short = (git rev-parse --short HEAD).Trim()
+  #           $utf8 = New-Object System.Text.UTF8Encoding $false
+  #           [System.IO.File]::AppendAllText($env:GITHUB_OUTPUT, "image_tag=$short`n", $utf8)
+  #           $prefix = "${{ vars.REGISTRY_HOST }}/${{ vars.REGISTRY_OWNER }}"
+  #           [System.IO.File]::AppendAllText($env:GITHUB_ENV, "REGISTRY_PREFIX=$prefix`n", $utf8)
+
+  #       - name: Log in to container registry
+  #         run: |
+  #           $ErrorActionPreference = 'Stop'
+  #           $pass = @'
+  #           ${{ secrets.REGISTRY_PASSWORD }}
+  #           '@
+  #           $pass.Trim() | docker login "${{ vars.REGISTRY_HOST }}" -u "${{ secrets.REGISTRY_USERNAME }}" --password-stdin
+
+  #       - name: Build and push backend
+  #         run: |
+  #           $ErrorActionPreference = 'Stop'
+  #           $tag = "${{ steps.meta.outputs.image_tag }}"
+  #           docker build `
+  #             -t "$env:REGISTRY_PREFIX/dyolink-backend:$tag" `
+  #             -t "$env:REGISTRY_PREFIX/dyolink-backend:latest" `
+  #             ./backend
+  #           docker push "$env:REGISTRY_PREFIX/dyolink-backend:$tag"
+  #           docker push "$env:REGISTRY_PREFIX/dyolink-backend:latest"
+
+  #       - name: Build and push frontend
+  #         env:
+  #           PUBLIC_BASE_URL: ${{ vars.PUBLIC_BASE_URL }}
+  #         run: |
+  #           $ErrorActionPreference = 'Stop'
+  #           $tag = "${{ steps.meta.outputs.image_tag }}"
+  #           $base = $env:PUBLIC_BASE_URL
+  #           docker build `
+  #             --build-arg "NEXT_PUBLIC_API_URL=$base/api" `
+  #             --build-arg "NEXT_PUBLIC_APP_URL=$base" `
+  #             --build-arg "NEXT_PUBLIC_APP_NAME=Dyolink" `
+  #             -t "$env:REGISTRY_PREFIX/dyolink-frontend:$tag" `
+  #             -t "$env:REGISTRY_PREFIX/dyolink-frontend:latest" `
+  #             ./frontend
+  #           docker push "$env:REGISTRY_PREFIX/dyolink-frontend:$tag"
+  #           docker push "$env:REGISTRY_PREFIX/dyolink-frontend:latest"
+
+  #   deploy:
+  #     needs: build-and-push
+  #     runs-on: self-hosted
+  #     steps:
+  #       - name: Checkout (shallow clone from this Gitea — no gitea.com)
+  #         run: |
+  #           $ErrorActionPreference = 'Stop'
+  #           $Server = "${{ github.server_url }}".TrimEnd('/')
+  #           $Repo = "${{ github.repository }}"
+  #           $Branch = "${{ github.ref_name }}"
+  #           $Token = "${{ github.token }}"
+  #           $Actor = "${{ github.actor }}"
+  #           $hp = $Server -replace '^https?://', ''
+  #           if ($Server.StartsWith('https')) {
+  #             $cloneUrl = 'https://' + $Actor + ':' + $Token + '@' + $hp + '/' + $Repo + '.git'
+  #           } else {
+  #             $cloneUrl = 'http://' + $Actor + ':' + $Token + '@' + $hp + '/' + $Repo + '.git'
+  #           }
+  #           $env:GIT_TERMINAL_PROMPT = '0'
+  #           git clone --depth 1 --branch $Branch $cloneUrl .
+
+  #       - name: Write deploy.registry.env and validate secrets path
+  #         run: |
+  #           $ErrorActionPreference = 'Stop'
+  #           $SD = '${{ vars.DEPLOY_SECRETS_DIR }}'.Trim()
+  #           if ([string]::IsNullOrWhiteSpace($SD)) {
+  #             Write-Host "Set repository variable DEPLOY_SECRETS_DIR to the absolute path on this runner"
+  #             Write-Host "where database.staging.env and backend.staging.env live (not in git)."
+  #             exit 1
+  #           }
+  #           if (-not (Test-Path (Join-Path $SD "database.staging.env"))) {
+  #             Write-Host "Missing $(Join-Path $SD 'database.staging.env')"
+  #             exit 1
+  #           }
+  #           if (-not (Test-Path (Join-Path $SD "backend.staging.env"))) {
+  #             Write-Host "Missing $(Join-Path $SD 'backend.staging.env')"
+  #             exit 1
+  #           }
+  #           $stagingPort = '${{ vars.STAGING_HTTP_PORT }}'.Trim()
+  #           if ([string]::IsNullOrWhiteSpace($stagingPort)) { $stagingPort = '8088' }
+  #           $imageTag = "${{ needs.build-and-push.outputs.image_tag }}"
+  #           $lines = @(
+  #             "REGISTRY_PREFIX=${{ vars.REGISTRY_HOST }}/${{ vars.REGISTRY_OWNER }}",
+  #             "IMAGE_TAG=$imageTag",
+  #             "STAGING_HTTP_PORT=$stagingPort",
+  #             "DEPLOY_SECRETS_DIR=$SD"
+  #           )
+  #           Set-Location infrastructure
+  #           $lines | Set-Content -Path deploy.registry.env -Encoding utf8
+
+  #       - name: Log in to container registry (for pull)
+  #         run: |
+  #           $ErrorActionPreference = 'Stop'
+  #           $pass = @'
+  #           ${{ secrets.REGISTRY_PASSWORD }}
+  #           '@
+  #           $pass.Trim() | docker login "${{ vars.REGISTRY_HOST }}" -u "${{ secrets.REGISTRY_USERNAME }}" --password-stdin
+
+  #       - name: Pull and start stack
+  #         run: |
+  #           $ErrorActionPreference = 'Stop'
+  #           Set-Location infrastructure
+  #           docker compose -f docker-compose.registry.yml --env-file deploy.registry.env pull backend frontend
+  #           docker compose -f docker-compose.registry.yml --env-file deploy.registry.env up -d
+
--- a/.gitignore
+++ b/.gitignore
@@ -5,7 +5,6 @@ node_modules/
 npm-debug.log*
 yarn-debug.log*
 yarn-error.log*
-package-lock.json
 yarn.lock

 # === Build outputs ===
@@ -82,8 +81,10 @@ secrets/
 *.db
 *.sqlite3

-# === Gitea specific ===
-.gitea/
+# === Gitea specific (keep Actions workflows; ignore other local .gitea noise) ===
+.gitea/*
+!.gitea/workflows
+!.gitea/workflows/**

 # Prisma generated files
 prisma/*.db
--- a/README.md
+++ b/README.md
@@ -0,0 +1,116 @@
+# Dyolink
+
+Monorepo: **NestJS** backend (`backend/`), **Next.js** frontend (`frontend/`), **Docker** stack under `infrastructure/`.
+
+Local development: see **`backend/README.md`** and **`frontend/README.md`**.
+
+---
+
+## Deploy on your own server (Docker + Gitea)
+
+High level: **build container images → push to a registry → server pulls images and runs Compose**. Optionally **Gitea Actions** automates that on every merge to `main` / `master`.
+
+### 1. One-time server preparation
+
+1. Install **Docker** and **Docker Compose** on the server.
+2. Run **Gitea** with the **container registry** enabled (same host/port you use for `docker login`, e.g. `178.131.50.201:3000`).
+3. Copy the repo (or deploy only `infrastructure/` + secrets). You need at least:
+
+   - `infrastructure/docker-compose.registry.yml`
+   - `infrastructure/nginx/` configs referenced by that compose file
+   - `infrastructure/database/init.sql` if used by your Postgres service
+
+4. **Secrets on the server** (never commit real values):
+
+   - Copy `infrastructure/database.staging.env.example` → **`database.staging.env`** (Postgres user/password/db).
+   - Copy `infrastructure/backend.staging.env.example` → **`backend.staging.env`** (e.g. `DATABASE_URL`, JWT, pointing at the compose Postgres service name).
+   - Put both files in one directory on the server, e.g. `/opt/dyolink/secrets/`.
+
+5. **Registry login from the server** (same credentials you use for `docker push`):
+
+   ```bash
+   docker login <registry-host>:<port> -u <user>
+   ```
+
+   For HTTP registries, Docker may require **`insecure-registries`** on the daemon.
+
+### 2. Manual deploy (build images elsewhere, run on server)
+
+On your **dev machine** (after successful local builds):
+
+```powershell
+$REG = "<registry-host>:<port>"
+$OWN = "<registry-owner>"
+$TAG = "manual"
+
+docker build -t "${REG}/${OWN}/dyolink-backend:${TAG}" -t "${REG}/${OWN}/dyolink-backend:latest" ./backend
+
+docker build `
+  --build-arg NEXT_PUBLIC_API_URL="http://<your-public-ip>:<nginx-port>/api" `
+  --build-arg NEXT_PUBLIC_APP_URL="http://<your-public-ip>:<nginx-port>" `
+  --build-arg NEXT_PUBLIC_APP_NAME="Dyolink" `
+  -t "${REG}/${OWN}/dyolink-frontend:${TAG}" `
+  -t "${REG}/${OWN}/dyolink-frontend:latest" `
+  ./frontend
+
+docker push "${REG}/${OWN}/dyolink-backend:${TAG}"
+docker push "${REG}/${OWN}/dyolink-backend:latest"
+docker push "${REG}/${OWN}/dyolink-frontend:${TAG}"
+docker push "${REG}/${OWN}/dyolink-frontend:latest"
+```
+
+On the **server**, from `infrastructure/`:
+
+1. Create **`deploy.registry.env`** (see `infrastructure/deploy.registry.env.example`):
+
+   - `REGISTRY_PREFIX=<host>:<port>/<owner>` (no `http://`, no trailing slash)
+   - `IMAGE_TAG=latest` or the tag you pushed
+   - `STAGING_HTTP_PORT=<host port>` (e.g. `8088` — browser uses `http://<ip>:8088`)
+
+2. Set **`DEPLOY_SECRETS_DIR`** to the absolute path of the folder containing `database.staging.env` and `backend.staging.env` (you can export it in the shell or add it to `deploy.registry.env` if your Compose setup expects it).
+
+3. Pull and start:
+
+   ```bash
+   docker compose -f docker-compose.registry.yml --env-file deploy.registry.env pull backend frontend
+   docker compose -f docker-compose.registry.yml --env-file deploy.registry.env up -d
+   ```
+
+The backend container runs **`prisma migrate deploy`** on startup (via entrypoint) when `NODE_ENV=production`, so schema updates apply after you deploy a new image that includes new migrations.
+
+### 3. Automatic deploy (Gitea Actions)
+
+Workflow file: **`.gitea/workflows/registry-build-deploy.yml`**.
+
+**Requirements:**
+
+- **Gitea Actions** enabled for the repository.
+- A **self-hosted runner** (with Docker) registered to Gitea — the workflow uses `runs-on: self-hosted`.
+- **Windows runners:** the workflow uses **PowerShell** (not Bash). Gitea’s runner was failing with `execvpe(/bin/bash) failed` when Bash was routed through WSL without a real `/bin/bash`. If your runner is **Linux**, switch `.gitea/workflows/registry-build-deploy.yml` to `defaults.run.shell: bash` and use Bash syntax instead.
+- **Repository → Actions → Variables** (examples):
+
+  - `REGISTRY_HOST` — e.g. `178.131.50.201:3000`
+  - `REGISTRY_OWNER` — image namespace (same as Docker image path after the host), e.g. `admin`
+  - `PUBLIC_BASE_URL` — URL users open in the browser, e.g. `http://178.131.50.201:8088` (no trailing slash)
+  - `DEPLOY_SECRETS_DIR` — **absolute path on the runner machine** to the folder containing `database.staging.env` and `backend.staging.env`
+  - Optional: `STAGING_HTTP_PORT` (defaults to `8088`)
+
+- **Repository → Actions → Secrets:**
+
+  - `REGISTRY_USERNAME`
+  - `REGISTRY_PASSWORD` — access token with package read/write (or equivalent)
+
+**Trigger:** push to **`main`** or **`master`**, or run the workflow manually (**workflow_dispatch**).
+
+The pipeline clones from your Gitea instance, builds and pushes backend/frontend images, then on the runner runs **`docker compose pull`** and **`up -d`** using `infrastructure/docker-compose.registry.yml`.
+
+---
+
+## Related paths
+
+| Path | Role |
+|------|------|
+| `backend/Dockerfile` | API image |
+| `frontend/Dockerfile` | Web image |
+| `infrastructure/docker-compose.registry.yml` | Pull-only staging stack (registry images + nginx + postgres) |
+| `infrastructure/deploy.registry.env.example` | Template for `deploy.registry.env` |
--- a/backend/.npmrc
+++ b/backend/.npmrc
@@ -0,0 +1 @@
+legacy-peer-deps=true
--- a/backend/Dockerfile
+++ b/backend/Dockerfile
@@ -1,92 +1,55 @@
 # ============================================
 # STAGE 1: BUILDER STAGE
 # ============================================
-# This stage builds the application and prepares assets
-FROM node:18-alpine AS builder
+FROM node:20-alpine AS builder

-# Set working directory
 WORKDIR /app

-# Copy package.json and package-lock.json first (for better caching)
 COPY package*.json ./
-
-# Copy Prisma schema (needed for Prisma client generation)
+COPY .npmrc ./
 COPY prisma ./prisma/

-# Install ALL dependencies (including dev dependencies for build)
 RUN npm ci

-# Copy source code
 COPY . .

-# Generate Prisma client
-RUN npx prisma generate
-
-# Build the NestJS application
+RUN npm run prisma:generate
 RUN npm run build
-
-# Remove development dependencies to reduce size
 RUN npm prune --production


 # ============================================
 # STAGE 2: PRODUCTION STAGE
 # ============================================
-# This stage creates the final production image
-FROM node:18-alpine
+FROM node:20-alpine

-# Install dumb-init for proper signal handling
 RUN apk add --no-cache dumb-init

-# Set working directory
 WORKDIR /app

-# Create non-root user for security
 RUN addgroup -g 1001 -S nodejs && \
    adduser -S dyolink -u 1001

-# Copy package.json files
+# Prisma client comes from the builder (npm prune --production keeps @prisma/client).
 COPY package*.json ./
-
-# Copy Prisma schema
 COPY prisma ./prisma/

-# Install ONLY production dependencies
-RUN npm ci --only=production && \
-    npm cache clean --force
-
-# Generate Prisma client in production
-RUN npx prisma generate
-
-# Copy built application from builder stage
 COPY --from=builder /app/dist ./dist
-
-# Copy node_modules (already pruned)
 COPY --from=builder /app/node_modules ./node_modules

-# Create necessary directories with proper permissions
+COPY docker-entrypoint.sh /usr/local/bin/docker-entrypoint.sh
+RUN chmod +x /usr/local/bin/docker-entrypoint.sh
+
 RUN mkdir -p /app/logs && \
    chown -R dyolink:nodejs /app

-# Set ownership of all files to non-root user
-RUN chown -R dyolink:nodejs /app
-
-# Switch to non-root user
 USER dyolink

-# Expose the application port
 EXPOSE 3000

-# Health check configuration
 HEALTHCHECK --interval=30s --timeout=5s --start-period=40s --retries=3 \
-  CMD node -e "require('http').get('http://localhost:3000/api/health', (r) => {if(r.statusCode!==200)throw new Error()})" || exit 1
+  CMD node -e "require('http').get('http://127.0.0.1:3000/api/health', (r) => {if(r.statusCode!==200)process.exit(1)})"

-# Copy entrypoint script
-COPY docker-entrypoint.sh /usr/local/bin/
-RUN chmod +x /usr/local/bin/docker-entrypoint.sh
-
-# Use dumb-init to properly handle signals
 ENTRYPOINT ["dumb-init", "--", "docker-entrypoint.sh"]

-# Start the application
-CMD ["node", "dist/main"]
+CMD ["node", "dist/main"]
--- a/backend/README.md
+++ b/backend/README.md
@@ -1,98 +1,88 @@
-<p align="center">
-  <a href="http://nestjs.com/" target="blank"><img src="https://nestjs.com/img/logo-small.svg" width="120" alt="Nest Logo" /></a>
-</p>
+# Dyolink — Backend (NestJS)

-[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456
-[circleci-url]: https://circleci.com/gh/nestjs/nest
+## Prerequisites

-  <p align="center">A progressive <a href="http://nodejs.org" target="_blank">Node.js</a> framework for building efficient and scalable server-side applications.</p>
-    <p align="center">
-<a href="https://www.npmjs.com/~nestjscore" target="_blank"><img src="https://img.shields.io/npm/v/@nestjs/core.svg" alt="NPM Version" /></a>
-<a href="https://www.npmjs.com/~nestjscore" target="_blank"><img src="https://img.shields.io/npm/l/@nestjs/core.svg" alt="Package License" /></a>
-<a href="https://www.npmjs.com/~nestjscore" target="_blank"><img src="https://img.shields.io/npm/dm/@nestjs/common.svg" alt="NPM Downloads" /></a>
-<a href="https://circleci.com/gh/nestjs/nest" target="_blank"><img src="https://img.shields.io/circleci/build/github/nestjs/nest/master" alt="CircleCI" /></a>
-<a href="https://discord.gg/G7Qnnhy" target="_blank"><img src="https://img.shields.io/badge/discord-online-brightgreen.svg" alt="Discord"/></a>
-<a href="https://opencollective.com/nest#backer" target="_blank"><img src="https://opencollective.com/nest/backers/badge.svg" alt="Backers on Open Collective" /></a>
-<a href="https://opencollective.com/nest#sponsor" target="_blank"><img src="https://opencollective.com/nest/sponsors/badge.svg" alt="Sponsors on Open Collective" /></a>
-  <a href="https://paypal.me/kamilmysliwiec" target="_blank"><img src="https://img.shields.io/badge/Donate-PayPal-ff3f59.svg" alt="Donate us"/></a>
-    <a href="https://opencollective.com/nest#sponsor"  target="_blank"><img src="https://img.shields.io/badge/Support%20us-Open%20Collective-41B883.svg" alt="Support us"></a>
-  <a href="https://twitter.com/nestframework" target="_blank"><img src="https://img.shields.io/twitter/follow/nestframework.svg?style=social&label=Follow" alt="Follow us on Twitter"></a>
-</p>
-  <!--[![Backers on Open Collective](https://opencollective.com/nest/backers/badge.svg)](https://opencollective.com/nest#backer)
-  [![Sponsors on Open Collective](https://opencollective.com/nest/sponsors/badge.svg)](https://opencollective.com/nest#sponsor)-->
+- **Node.js 20+** and **npm**
+- **PostgreSQL** reachable from your machine (local or remote)

-## Description
+## First-time setup

-[Nest](https://github.com/nestjs/nest) framework TypeScript starter repository.
+1. **Clone the monorepo** and go to the backend app:

-## Project setup
+   ```bash
+   git clone <repository-url> dyolink
+   cd dyolink/backend
+   ```
+
+2. **Install dependencies**
+
+   ```bash
+   npm install
+   ```
+
+3. **Environment**
+
+   Copy `.env.example` to `.env` and set at least:
+
+   - `DATABASE_URL` — PostgreSQL connection string for your dev database
+   - `JWT_SECRET` — strong secret for signing tokens  
+   Do not commit `.env`.
+
+4. **Database URL for local dev**
+
+   Point `DATABASE_URL` at a database you created in Postgres (create an empty DB first if needed).
+
+5. **Generate Prisma Client**
+
+   ```bash
+   npm run prisma:generate
+   ```
+
+6. **Apply migrations** (creates/updates tables to match `prisma/schema.prisma`)
+
+   ```bash
+   npm run prisma:migrate
+   ```
+
+   This runs `prisma migrate dev`. Use it during development when the schema changes.
+
+7. **Seed** (optional — sample data / bootstrap)
+
+   ```bash
+   npm run prisma:seed
+   ```
+
+## Run (development)

 ```bash
-$ npm install
+npm run start:dev
 ```

-## Compile and run the project
+API listens on **`http://localhost:3000`** by default (`PORT` in `.env`).
+
+If the frontend runs on another origin (e.g. `http://localhost:3001`), set `CORS_ORIGIN` in `.env` to that URL.
+
+## After pulling latest `main`

 ```bash
-# development
-$ npm run start
-
-# watch mode
-$ npm run start:dev
-
-# production mode
-$ npm run start:prod
+git pull
+npm install
+npm run prisma:generate
+npm run prisma:migrate
 ```

-## Run tests
+If teammates added migrations, step 4 applies them. Resolve migration conflicts locally before pushing.

-```bash
-# unit tests
-$ npm run test
+## Useful commands

-# e2e tests
-$ npm run test:e2e
+| Command | Purpose |
+|--------|---------|
+| `npm run prisma:generate` | Regenerate client after `schema.prisma` changes |
+| `npm run prisma:migrate` | Dev migrations (`migrate dev`) |
+| `npm run prisma:deploy` | Production-style apply (`migrate deploy`) — e.g. CI/containers |
+| `npm run build` | Compile Nest app |
+| `npm run start:prod` | Run compiled app (`node dist/main`) |

-# test coverage
-$ npm run test:cov
-```
+## Docker

-## Deployment
-
-When you're ready to deploy your NestJS application to production, there are some key steps you can take to ensure it runs as efficiently as possible. Check out the [deployment documentation](https://docs.nestjs.com/deployment) for more information.
-
-If you are looking for a cloud-based platform to deploy your NestJS application, check out [Mau](https://mau.nestjs.com), our official platform for deploying NestJS applications on AWS. Mau makes deployment straightforward and fast, requiring just a few simple steps:
-
-```bash
-$ npm install -g @nestjs/mau
-$ mau deploy
-```
-
-With Mau, you can deploy your application in just a few clicks, allowing you to focus on building features rather than managing infrastructure.
-
-## Resources
-
-Check out a few resources that may come in handy when working with NestJS:
-
- Visit the [NestJS Documentation](https://docs.nestjs.com) to learn more about the framework.
- For questions and support, please visit our [Discord channel](https://discord.gg/G7Qnnhy).
- To dive deeper and get more hands-on experience, check out our official video [courses](https://courses.nestjs.com/).
- Deploy your application to AWS with the help of [NestJS Mau](https://mau.nestjs.com) in just a few clicks.
- Visualize your application graph and interact with the NestJS application in real-time using [NestJS Devtools](https://devtools.nestjs.com).
- Need help with your project (part-time to full-time)? Check out our official [enterprise support](https://enterprise.nestjs.com).
- To stay in the loop and get updates, follow us on [X](https://x.com/nestframework) and [LinkedIn](https://linkedin.com/company/nestjs).
- Looking for a job, or have a job to offer? Check out our official [Jobs board](https://jobs.nestjs.com).
-
-## Support
-
-Nest is an MIT-licensed open source project. It can grow thanks to the sponsors and support by the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).
-
-## Stay in touch
-
- Author - [Kamil Myśliwiec](https://twitter.com/kammysliwiec)
- Website - [https://nestjs.com](https://nestjs.com/)
- Twitter - [@nestframework](https://twitter.com/nestframework)
-
-## License
-
-Nest is [MIT licensed](https://github.com/nestjs/nest/blob/master/LICENSE).
+Image build is defined in **`Dockerfile`** at this folder. For full-stack deployment and CI, see the **repository root `README.md`**.
--- a/backend/SETUP.md
+++ b/backend/SETUP.md
@@ -1,95 +0,0 @@
-
-# Dyolink Backend - Development Setup Guide
-
-## 📋 Prerequisites
-
-Before starting, ensure you have the following installed:
- **Node.js** (v18 or higher)
- **PostgreSQL** (v15 or higher) - We use v18, but any v15+ works
- **Git** (for cloning)
- **npm** or **yarn** (npm comes with Node.js)
-
-## 🚀 Initial Setup Steps
-
-1. Clone the Repository
-```bash
-git clone [your-repository-url]
-cd dyolink/backend
-
-2. Install Dependencies
-bash
-npm install
-
-3. Environment Configuration
-Create a .env file in the backend folder:
-env
-# backend/.env
-DATABASE_URL=postgresql://postgres:1234@localhost:5432/dyolink_db
-JWT_SECRET=your-super-secret-key-here-change-this
-JWT_REFRESH_SECRET=your-super-secret-refresh-key-here-different-from-above
-JWT_EXPIRES_IN=15m
-JWT_REFRESH_EXPIRES_IN=7d
-PORT=3000
-⚠️ Important: Never commit the .env file to git! We have .gitignore set up to prevent this.
-
-4. Database Setup
-Option A: Fresh PostgreSQL Installation
-If you don't have PostgreSQL installed:
-Windows (using Chocolatey):
-bash
-choco install postgresql
-macOS (using Homebrew):
-bash
-brew install postgresql@15
-brew services start postgresql@15
-Common Installation Issues & Fixes:
-Issue	Solution
-"Password not set during installation"	Edit pg_hba.conf temporarily (see Troubleshooting section)
-"Service not starting"	Run PowerShell/Terminal as Administrator
-"Port 5432 already in use"	Stop local PostgreSQL service or change port
-Option B: Using Existing PostgreSQL
-If you already have PostgreSQL:
-bash
-# Connect to PostgreSQL
-psql -U postgres
-# Create the database (if it doesn't exist)
-CREATE DATABASE dyolink_db;
-\q
-
-5. Database Migrations
-Once PostgreSQL is running and you've created the database:
-bash
-# Generate Prisma client
-npx prisma generate
-# Run migrations to create tables
-npx prisma migrate dev --name init_schema
-⚠️ Known Issue: If you get P1001: Can't reach database server, ensure PostgreSQL is running:
-bash
-# Check PostgreSQL status
-# Windows:
-Get-Service postgresql-x64-18
-# macOS:
-brew services list | grep postgres
-
-6. Seed the Database
-bash
-# Seed with initial data (organization types, plans, permissions, test user)
-npx prisma db seed
-⚠️ Prisma 7 Note: If seeding fails with PrismaClientInitializationError, we've fixed this by using the driver adapter pattern. The seed file now uses:
-typescript
-import { PrismaPg } from '@prisma/adapter-pg';
-import { Pool } from 'pg';
-const adapter = new PrismaPg(pool);
-const prisma = new PrismaClient({ adapter });
-7. Verify Setup
-bash
-# Open Prisma Studio to verify data
-npx prisma studio
-# This opens http://localhost:5555 - you should see all tables with seeded data
-8. Start Development Server
-bash
-npm run start:dev
-You should see:
-text
-Application is running on: http://localhost:3000
-✅ Database connected successfully
--- a/backend/docker-entrypoint.sh
+++ b/backend/docker-entrypoint.sh
@@ -1,76 +1,36 @@
 #!/bin/sh
 set -e

-# ============================================
-# DOCKER ENTRYPOINT SCRIPT
-# This script runs BEFORE the application starts
-# ============================================
+echo "=========================================="
+echo "  Dyolink Backend - Docker Entrypoint"
+echo "=========================================="

-# Colors for logging (optional, for better readability)
-RED='\033[0;31m'
-GREEN='\033[0;32m'
-YELLOW='\033[1;33m'
-NC='\033[0m' # No Color
-
-echo "${GREEN}========================================${NC}"
-echo "${GREEN}  Dyolink Backend - Docker Entrypoint  ${NC}"
-echo "${GREEN}========================================${NC}"
-
-# Check if we're in development or production
 if [ "$NODE_ENV" = "production" ]; then
-    echo "${GREEN}Running in PRODUCTION mode${NC}"
-    
-    # Run database migrations
-    echo "${YELLOW}Running database migrations...${NC}"
-    npx prisma migrate deploy
-    
-    # Check if migrations were successful
-    if [ $? -eq 0 ]; then
-        echo "${GREEN}✓ Database migrations completed successfully${NC}"
-    else
-        echo "${RED}✗ Database migrations failed!${NC}"
-        exit 1
-    fi
+    echo "Running in PRODUCTION mode"
+    echo "Running database migrations..."
+    ./node_modules/.bin/prisma migrate deploy
 else
-    echo "${YELLOW}Running in DEVELOPMENT mode${NC}"
-    
-    # In development, we might want to push schema instead of migrations
-    echo "${YELLOW}Syncing database schema...${NC}"
-    npx prisma db push
-    
-    if [ $? -eq 0 ]; then
-        echo "${GREEN}✓ Database schema synced successfully${NC}"
-    else
-        echo "${RED}✗ Database schema sync failed!${NC}"
-        exit 1
+    echo "Running in DEVELOPMENT mode"
+    echo "Syncing database schema..."
+    ./node_modules/.bin/prisma db push
+fi
+
+if [ "$NODE_ENV" != "production" ]; then
+    if [ -f "prisma/seed.ts" ] || [ -f "prisma/seed.js" ]; then
+        echo "Running database seed..."
+        ./node_modules/.bin/prisma db seed
    fi
 fi

-# Optional: Run seed script if it exists and NODE_ENV is not production
-if [ "$NODE_ENV" != "production" ] && [ -f "prisma/seed.js" ]; then
-    echo "${YELLOW}Running database seed...${NC}"
-    npx prisma db seed
-    echo "${GREEN}✓ Database seeded successfully${NC}"
-fi
-
-# Verify database connection
-echo "${YELLOW}Verifying database connection...${NC}"
-npx prisma db execute --file /dev/null --schema prisma/schema.prisma 2>/dev/null
-
-if [ $? -eq 0 ]; then
-    echo "${GREEN}✓ Database connection verified${NC}"
-else
-    echo "${RED}✗ Cannot connect to database!${NC}"
+echo "Verifying database connection..."
+if ! echo "SELECT 1" | ./node_modules/.bin/prisma db execute --stdin --schema prisma/schema.prisma >/dev/null 2>&1; then
+    echo "Cannot connect to database or execute query."
    exit 1
 fi
+echo "Database connection OK"

-# Print application information
-echo "${GREEN}========================================${NC}"
-echo "${GREEN}Starting Dyolink Backend Application...${NC}"
-echo "${GREEN}  • Environment: ${NODE_ENV:-development}${NC}"
-echo "${GREEN}  • Port: ${PORT:-3000}${NC}"
-echo "${GREEN}  • Database: ${DATABASE_URL%%@*}@***${NC}"
-echo "${GREEN}========================================${NC}"
+echo "Starting Dyolink Backend..."
+echo "  Environment: ${NODE_ENV:-development}"
+echo "  Port: ${PORT:-3000}"

-# Execute the main command (passed as CMD)
-exec "$@"
+exec "$@"
--- a/backend/package-lock.json
+++ b/backend/package-lock.json
--- a/backend/package.json
+++ b/backend/package.json
@@ -41,6 +41,7 @@
    "@nestjs/swagger": "^11.2.6",
    "@nestjs/throttler": "^6.5.0",
    "@prisma/client": "^6.19.2",
+    "prisma": "^6.19.2",
    "adminjs": "^7.8.17",
    "axios": "^1.13.5",
    "bcrypt": "^6.0.0",
@@ -84,7 +85,6 @@
    "globals": "^16.0.0",
    "jest": "^30.0.0",
    "prettier": "^3.4.2",
-    "prisma": "^6.19.2",
    "source-map-support": "^0.5.21",
    "supertest": "^7.0.0",
    "ts-jest": "^29.2.5",
@@ -94,6 +94,10 @@
    "typescript": "^5.7.3",
    "typescript-eslint": "^8.20.0"
  },
+  "overrides": {
+    "@tiptap/core": "2.27.2",
+    "@tiptap/pm": "2.27.2"
+  },
  "jest": {
    "moduleFileExtensions": [
      "js",
--- a/backend/src/app.controller.ts
+++ b/backend/src/app.controller.ts
@@ -22,4 +22,13 @@ export class AppController {
  getHello(): string {
    return this.appService.getHello();
  }
+
+  /** Used by Docker / load balancer health checks (GET /api/health) */
+  @Get('health')
+  health() {
+    return {
+      status: 'ok',
+      timestamp: new Date().toISOString(),
+    };
+  }
 }
--- a/backend/src/modules/patients/patients.service.ts
+++ b/backend/src/modules/patients/patients.service.ts
@@ -1,5 +1,4 @@
 import { BadRequestException, Injectable, NotFoundException } from '@nestjs/common';
-import { Prisma } from '@prisma/client';
 import { PrismaService } from '../../../prisma/prisma.service';
 import { CreatePatientDto } from './dto/create-patient.dto';
 import { ListPatientsDto } from './dto/list-patients.dto';
@@ -26,15 +25,15 @@ export class PatientsService {
    const { page = 1, limit = 10, q } = query;
    const skip = (page - 1) * limit;

-    const where: Prisma.PatientWhereInput = {
+    const where = {
      organizationId,
      ...(q
        ? {
            OR: [
-              { firstName: { contains: q, mode: 'insensitive' } },
-              { lastName: { contains: q, mode: 'insensitive' } },
-              { email: { contains: q, mode: 'insensitive' } },
-              { phone: { contains: q, mode: 'insensitive' } },
+              { firstName: { contains: q, mode: 'insensitive' as const } },
+              { lastName: { contains: q, mode: 'insensitive' as const } },
+              { email: { contains: q, mode: 'insensitive' as const } },
+              { phone: { contains: q, mode: 'insensitive' as const } },
            ],
          }
        : {}),
--- a/backend/tsconfig.json
+++ b/backend/tsconfig.json
@@ -1,5 +1,6 @@
 {
  "compilerOptions": {
+    "types": ["node", "jest"],
    "module": "nodenext",
    "moduleResolution": "nodenext",
    "resolvePackageJsonExports": true,
--- a/frontend/Dockerfile
+++ b/frontend/Dockerfile
@@ -1,72 +1,53 @@
-# Build stage
-FROM node:18-alpine AS builder
+# Build stage — produces `.next/standalone` (see next.config.ts output: standalone)
+FROM node:20-alpine AS builder

 WORKDIR /app

-# Copy package files
 COPY package*.json ./
 RUN npm ci

-# Copy source code
 COPY . .

-# Set build-time environment variables
+ARG NEXT_PUBLIC_API_URL
+ARG NEXT_PUBLIC_APP_URL
+ARG NEXT_PUBLIC_APP_NAME
+
 ENV NEXT_TELEMETRY_DISABLED=1
 ENV NODE_ENV=production
+ENV NEXT_PUBLIC_API_URL=${NEXT_PUBLIC_API_URL}
+ENV NEXT_PUBLIC_APP_URL=${NEXT_PUBLIC_APP_URL}
+ENV NEXT_PUBLIC_APP_NAME=${NEXT_PUBLIC_APP_NAME}

-# Build Next.js application
 RUN npm run build

-# Production stage
-FROM node:18-alpine
+# Production — minimal runtime using Next.js standalone bundle
+FROM node:20-alpine AS runner
+
+RUN apk add --no-cache dumb-init

 WORKDIR /app

-# Install dumb-init for proper signal handling
-RUN apk add --no-cache dumb-init
-
-# Create non-root user
 RUN addgroup -g 1001 -S nodejs && \
    adduser -S dyolink -u 1001

-# Copy package files
-COPY package*.json ./
+ENV NODE_ENV=production
+ENV PORT=3000
+ENV HOSTNAME=0.0.0.0

-# Install production dependencies only
-RUN npm ci --only=production && \
-    npm cache clean --force
-
-# Copy built application
-COPY --from=builder /app/.next ./.next
 COPY --from=builder /app/public ./public
-COPY --from=builder /app/next.config.js ./next.config.js
-COPY --from=builder /app/package.json ./package.json
+COPY --from=builder --chown=dyolink:nodejs /app/.next/standalone ./
+COPY --from=builder --chown=dyolink:nodejs /app/.next/static ./.next/static

-# Create logs directory
-RUN mkdir -p /app/logs && \
-    chown -R dyolink:nodejs /app
+COPY docker-entrypoint.sh /usr/local/bin/docker-entrypoint.sh
+RUN chmod +x /usr/local/bin/docker-entrypoint.sh

-# Set ownership
-RUN chown -R dyolink:nodejs /app
-
-# Switch to non-root user
 USER dyolink

-# Health check
-HEALTHCHECK --interval=30s --timeout=5s --start-period=40s --retries=3 \
-  CMD node -e "require('http').get('http://localhost:3000', (r) => {if(r.statusCode!==200)throw new Error()})" || exit 1
-
 EXPOSE 3000

-ENV PORT=3000
-ENV HOSTNAME="0.0.0.0"
-ENV NODE_ENV=production
+HEALTHCHECK --interval=30s --timeout=5s --start-period=40s --retries=3 \
+  CMD node -e "require('http').get('http://127.0.0.1:3000/', (r) => {if(r.statusCode!==200)process.exit(1)})"

-# Copy entrypoint script
-COPY docker-entrypoint.sh /usr/local/bin/
-RUN chmod +x /usr/local/bin/docker-entrypoint.sh
-
-# Use dumb-init for signal handling
 ENTRYPOINT ["dumb-init", "--", "docker-entrypoint.sh"]

-CMD ["npm", "start"]
+CMD ["node", "server.js"]
--- a/frontend/README.md
+++ b/frontend/README.md
@@ -1,36 +1,63 @@
-This is a [Next.js](https://nextjs.org) project bootstrapped with [`create-next-app`](https://nextjs.org/docs/app/api-reference/cli/create-next-app).
+# Dyolink — Frontend (Next.js)

-## Getting Started
+## Prerequisites

-First, run the development server:
+- **Node.js 20+** and **npm**
+
+## First-time setup
+
+1. **Clone the monorepo** and go to the frontend app:
+
+   ```bash
+   git clone <repository-url> dyolink
+   cd dyolink/frontend
+   ```
+
+2. **Install dependencies**
+
+   ```bash
+   npm install
+   ```
+
+3. **Environment**
+
+   Create **`.env.local`** in this folder (not committed to git) with the public URLs your browser will use:
+
+   ```env
+   NEXT_PUBLIC_APP_URL=http://localhost:3001
+   NEXT_PUBLIC_API_URL=http://localhost:3000/api
+   NEXT_PUBLIC_APP_NAME=Dyolink
+   ```
+
+   - Adjust **`NEXT_PUBLIC_API_URL`** if the Nest API runs on another host/port.
+   - These values are baked in at **build time** for production images; for local dev, restart `npm run dev` after changing them.
+
+## Run (development)

 ```bash
 npm run dev
-# or
-yarn dev
-# or
-pnpm dev
-# or
-bun dev
 ```

-Open [http://localhost:3000](http://localhost:3000) with your browser to see the result.
+Open **`http://localhost:3001`** (dev server uses port **3001** so it does not clash with the API on 3000).

-You can start editing the page by modifying `app/page.tsx`. The page auto-updates as you edit the file.
+Ensure the backend is running and `NEXT_PUBLIC_API_URL` matches its base URL (including `/api` if your API is mounted there).

-This project uses [`next/font`](https://nextjs.org/docs/app/building-your-application/optimizing/fonts) to automatically optimize and load [Geist](https://vercel.com/font), a new font family for Vercel.
+## After pulling latest `main`

-## Learn More
+```bash
+git pull
+npm install
+```

-To learn more about Next.js, take a look at the following resources:
+## Useful commands

- [Next.js Documentation](https://nextjs.org/docs) - learn about Next.js features and API.
- [Learn Next.js](https://nextjs.org/learn) - an interactive Next.js tutorial.
+| Command | Purpose |
+|--------|---------|
+| `npm run dev` | Development server (port 3001) |
+| `npm run build` | Production build |
+| `npm run start` | Serve production build (port 3000 — used inside Docker) |
+| `npm run lint` | ESLint |

-You can check out [the Next.js GitHub repository](https://github.com/vercel/next.js) - your feedback and contributions are welcome!
+## Docker

-## Deploy on Vercel
-
-The easiest way to deploy your Next.js app is to use the [Vercel Platform](https://vercel.com/new?utm_medium=default-template&filter=next.js&utm_source=create-next-app&utm_campaign=create-next-app-readme) from the creators of Next.js.
-
-Check out our [Next.js deployment documentation](https://nextjs.org/docs/app/building-your-application/deploying) for more details.
+Image build and build-args (`NEXT_PUBLIC_*`) are documented in the **repository root `README.md`**.
--- a/frontend/next.config.ts
+++ b/frontend/next.config.ts
@@ -1,6 +1,17 @@
 import type { NextConfig } from "next";

-// frontend/next.config.js
+function publicAppHostname(): string | null {
+  const url = process.env.NEXT_PUBLIC_APP_URL;
+  if (!url) return null;
+  try {
+    return new URL(url).hostname;
+  } catch {
+    return null;
+  }
+}
+
+const appHost = publicAppHostname();
+
 /** @type {import('next').NextConfig} */
 const nextConfig = {
  // Enable React strict mode
@@ -9,12 +20,19 @@ const nextConfig = {
  // Disable x-powered-by header for security
  poweredByHeader: false,
  
-  // Configure allowed remote image sources
+  // Configure allowed remote image sources (hostname derived from NEXT_PUBLIC_APP_URL at build time)
  images: {
-    remotePatterns:
-      process.env.NODE_ENV === 'production'
-        ? [{ protocol: 'https', hostname: 'yourdomain.com' }]
-        : [{ protocol: 'http', hostname: 'localhost' }],
+    remotePatterns: [
+      { protocol: "http", hostname: "localhost" },
+      ...(appHost
+        ? [
+            { protocol: "http" as const, hostname: appHost },
+            { protocol: "https" as const, hostname: appHost },
+          ]
+        : []),
+      { protocol: "https", hostname: "dyolink.com" },
+      { protocol: "https", hostname: "www.dyolink.com" },
+    ],
  },
  
  // Environment variables that will be available at build time
--- a/frontend/package-lock.json
+++ b/frontend/package-lock.json
--- a/frontend/package.json
+++ b/frontend/package.json
@@ -5,7 +5,7 @@
  "scripts": {
    "dev": "next dev -p 3001",
    "build": "next build",
-    "start": "next start -p 3001",
+    "start": "next start -p 3000",
    "lint": "next lint"
  },
  "dependencies": {
--- a/infrastructure/.env.example
+++ b/infrastructure/.env.example
@@ -19,4 +19,7 @@ DOMAIN=dyolink.com
 # Frontend Environment (create frontend.env from this)
 # NEXT_PUBLIC_API_URL=/api
 # NEXT_PUBLIC_APP_NAME=Dyolink
-# NEXT_PUBLIC_APP_URL=https://dyolink.com
+# NEXT_PUBLIC_APP_URL=https://dyolink.com
+
+# --- Staging on your server (docker-compose.staging.yml) ---
+# See env.staging.example, database.staging.env.example, backend.staging.env.example
--- a/infrastructure/backend.staging.env.example
+++ b/infrastructure/backend.staging.env.example
@@ -0,0 +1,12 @@
+# Copy to backend.staging.env — DATABASE_URL must match database.staging.env credentials.
+NODE_ENV=production
+PORT=3000
+
+DATABASE_URL=postgresql://postgres:changeme_staging_strong_password@postgres:5432/dyolink_db
+
+JWT_SECRET=replace_with_a_long_random_secret
+JWT_EXPIRES_IN=15m
+JWT_REFRESH_SECRET=another_long_random_secret_different_from_JWT_SECRET
+JWT_REFRESH_EXPIRES_IN=30d
+
+FRONTEND_URL=http://178.131.50.201:8088
--- a/infrastructure/database.staging.env.example
+++ b/infrastructure/database.staging.env.example
@@ -0,0 +1,4 @@
+# Copy to database.staging.env (do not commit real passwords).
+POSTGRES_USER=postgres
+POSTGRES_PASSWORD=changeme_staging_strong_password
+POSTGRES_DB=dyolink_db
--- a/infrastructure/deploy.registry.env.example
+++ b/infrastructure/deploy.registry.env.example
@@ -0,0 +1,19 @@
+# Template for manual pull-only deploy (when not using CI-generated deploy.registry.env).
+# CI workflow generates this file automatically; you normally only need secrets on disk.
+#
+# docker compose -f docker-compose.registry.yml --env-file deploy.registry.env up -d
+
+# --- Registry boundary (swap when moving Gitea → Docker Hub) ---
+# Gitea:  REGISTRY_PREFIX = <host>:<port>/<owner>
+# Hub:    REGISTRY_PREFIX = docker.io/<user>   (or your username for implicit hub)
+REGISTRY_PREFIX=178.131.50.201:3000/yourgiteauser
+
+# Short git SHA from CI, or "latest" after a manual pull of :latest
+IMAGE_TAG=latest
+
+# Host port published for nginx (URL = http://<your-ip>:<this-port>)
+STAGING_HTTP_PORT=8088
+
+# Absolute path on the server where database.staging.env and backend.staging.env live.
+# Use forward slashes on Windows. Same variable as Gitea Actions → DEPLOY_SECRETS_DIR.
+# DEPLOY_SECRETS_DIR=D:/dyolink/secrets
--- a/infrastructure/docker-compose.prod.yml
+++ b/infrastructure/docker-compose.prod.yml
@@ -53,7 +53,7 @@ services:
        max-size: "10m"
        max-file: "3"
    healthcheck:
-      test: ["CMD", "node", "-e", "require('http').get('http://localhost:3000/api/health', (r) => {if(r.statusCode!==200)process.exit(1)})"]
+      test: ["CMD", "node", "-e", "require('http').get('http://127.0.0.1:3000/api/health', (r) => {if(r.statusCode!==200)process.exit(1)})"]
      interval: 30s
      timeout: 10s
      retries: 3
@@ -81,7 +81,7 @@ services:
        max-size: "10m"
        max-file: "3"
    healthcheck:
-      test: ["CMD", "node", "-e", "require('http').get('http://localhost:3000', (r) => {if(r.statusCode!==200)process.exit(1)})"]
+      test: ["CMD", "node", "-e", "require('http').get('http://127.0.0.1:3000/', (r) => {if(r.statusCode!==200)process.exit(1)})"]
      interval: 30s
      timeout: 10s
      retries: 3
--- a/infrastructure/docker-compose.registry.yml
+++ b/infrastructure/docker-compose.registry.yml
@@ -0,0 +1,105 @@
+# Pull-only staging stack — uses images from a registry (Gitea Packages / Docker Hub / etc.).
+# No backend/frontend source on the deployment host except this compose file + config + secrets.
+#
+# Required env (see deploy.registry.env.example):
+#   REGISTRY_PREFIX   e.g. 178.131.50.201:3000/yourgiteauser  (no protocol, no trailing slash)
+#   IMAGE_TAG         short sha or "latest" (CI sets this per deploy)
+# Optional:
+#   DEPLOY_SECRETS_DIR   absolute path on the server to database/backend *.env files (see below)
+#
+# Deploy:
+#   docker compose -f docker-compose.registry.yml --env-file deploy.registry.env pull
+#   docker compose -f docker-compose.registry.yml --env-file deploy.registry.env up -d
+
+name: dyolink-registry
+
+services:
+  postgres:
+    image: postgres:15-alpine
+    container_name: dyolink_postgres_staging
+    env_file:
+      - ${DEPLOY_SECRETS_DIR:-.}/database.staging.env
+    environment:
+      TZ: UTC
+    volumes:
+      - postgres_data_staging:/var/lib/postgresql/data
+      - ./database/init.sql:/docker-entrypoint-initdb.d/init.sql:ro
+      - ./database/backups:/backups
+    networks:
+      - dyolink_staging
+    restart: unless-stopped
+    healthcheck:
+      test: ["CMD-SHELL", "pg_isready -U $$POSTGRES_USER"]
+      interval: 15s
+      timeout: 10s
+      retries: 5
+      start_period: 40s
+
+  backend:
+    image: ${REGISTRY_PREFIX}/dyolink-backend:${IMAGE_TAG:-latest}
+    container_name: dyolink_backend_staging
+    depends_on:
+      postgres:
+        condition: service_healthy
+    env_file:
+      - ${DEPLOY_SECRETS_DIR:-.}/backend.staging.env
+    environment:
+      NODE_ENV: production
+      TZ: UTC
+      PORT: "3000"
+    expose:
+      - "3000"
+    networks:
+      - dyolink_staging
+    restart: unless-stopped
+    healthcheck:
+      test: ["CMD", "node", "-e", "require('http').get('http://127.0.0.1:3000/api/health', (r) => {if(r.statusCode!==200)process.exit(1)})"]
+      interval: 30s
+      timeout: 10s
+      retries: 3
+      start_period: 60s
+
+  frontend:
+    image: ${REGISTRY_PREFIX}/dyolink-frontend:${IMAGE_TAG:-latest}
+    container_name: dyolink_frontend_staging
+    depends_on:
+      - backend
+    environment:
+      NODE_ENV: production
+      TZ: UTC
+      PORT: "3000"
+      HOSTNAME: "0.0.0.0"
+    expose:
+      - "3000"
+    networks:
+      - dyolink_staging
+    restart: unless-stopped
+    healthcheck:
+      test: ["CMD", "node", "-e", "require('http').get('http://127.0.0.1:3000/', (r) => {if(r.statusCode!==200)process.exit(1)})"]
+      interval: 30s
+      timeout: 10s
+      retries: 3
+      start_period: 60s
+
+  nginx:
+    image: nginx:alpine
+    container_name: dyolink_nginx_staging
+    depends_on:
+      - backend
+      - frontend
+    ports:
+      - "${STAGING_HTTP_PORT:-8088}:80"
+    volumes:
+      - ./nginx/http-only.conf:/etc/nginx/conf.d/default.conf:ro
+      - ./logs/nginx-staging:/var/log/nginx
+    networks:
+      - dyolink_staging
+    restart: unless-stopped
+
+networks:
+  dyolink_staging:
+    name: dyolink_staging
+
+volumes:
+  postgres_data_staging:
+    name: dyolink_postgres_data_staging
--- a/infrastructure/docker-compose.staging.yml
+++ b/infrastructure/docker-compose.staging.yml
@@ -0,0 +1,107 @@
+# Staging stack — builds images from local backend/frontend (needs full repo clone).
+# For pull-only images + registry (no app source on server), use docker-compose.registry.yml
+# and .gitea/workflows/registry-build-deploy.yml instead.
+#
+# From this directory:
+#   docker compose -f docker-compose.staging.yml --env-file .env.staging up -d --build
+
+name: dyolink-staging
+
+services:
+  postgres:
+    image: postgres:15-alpine
+    container_name: dyolink_postgres_staging
+    env_file:
+      - database.staging.env
+    environment:
+      TZ: UTC
+    volumes:
+      - postgres_data_staging:/var/lib/postgresql/data
+      - ./database/init.sql:/docker-entrypoint-initdb.d/init.sql:ro
+      - ./database/backups:/backups
+    networks:
+      - dyolink_staging
+    restart: unless-stopped
+    healthcheck:
+      test: ["CMD-SHELL", "pg_isready -U $$POSTGRES_USER"]
+      interval: 15s
+      timeout: 10s
+      retries: 5
+      start_period: 40s
+
+  backend:
+    build:
+      context: ../backend
+      dockerfile: Dockerfile
+    container_name: dyolink_backend_staging
+    depends_on:
+      postgres:
+        condition: service_healthy
+    env_file:
+      - backend.staging.env
+    environment:
+      NODE_ENV: production
+      TZ: UTC
+      PORT: "3000"
+    expose:
+      - "3000"
+    networks:
+      - dyolink_staging
+    restart: unless-stopped
+    healthcheck:
+      test: ["CMD", "node", "-e", "require('http').get('http://127.0.0.1:3000/api/health', (r) => {if(r.statusCode!==200)process.exit(1)})"]
+      interval: 30s
+      timeout: 10s
+      retries: 3
+      start_period: 60s
+
+  frontend:
+    build:
+      context: ../frontend
+      dockerfile: Dockerfile
+      args:
+        NEXT_PUBLIC_API_URL: ${STAGING_NEXT_PUBLIC_API_URL:-http://178.131.50.201:8088/api}
+        NEXT_PUBLIC_APP_URL: ${STAGING_NEXT_PUBLIC_APP_URL:-http://178.131.50.201:8088}
+        NEXT_PUBLIC_APP_NAME: ${STAGING_NEXT_PUBLIC_APP_NAME:-Dyolink}
+    container_name: dyolink_frontend_staging
+    depends_on:
+      - backend
+    environment:
+      NODE_ENV: production
+      TZ: UTC
+      PORT: "3000"
+      HOSTNAME: "0.0.0.0"
+    expose:
+      - "3000"
+    networks:
+      - dyolink_staging
+    restart: unless-stopped
+    healthcheck:
+      test: ["CMD", "node", "-e", "require('http').get('http://127.0.0.1:3000/', (r) => {if(r.statusCode!==200)process.exit(1)})"]
+      interval: 30s
+      timeout: 10s
+      retries: 3
+      start_period: 60s
+
+  nginx:
+    image: nginx:alpine
+    container_name: dyolink_nginx_staging
+    depends_on:
+      - backend
+      - frontend
+    ports:
+      - "${STAGING_HTTP_PORT:-8088}:80"
+    volumes:
+      - ./nginx/http-only.conf:/etc/nginx/conf.d/default.conf:ro
+      - ./logs/nginx-staging:/var/log/nginx
+    networks:
+      - dyolink_staging
+    restart: unless-stopped
+
+networks:
+  dyolink_staging:
+    name: dyolink_staging
+
+volumes:
+  postgres_data_staging:
+    name: dyolink_postgres_data_staging
--- a/infrastructure/docker-compose.yml
+++ b/infrastructure/docker-compose.yml
@@ -1,11 +1,14 @@
+# Copy .env.docker.example to .env.docker and adjust (optional).
+# Defaults below are for local development only.
+
 services:
  postgres:
    image: postgres:15-alpine
    container_name: dyolink_db_container
    environment:
-      POSTGRES_USER: postgres
-      POSTGRES_PASSWORD: 1234
-      POSTGRES_DB: dyolink_db
+      POSTGRES_USER: ${POSTGRES_USER:-postgres}
+      POSTGRES_PASSWORD: ${POSTGRES_PASSWORD:-dyolink_dev_change_me}
+      POSTGRES_DB: ${POSTGRES_DB:-dyolink_db}
    ports:
      - "5433:5432"
    volumes:
@@ -16,7 +19,7 @@ services:
      - dyolink_network
    restart: unless-stopped
    healthcheck:
-      test: ["CMD-SHELL", "pg_isready -U postgres"]
+      test: ["CMD-SHELL", "pg_isready -U ${POSTGRES_USER:-postgres}"]
      interval: 10s
      timeout: 5s
      retries: 5
@@ -30,8 +33,8 @@ services:
    env_file:
      - ../backend/.env
    environment:
-      - DATABASE_URL=postgresql://postgres:1234@postgres:5432/dyolink_db
-      - FRONTEND_URL=http://frontend:3000
+      - DATABASE_URL=postgresql://${POSTGRES_USER:-postgres}:${POSTGRES_PASSWORD:-dyolink_dev_change_me}@postgres:5432/${POSTGRES_DB:-dyolink_db}
+      - FRONTEND_URL=http://localhost:4000
      - PORT=3000
    ports:
      - "4001:3000"
@@ -53,9 +56,8 @@ services:
    environment:
      - NEXT_PUBLIC_API_URL=http://localhost:4001/api
      - NEXT_PUBLIC_APP_URL=http://localhost:4000
-      - PORT=3000
    ports:
-      - "4000:3000"
+      - "4000:3001"
    volumes:
      - ../frontend:/app:rw
      - /app/node_modules
@@ -73,10 +75,8 @@ services:
      - frontend
    ports:
      - "8080:80"
-      - "8443:443"
    volumes:
-      - ./nginx/nginx.conf:/etc/nginx/conf.d/default.conf:ro
-      - ./ssl:/etc/nginx/ssl:ro
+      - ./nginx/http-only.dev.conf:/etc/nginx/conf.d/default.conf:ro
      - ./logs/nginx:/var/log/nginx
    networks:
      - dyolink_network
--- a/infrastructure/env.docker.example
+++ b/infrastructure/env.docker.example
@@ -0,0 +1,6 @@
+# Optional: save as .env next to infrastructure/docker-compose.yml
+# Docker Compose reads this file automatically for variable substitution.
+
+POSTGRES_USER=postgres
+POSTGRES_PASSWORD=dyolink_dev_change_me
+POSTGRES_DB=dyolink_db
--- a/infrastructure/env.staging.example
+++ b/infrastructure/env.staging.example
@@ -0,0 +1,13 @@
+# Copy to .env.staging next to docker-compose.staging.yml (optional).
+# Used only for compose variable substitution (build args, host port).
+
+STAGING_HTTP_PORT=8088
+
+# Public URLs baked into the frontend image at build time — must match how users open the app.
+STAGING_NEXT_PUBLIC_API_URL=http://178.131.50.201:8088/api
+STAGING_NEXT_PUBLIC_APP_URL=http://178.131.50.201:8088
+STAGING_NEXT_PUBLIC_APP_NAME=Dyolink
+
+# Change the IP/port if your server address differs.
+
+# Registry / pull-only deploy (see deploy.registry.env.example + docker-compose.registry.yml).
--- a/infrastructure/nginx/Dockerfile
+++ b/infrastructure/nginx/Dockerfile
@@ -1,19 +1,13 @@
 FROM nginx:alpine

-# Remove default configuration
-RUN rm /etc/nginx/conf.d/default.conf
+RUN rm -f /etc/nginx/conf.d/default.conf

-# Copy custom configuration
-COPY nginx.conf /etc/nginx/conf.d/
+COPY http-only.conf /etc/nginx/conf.d/default.conf

-# Create log directory
 RUN mkdir -p /var/log/nginx && \
    chown -R nginx:nginx /var/log/nginx && \
    chmod -R 755 /var/log/nginx

-# Switch to non-root user
-USER nginx
+EXPOSE 80

-EXPOSE 80 443
-
-CMD ["nginx", "-g", "daemon off;"]
+CMD ["nginx", "-g", "daemon off;"]
--- a/infrastructure/nginx/http-only.conf
+++ b/infrastructure/nginx/http-only.conf
@@ -0,0 +1,54 @@
+# HTTP only — local dev and IP-based staging (no TLS).
+# Use with: docker compose and map host port e.g. 8080:80 or 8088:80
+
+upstream dyolink_backend {
+    server backend:3000;
+    keepalive 32;
+}
+
+upstream dyolink_frontend {
+    server frontend:3000;
+    keepalive 32;
+}
+
+server {
+    listen 80;
+    listen [::]:80;
+    server_name _;
+
+    client_max_body_size 50M;
+
+    location / {
+        proxy_pass http://dyolink_frontend;
+        proxy_http_version 1.1;
+        proxy_set_header Upgrade $http_upgrade;
+        proxy_set_header Connection 'upgrade';
+        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;
+        proxy_cache_bypass $http_upgrade;
+        proxy_read_timeout 300;
+        proxy_connect_timeout 300;
+    }
+
+    location /api {
+        proxy_pass http://dyolink_backend;
+        proxy_http_version 1.1;
+        proxy_set_header Upgrade $http_upgrade;
+        proxy_set_header Connection 'upgrade';
+        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;
+        proxy_cache_bypass $http_upgrade;
+        proxy_read_timeout 300;
+        proxy_connect_timeout 300;
+    }
+
+    location /health {
+        access_log off;
+        return 200 "healthy\n";
+        add_header Content-Type text/plain;
+    }
+}
--- a/infrastructure/nginx/http-only.dev.conf
+++ b/infrastructure/nginx/http-only.dev.conf
@@ -0,0 +1,54 @@
+# Dev docker-compose only: local `npm run dev` uses port 3001 (see frontend package.json).
+# Staging / registry stacks use http-only.conf (frontend:3000).
+
+upstream dyolink_backend {
+    server backend:3000;
+    keepalive 32;
+}
+
+upstream dyolink_frontend {
+    server frontend:3001;
+    keepalive 32;
+}
+
+server {
+    listen 80;
+    listen [::]:80;
+    server_name _;
+
+    client_max_body_size 50M;
+
+    location / {
+        proxy_pass http://dyolink_frontend;
+        proxy_http_version 1.1;
+        proxy_set_header Upgrade $http_upgrade;
+        proxy_set_header Connection 'upgrade';
+        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;
+        proxy_cache_bypass $http_upgrade;
+        proxy_read_timeout 300;
+        proxy_connect_timeout 300;
+    }
+
+    location /api {
+        proxy_pass http://dyolink_backend;
+        proxy_http_version 1.1;
+        proxy_set_header Upgrade $http_upgrade;
+        proxy_set_header Connection 'upgrade';
+        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;
+        proxy_cache_bypass $http_upgrade;
+        proxy_read_timeout 300;
+        proxy_connect_timeout 300;
+    }
+
+    location /health {
+        access_log off;
+        return 200 "healthy\n";
+        add_header Content-Type text/plain;
+    }
+}
Author	SHA1	Message	Date
Admin	00207786f9	improvement: workflow bypassed temporarily.	2026-05-05 16:29:44 +03:30
Admin	7dfff53c71	improvement: workflow bypassed temporarily.	2026-05-05 16:21:31 +03:30
Admin	517ce0d5ba	improvement: workflow updated for git actions.	2026-05-05 00:33:30 +03:30
Admin	d03ecdfc7c	Merge branch 'master' into improvement/infrastructure	2026-05-05 00:04:36 +03:30
Admin	15ef17228f	improvement: fixed some package.json issues. readme files updated.	2026-05-05 00:01:06 +03:30
admin	f943b2c7be	Merge pull request 'improvement: docker infrastructure overhauled.' (#10 ) from improvement/infrastructure into master Some checks failed Registry — build, push, deploy / build-and-push (push) Failing after 29s Details Registry — build, push, deploy / deploy (push) Has been skipped Details Reviewed-on: http://178.131.50.201:3000/admin/dyolink/pulls/10	2026-05-03 20:32:33 +03:30
Admin	4c61885cef	improvement: a port issue for local dev fixed.	2026-05-03 20:29:58 +03:30
Admin	5682da87aa	improvement: docker infrastructure overhauled.	2026-05-03 20:15:39 +03:30
admin	a05249e343	Merge pull request 'improvement: dashboard UX improved' (#9 ) from improvement/dashboard-ux-improvements into master Reviewed-on: http://178.131.50.201:3000/admin/dyolink/pulls/9	2026-04-30 18:53:08 +03:30