Web

Saphira Linux webDragon

A Saphira feature that turns a normal installation into a managed web platform: Nginx, PHP-FPM 8.5 and Node.js, with TLS you do not have to babysit. You own the machine; webDragon removes the repetitive systems administration.

Tools included — beta state

Normal Saphira, not an appliance

webDragon does not introduce a parallel, proprietary system. It generates ordinary Nginx configuration, ordinary PHP-FPM pools and ordinary system service units, all from normal Saphira packages. The result is a web platform that looks like Saphira because it is Saphira.

NoteNothing is hidden behind an opaque layer. If you prefer to edit a virtual host by hand, you can — webDragon only rolls back its own transactions and will not fight manual changes outside of an install or enable operation.

Where the configuration lives

Virtual hosts — /etc/nginx/vhosts/<host>.conf (the generated, managed files).
Enabled sites — /etc/nginx/vhosts.enabled/<host>.conf, a symlink to the vhost.
PHP pools — /etc/php85/php-fpm.d/<host>.conf.
Logs — /var/log/nginx/<host>.access.log and <host>.error.log.
Site content — /srv/<host> (htdocs, server, app, css, js, images).

Nginx documentation

Environment overrides

For non-default layouts, saphira-site honours a small set of environment variables: SAPHIRA_NGINX_DIR (vhost directory), SAPHIRA_NGINX_ENABLED_DIR (enabled directory), SAPHIRA_PHP_DIR (PHP-FPM pool directory), SAPHIRA_LOG_DIR (Nginx logs) and SAPHIRA_SITE_ROOT_BASE (the base under which sites are created, default /srv). The defaults match a standard Saphira web server.

Understanding what was generated

Because the output is normal Nginx and PHP-FPM configuration, an administrator can read exactly what webDragon configured without reverse-engineering a database or a binary blob. Each managed virtual host is commented with the host it was generated for, and the underlying services and files are the ones a Saphira administrator already knows.