How weitgraven/tela works
Tela is a self-hosted hosting control panel. An administrator signs in to the web panel, uses feature screens to request hosting changes, and the panel API delegates privileged work to a local Unix-socket agent; the agent validates and dispatches named actions that configure server services. Separate feature branches cover websites, databases, DNS, mail, backups, and WordPress. The README documents all of these capabilities, although several corresponding source modules were not excerpted, so their internal calls are not inferred here.
Main entry points: registry.py Action registry · actions/websites.py Website actions · dns.py DNS actions · api/websites.py Website API
Components 22
Panel
- Panel UI
web/app.js - Authentication
src/tela/api/auth.py - Website API
src/tela/api/websites.py - Feature APIs
src/tela/api - Panel database
src/tela/db.py - Agent client
src/tela/agent_client.py
Privileged agent
- Agent server
src/tela_agent/server.py - Action registry
src/tela_agent/registry.py - Input validation
src/tela_agent/validate.py
Hosting features
- Website actions
src/tela_agent/actions/websites.py - Database actions
src/tela_agent/actions/databases.py - DNS actions
src/tela_agent/actions/dns.py - Mail actions
src/tela_agent/actions/mail.py - Backup actions
src/tela_agent/actions/backups.py - WordPress actions
src/tela_agent/actions/wordpress.py
Server services
- Web server config
src/tela_agent/ols.py - Host operations
src/tela_agent/sysops.py - MariaDB
src/tela_agent/mariadb.py - Cloudflare
src/tela_agent/cloudflare.py - PowerDNS
src/tela_agent/powerdns.py - Restic backups
src/tela_agent/restic.py
Other components
- Administrator
Connections 28
- Administrator → Panel UI: uses
- Panel UI → Website API: requests changes
- Panel UI → Feature APIs: requests features
- Website API → Authentication: checks identity
src/tela/api/websites.py - Website API → Panel database: reads ownership
src/tela/api/websites.py - Website API → Agent client: calls agent
src/tela/api/websites.py - Feature APIs → Agent client: delegates actions
src/tela/api/common.py - Authentication → Panel database: stores sessions
- Agent client → Agent server: sends socket request
- Agent server → Action registry: dispatches action
src/tela_agent/server.py - Action registry → Website actions: routes actions
src/tela_agent/actions/websites.py - Action registry → Database actions: routes actions
src/tela_agent/actions/databases.py - Action registry → DNS actions: routes actions
src/tela_agent/actions/dns.py - Action registry → Mail actions: routes actions
src/tela_agent/actions/mail.py - Action registry → Backup actions: routes actions
- Action registry → WordPress actions: routes actions
src/tela_agent/actions/wordpress.py - Website actions → Input validation: validates input
src/tela_agent/actions/websites.py - Database actions → Input validation: validates input
src/tela_agent/actions/databases.py - Website actions → Web server config: configures sites
src/tela_agent/actions/websites.py - Website actions → DNS actions: adds site records
src/tela_agent/actions/websites.py - Database actions → MariaDB: manages databases
src/tela_agent/actions/databases.py - DNS actions → Cloudflare: edits zones
src/tela_agent/actions/dns.py - DNS actions → PowerDNS: manages zones
src/tela_agent/actions/dns.py - Mail actions → DNS actions: adds mail records
src/tela_agent/actions/mail.py - Backup actions → Restic backups: runs snapshots
- WordPress actions → Backup actions: uses backup actions
src/tela_agent/actions/wordpress.py - Website actions → Host operations: manages host users
src/tela_agent/actions/websites.py - Website actions → DNS actions: checks name conflicts
src/tela_agent/actions/websites.py