Deploy your Enferno application to production
Enferno provides multiple deployment options to suit different needs. You can either use the automated Enferno CLI tool for quick Ubuntu server deployments, or follow the traditional deployment process for other environments.
The Enferno CLI tool automates the entire deployment process on Ubuntu servers with a single command.
The tool will guide you through the configuration process, prompting for necessary information like server hostname, credentials, and deployment options.
If you prefer manual deployment or need to deploy to a different environment, follow these steps:
Enferno supports both SQLite (default) and PostgreSQL databases. Choose one of the following options:
No additional configuration needed. The database will be created automatically when you run:
.env
configuration:Create a new Nginx configuration:
Create a service file /etc/systemd/system/enferno.service
:
Enable and start the service:
Create /etc/systemd/system/enferno-celery.service
:
Enable and start the worker:
FLASK_DEBUG=0
in .env
SECRET_KEY
Static files not found (404)
flask static
to collect static filesDatabase connection errors
.env
Application not starting
sudo journalctl -u enferno
Redis connection issues
sudo systemctl status redis
For more deployment options and troubleshooting, visit the Enferno CLI documentation.
Deploy your Enferno application to production
Enferno provides multiple deployment options to suit different needs. You can either use the automated Enferno CLI tool for quick Ubuntu server deployments, or follow the traditional deployment process for other environments.
The Enferno CLI tool automates the entire deployment process on Ubuntu servers with a single command.
The tool will guide you through the configuration process, prompting for necessary information like server hostname, credentials, and deployment options.
If you prefer manual deployment or need to deploy to a different environment, follow these steps:
Enferno supports both SQLite (default) and PostgreSQL databases. Choose one of the following options:
No additional configuration needed. The database will be created automatically when you run:
.env
configuration:Create a new Nginx configuration:
Create a service file /etc/systemd/system/enferno.service
:
Enable and start the service:
Create /etc/systemd/system/enferno-celery.service
:
Enable and start the worker:
FLASK_DEBUG=0
in .env
SECRET_KEY
Static files not found (404)
flask static
to collect static filesDatabase connection errors
.env
Application not starting
sudo journalctl -u enferno
Redis connection issues
sudo systemctl status redis
For more deployment options and troubleshooting, visit the Enferno CLI documentation.