furt/furt-lua
michael 0abc9791d3 fix(deployment): resolve OpenBSD rc.d service tracking and deployment workflow
- Fix OpenBSD service file pexp pattern to match actual running process
- Set pexp after sourcing rc.subr to prevent automatic override
- Update deployment script process detection from broken furt-lua pattern
- Add TTY-based daemon detection in start.sh for service vs development mode
- Implement comprehensive deployment workflow with backup and health checks
- Enable proper rcctl start/stop/check functionality on OpenBSD

Root cause: OpenBSD rc.subr automatically generates pexp from daemon+flags,
but actual process (/usr/local/bin/lua src/main.lua) differs from wrapper
(start.sh). Solution: Override pexp after rc.subr with correct Lua pattern.

Deployment script also had incorrect process detection pattern looking for
'furt-lua' string that doesn't exist in process name.

Technical details:
- Service file: pexp="/usr/local/bin/lua src/main.lua.*" after rc.subr
- Process detection: pgrep -u _furt -f 'src/main.lua'
- TTY detection: [ ! -t 0 ] for daemon vs interactive mode
- Complete deployment workflow with stop/sync/start/health-check cycle

Fixes #77 - OpenBSD rc.d service file problem resolved
Related: Deployment automation now fully functional karl→walter
2025-06-23 19:44:21 +02:00
..
config feat(smtp): complete native Lua SMTP integration for production mail delivery 2025-06-19 09:52:15 +02:00
deployment/openbsd fix(deployment): resolve OpenBSD rc.d service tracking and deployment workflow 2025-06-23 19:44:21 +02:00
scripts fix(deployment): resolve OpenBSD rc.d service tracking and deployment workflow 2025-06-23 19:44:21 +02:00
src feat(smtp): implement universal SSL compatibility for luaossl and luasec (#74) 2025-06-23 08:27:59 +02:00
tests feat(furt): implement complete Lua HTTP-Server for digital sovereignty (#63) 2025-06-17 20:40:40 +02:00
README.md feat(furt): implement complete Lua HTTP-Server for digital sovereignty (#63) 2025-06-17 20:40:40 +02:00

Furt Lua HTTP-Server

Pure Lua HTTP-Server für Dragons@Work API-Gateway
Week 1 Implementation - Digital Sovereignty Project

Überblick

Furt ist der erste Schritt zur Migration des API-Gateways von Go auf C+Lua für maximale digitale Souveränität. Diese Implementierung startet mit reinem Lua und bildet die Grundlage für die spätere C+Lua-Hybridarchitektur.

Funktionen

  • HTTP-Server mit lua-socket
  • JSON API Endpoints
  • Request/Response Parsing
  • Basic Routing
  • Mail-Service-Grundgerüst
  • Health-Check
  • Error Handling
  • Automated Tests

Dependencies

Erforderlich:

  • lua 5.4+
  • lua-socket (HTTP-Server)
  • lua-cjson (JSON-Verarbeitung)

Arch Linux:

pacman -S lua lua-socket lua-cjson

Ubuntu:

apt install lua5.4 lua-socket lua-cjson

Projektstruktur

furt-lua/
├── src/
│   └── main.lua              # HTTP-Server (< 200 Zeilen)
├── config/
│   └── server.lua            # Konfiguration 
├── scripts/
│   ├── start.sh              # Server starten
│   └── test_curl.sh          # Manuelle Tests
├── tests/
│   └── test_http.lua         # Automatische Tests
└── README.md

Installation & Start

1. Repository Setup:

mkdir furt-lua
cd furt-lua

# Dateien erstellen (aus Claude-Artefakten)
# main.lua, config/server.lua, scripts/start.sh, etc.

2. Executable machen:

chmod +x scripts/start.sh
chmod +x scripts/test_curl.sh

3. Server starten:

./scripts/start.sh

Server läuft auf: http://127.0.0.1:8080

API-Endpoints

Health Check

GET /health
→ {"status":"healthy","service":"furt-lua","version":"1.0.0"}

Test Endpoint

POST /test
Content-Type: application/json
{"test": "data"}{"message":"Test endpoint working"}

Mail Service

POST /v1/mail/send
Content-Type: application/json
{
  "name": "Test User",
  "email": "test@example.com", 
  "message": "Test message"
}{"success":true,"message":"Mail queued for sending"}

Testing

Automatische Tests:

# Server muss laufen!
lua tests/test_http.lua

Manuelle curl-Tests:

./scripts/test_curl.sh

Quick Test:

curl -X POST http://127.0.0.1:8080/test \
     -H "Content-Type: application/json" \
     -d '{"test":"data"}'

Konfiguration

Mail-SMTP (Environment Variables):

export FURT_MAIL_USERNAME="your_email@dragons-at-work.de"
export FURT_MAIL_PASSWORD="your_password"

Server-Config: config/server.lua

  • Port, Host ändern
  • API-Keys definieren
  • SMTP-Einstellungen

Week 1 Status

Tag 1: HTTP-Server basic functionality
Tag 2: Request/Response parsing
Tag 3: JSON handling, Mail endpoint structure
Tag 4: Routing, Error handling
Tag 5: Testing, Documentation

Success Criteria erreicht:

  • curl -X POST http://localhost:8080/test → HTTP 200 ✓
  • Alle Module < 200 Zeilen ✓
  • JSON Request/Response ✓
  • /v1/mail/send Endpoint ✓

Nächste Schritte (Week 2)

  1. SMTP-Integration - Echte Mail-Versendung
  2. API-Key-Authentication - Security-Layer
  3. Hugo-Integration - POST-based Form-Handling
  4. HTTPS mit lua-ssl

Technologie-Philosophie

  • Lua: PUC-Rio University (echte Unabhängigkeit)
  • Minimale Dependencies: < 5 externe Libraries
  • Modulare Architektur: < 200 Zeilen pro Datei
  • Transparenter Code: Jede Zeile verstehbar
  • Corporate-frei: Keine Google/Microsoft/etc. Dependencies

Teil der Dragons@Work Tech-Souveränitätsstrategie

Development

Code-Stil:

  • Module < 200 Zeilen
  • Funktionen < 50 Zeilen
  • Klare, lesbare Namen
  • Error-Handling für alles

Testing-Pattern:

  • Jede Funktion testbar
  • HTTP-Integration-Tests
  • curl-basierte Verifikation

Week 1 Challenge: COMPLETE
Foundation für souveräne API-Gateway-Architektur gelegt.