Apache Reverse Proxy für api.dragons-at-work.de (Ready for aitvaras) #50

Closed
opened 2025-06-11 20:02:12 +02:00 by Michael · 1 comment
Michael commented 2025-06-11 20:02:12 +02:00 (Migrated from gitea.dragons-at-work.de)

📋 STATUS: READY FOR AITVARAS DEPLOYMENT

Backend is ready - needs Apache-ISPConfig setup on aitvaras

Current Status

  • Furt-Backend ready - Tested and working on walter
  • Domain prepared - api.dragons-at-work.de DNS ready
  • 📋 aitvaras-Deployment - Furt installation needed
  • ISPConfig-Proxy - VirtualHost configuration
  • SSL-Certificate - Let's Encrypt integration

Infrastructure Plan

Internet → aitvaras:443 (Apache SSL) → 127.0.0.1:8080 (Furt-Lua)

Apache VirtualHost (ISPConfig)

<VirtualHost *:443>
    ServerName api.dragons-at-work.de
    
    SSLEngine on
    # SSL certificates via ISPConfig/Let's Encrypt
    
    ProxyPreserveHost On
    ProxyPass / http://127.0.0.1:8080/
    ProxyPassReverse / http://127.0.0.1:8080/
    
    ProxySetHeader X-Forwarded-For %{REMOTE_ADDR}s
    ProxySetHeader X-Forwarded-Proto https
    ProxySetHeader X-Real-IP %{REMOTE_ADDR}s
</VirtualHost>

Deployment Steps

  1. Furt-Installation - deploy_aitvaras.sh (adaptation of deploy_walter.sh)
  2. ISPConfig-Website - Create api.dragons-at-work.de website
  3. Proxy-Configuration - Apache ProxyPass setup
  4. SSL-Integration - Let's Encrypt certificate
  5. Health-Check - https://api.dragons-at-work.de/health

Priority

High - Required for Hugo website integration and production contact forms

Dependencies

  • Furt-Backend functional
  • aitvaras server access
  • ISPConfig proxy configuration
  • DNS verification

Next Step: aitvaras deployment

## 📋 STATUS: READY FOR AITVARAS DEPLOYMENT **Backend is ready - needs Apache-ISPConfig setup on aitvaras** ## Current Status - [x] ✅ **Furt-Backend ready** - Tested and working on walter - [x] ✅ **Domain prepared** - api.dragons-at-work.de DNS ready - [x] 📋 **aitvaras-Deployment** - Furt installation needed - [x] ✅ **ISPConfig-Proxy** - VirtualHost configuration - [x] ✅ **SSL-Certificate** - Let's Encrypt integration ## Infrastructure Plan ``` Internet → aitvaras:443 (Apache SSL) → 127.0.0.1:8080 (Furt-Lua) ``` ## Apache VirtualHost (ISPConfig) ```apache <VirtualHost *:443> ServerName api.dragons-at-work.de SSLEngine on # SSL certificates via ISPConfig/Let's Encrypt ProxyPreserveHost On ProxyPass / http://127.0.0.1:8080/ ProxyPassReverse / http://127.0.0.1:8080/ ProxySetHeader X-Forwarded-For %{REMOTE_ADDR}s ProxySetHeader X-Forwarded-Proto https ProxySetHeader X-Real-IP %{REMOTE_ADDR}s </VirtualHost> ``` ## Deployment Steps 1. **Furt-Installation** - deploy_aitvaras.sh (adaptation of deploy_walter.sh) 2. **ISPConfig-Website** - Create api.dragons-at-work.de website 3. **Proxy-Configuration** - Apache ProxyPass setup 4. **SSL-Integration** - Let's Encrypt certificate 5. **Health-Check** - https://api.dragons-at-work.de/health ## Priority **High** - Required for Hugo website integration and production contact forms ## Dependencies - [x] ✅ Furt-Backend functional - [x] ✅ aitvaras server access - [x] ✅ ISPConfig proxy configuration - [x] ✅ DNS verification **Next Step**: aitvaras deployment
Michael commented 2025-06-24 11:07:48 +02:00 (Migrated from gitea.dragons-at-work.de)

PRODUCTION DEPLOYMENT SUCCESSFUL

Deployment completed: karl → aitvaras with deploy_aitvaras.sh

Infrastructure Status:

  • Backend: Furt-Lua running on aitvaras:8080
  • Service: systemd service furt-api active and enabled
  • Reverse Proxy: Apache ProxyPass configured
  • SSL: Let's Encrypt certificate active
  • Health Check: https://api.dragons-at-work.de/health responds correctly
  • SMTP: Configured and ready (smtp_configured: true)

Service Metrics:

  • Memory: 516.0K (peak: 2.0M) - excellent efficiency
  • CPU: 39ms startup time
  • Status: active (running) since 2025-06-24 11:06:27

API Endpoint: https://api.dragons-at-work.de

Next Steps:

  • Hugo-Integration ready for implementation
  • Production contact forms can be deployed
  • API-Gateway available for additional services (sagjan, etc.)

Issue #50 completed successfully! 🎉

## ✅ **PRODUCTION DEPLOYMENT SUCCESSFUL** **Deployment completed**: karl → aitvaras with deploy_aitvaras.sh **Infrastructure Status:** - ✅ **Backend**: Furt-Lua running on aitvaras:8080 - ✅ **Service**: systemd service furt-api active and enabled - ✅ **Reverse Proxy**: Apache ProxyPass configured - ✅ **SSL**: Let's Encrypt certificate active - ✅ **Health Check**: https://api.dragons-at-work.de/health responds correctly - ✅ **SMTP**: Configured and ready (`smtp_configured: true`) **Service Metrics:** - **Memory**: 516.0K (peak: 2.0M) - excellent efficiency - **CPU**: 39ms startup time - **Status**: active (running) since 2025-06-24 11:06:27 **API Endpoint:** https://api.dragons-at-work.de **Next Steps:** - Hugo-Integration ready for implementation - Production contact forms can be deployed - API-Gateway available for additional services (sagjan, etc.) **Issue #50 completed successfully!** 🎉
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: DAW/furt#50
No description provided.