Files
admin 45363040f3 feat: Complete infrastructure cleanup phase documentation and status updates
## Major Infrastructure Milestones Achieved

###  Service Migrations Completed
- Jellyfin: Successfully migrated to Docker Swarm with latest version
- Vaultwarden: Running in Docker Swarm on OMV800 (eliminated duplicate)
- Nextcloud: Operational with database optimization and cron setup
- Paperless services: Both NGX and AI running successfully

### 🚨 Duplicate Service Analysis Complete
- Identified MariaDB conflict (OMV800 Swarm vs lenovo410 standalone)
- Identified Vaultwarden duplication (now resolved)
- Documented PostgreSQL and Redis consolidation opportunities
- Mapped monitoring stack optimization needs

### 🏗️ Infrastructure Status Documentation
- Updated README with current cleanup phase status
- Enhanced Service Analysis with duplicate service inventory
- Updated Quick Start guide with immediate action items
- Documented current container distribution across 6 nodes

### 📋 Action Plan Documentation
- Phase 1: Immediate service conflict resolution (this week)
- Phase 2: Service migration and load balancing (next 2 weeks)
- Phase 3: Database consolidation and optimization (future)

### 🔧 Current Infrastructure Health
- Docker Swarm: All 6 nodes operational and healthy
- Caddy Reverse Proxy: Fully operational with SSL certificates
- Storage: MergerFS healthy, local storage for databases
- Monitoring: Prometheus + Grafana + Uptime Kuma operational

### 📊 Container Distribution Status
- OMV800: 25+ containers (needs load balancing)
- lenovo410: 9 containers (cleanup in progress)
- fedora: 1 container (ready for additional services)
- audrey: 4 containers (well-balanced, monitoring hub)
- lenovo420: 7 containers (balanced, can assist)
- surface: 9 containers (specialized, reverse proxy)

### 🎯 Next Steps
1. Remove lenovo410 MariaDB (eliminate port 3306 conflict)
2. Clean up lenovo410 Vaultwarden (256MB space savings)
3. Verify no service conflicts exist
4. Begin service migration from OMV800 to fedora/audrey

Status: Infrastructure 99% complete, entering cleanup and optimization phase
2025-09-01 16:50:37 -04:00

66 lines
2.0 KiB
YAML

version: '3.9'
services:
paperless:
image: paperlessngx/paperless-ngx:2.10.3
environment:
PAPERLESS_REDIS: redis://redis_master:6379
PAPERLESS_DBHOST: postgresql_primary
PAPERLESS_DBNAME: paperless
PAPERLESS_DBUSER: postgres
PAPERLESS_DBPASS_FILE: /run/secrets/pg_root_password
# CSRF and reverse proxy configuration
PAPERLESS_URL: https://paperless.pressmess.duckdns.org
PAPERLESS_CSRF_TRUSTED_ORIGINS: https://paperless.pressmess.duckdns.org
PAPERLESS_ALLOWED_HOSTS: paperless.pressmess.duckdns.org
# Security settings for reverse proxy
PAPERLESS_USE_X_FORWARDED_HOST: true
PAPERLESS_USE_X_FORWARDED_PORT: true
PAPERLESS_SECURE_SSL_REDIRECT: true
# Additional security headers
PAPERLESS_SECURE_BROWSER_XSS_FILTER: true
PAPERLESS_SECURE_CONTENT_TYPE_NOSNIFF: true
PAPERLESS_SECURE_HSTS_INCLUDE_SUBDOMAINS: true
PAPERLESS_SECURE_HSTS_SECONDS: 31536000
secrets:
- pg_root_password
volumes:
- paperless_data:/usr/src/paperless/data
- paperless_media:/usr/src/paperless/media
networks:
- traefik-public
- database-network
deploy:
labels:
- traefik.enable=true
- traefik.http.routers.paperless.rule=Host(`paperless.pressmess.duckdns.org`)
- traefik.http.routers.paperless.entrypoints=websecure
- traefik.http.routers.paperless.tls=true
- traefik.http.routers.paperless.tls.certresolver=letsencrypt
- traefik.http.services.paperless.loadbalancer.server.port=8000
- traefik.http.routers.paperless.middlewares=security-headers@file
volumes:
paperless_data:
driver: local
driver_opts:
type: nfs
o: addr=omv800.local,nolock,soft,rw
device: :/export/paperless
paperless_media:
driver: local
driver_opts:
type: nfs
o: addr=omv800.local,nolock,soft,rw
device: :/srv/mergerfs/DataPool/pdfs
secrets:
pg_root_password:
external: true
networks:
traefik-public:
external: true
database-network:
external: true