# Deployment Architecture — Zammad

> **Terakhir Diperbarui:** 2026-07-02

---

## Topology

```
Internet
   │
   ▼
10.100.1.24 (proxy.lan)
   ├── nginx :443  zammad.gisportal.id
   └── /opt/stacks/zammad/
         ├── zammad-railsserver
         ├── zammad-nginx (internal, upstream compose)
         ├── zammad-elasticsearch
         ├── zammad-redis
         └── zammad-init (one-shot)

10.100.1.25 (main-db)
   └── PostgreSQL database: zammad

10.100.1.10 (qnap)
   └── QuObjects :8010  bucket zammad-attachments

10.100.1.40 (AD)
   └── LDAP :389
```

---

## Keputusan deploy

| Topik | Keputusan |
|-------|-----------|
| App host | `10.100.1.24` (sama dengan my-portal, geonet-console) |
| PostgreSQL | **Eksternal** di `10.100.1.25` — DB server murni |
| Elasticsearch | **Enabled** di compose (RAM 62 GB cukup) |
| Object storage | **S3** ke QNAP, bukan disk lokal untuk attachment |
| Jira VM `.55` | **Tidak dipakai** |

---

## Path server

| Item | Path |
|------|------|
| Compose stack | `/opt/stacks/zammad/` |
| Nginx vhost | `/etc/nginx/conf.d/production/zammad.conf` |
| OSS cred reference | `/opt/stacks/geonet-console/.env` |

---

## Resource estimate (post-install)

| Service | RAM (perkiraan) |
|---------|-----------------|
| Zammad Rails + workers | 2–4 GB |
| Elasticsearch | 4–8 GB |
| Redis | <512 MB |

Monitor dengan `docker stats` setelah go-live.