bede/tfm_ainventory
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
574 Commits 97 Branches 7 Tags
dcc3f692f3af49b3fe70915bdfe5cdb67517c921
Commit Graph

3 Commits

Author SHA1 Message Date
Daniel Bedeleanu
0881b0ecee fix(6): resolve static asset serving and proxy header issues 
Fixed issues:
1. Caddy not forwarding X-Forwarded headers to Next.js
   - Added X-Forwarded-For, X-Forwarded-Proto, X-Forwarded-Host
2. Removed X-Content-Type-Options: nosniff (blocks static assets)
3. Copy static files to standalone build directory
   - Next.js standalone requires files in .next/standalone/.next/static/
4. Made script auto-copy static files after build

Result:
  ✓ CSS/JS loading with correct MIME types (text/css, text/javascript)
  ✓ Frontend fully rendering via HTTPS
  ✓ All static assets cached and served correctly
  ✓ Tested working via IP address (192.168.84.131:8919)
 2026-04-22 19:34:32 +03:00
Daniel Bedeleanu
0deef7f601 fix(6): make Caddy listen on any IP/hostname for HTTPS 
Changed from localhost-specific to wildcard listening:
  - https://:8918 (any IP on port 8918) → backend
  - https://:8919 (any IP on port 8919) → frontend

On-demand TLS generates certificates for any accessing IP/hostname
Self-signed certs now work via:
  - localhost
  - 127.0.0.1
  - 192.168.x.x (or any IP on network)
  - Any hostname

Tested and verified working via 192.168.84.131:8919
 2026-04-22 19:23:12 +03:00
Daniel Bedeleanu
6fa146fae2 feat(6): add Caddy reverse proxy with SSL to standalone deployment 
Complete feature parity with Docker deployment:
  - Caddy reverse proxy manages SSL/TLS
  - Ports: 8916/8917 (HTTP), 8918/8919 (HTTPS)
  - Self-signed certificates (development-friendly)
  - Automatic certificate generation via on-demand TLS
  - Security headers (HSTS, XSS Protection, etc.)

Changes:
  - Created Caddyfile.standalone for localhost config
  - Enhanced start_servers.py with Caddy startup/monitoring
  - Auto-install Caddy via apt if not present
  - Updated status output to show both HTTP and HTTPS URLs
  - All three services (backend, frontend, caddy) in one launcher

Both Docker and Standalone modes now have IDENTICAL capabilities:
  - Full production-ready SSL/TLS support
  - Reverse proxy with auto-certificate management
  - HTTPS-only capable

Resolves dual-deployment equivalence requirement
 2026-04-22 19:16:26 +03:00