Get Alphie running on a fresh Linux server with the new guided installer. Fewer questions, automatic setup, and a secure HTTPS entry point.
Use a fresh AlmaLinux, Rocky Linux, or RHEL 9 server with repository access and permission to install system packages. Run the installer as root. The installer intentionally stops if Alphie is already installed or the local PostgreSQL cluster already exists.
Make sure your installer bundle includes the following files in the same directory structure:
install_alphie_core_system_python.sh
alphie/ # frontend and backend
system/alphie.service
nginx/alphie.conf
scripts/db/alphie_db_schema_out/ # Core SQL schema
scripts/db/default_add.sql # initial dataThe shell script alone is not a complete installer bundle; it relies on these accompanying files.
From the directory containing the installer and its supporting folders:
sudo bash ./install_alphie_core_system_python.sh
You'll see the detected operating system and a confirmation prompt:
Type yes to continue. Any other response cancels the installation without proceeding.
Choose local for a PostgreSQL database hosted on the Alphie controller, or external for an existing PostgreSQL server. The local option is the default.
The installer initializes a fresh local PostgreSQL cluster, creates the database and user, then imports Alphie's Core schema and initial data.
Select external and supply the hostname/IP and port:
The external database and login role must already exist, be reachable, allow the supplied credentials, and have an empty public schema. Alphie creates the schema and seed data, but the installer does not provision a remote PostgreSQL server.
Enter the hostname users will browse to. The installer configures Nginx and gives you a choice of supplying an existing TLS certificate or generating a self-signed one.
If you choose y for an existing certificate, you'll be asked for the certificate file and private key file paths. Otherwise, Alphie creates a self-signed certificate automatically. Browsers may warn about self-signed certificates until the issuing certificate is trusted.
After the API passes its readiness check, the installer prompts for your initial local administrator.
The admin password must contain at least 8 characters. The installer also prints a newly created API client secret: save it securely when displayed. The samples above are illustrations, not screenshots from an actual install; no real credentials are shown.
Open https://your-alphie-hostname, sign in with the account you just created, and check the system services:
sudo systemctl status alphie.service
sudo systemctl status nginx
sudo systemctl status postgresql # local database only
sudo journalctl -u alphie.service -n 100 --no-pager
/opt/alphie/etc/alphie/alphie.env127.0.0.1:8000HTTPS · port 443Alphie uses a single Gunicorn/Uvicorn worker for the existing live-log behavior. Nginx fronts the application over HTTPS. If firewalld is active, the installer enables the HTTPS service; it does not open port 8000 for external access.
/opt/alphie, /etc/alphie/alphie.env, the systemd unit, or Nginx's Alphie configuration. It is not an upgrade installer.journalctl -u alphie.service -n 90 --no-pager to inspect the Gunicorn/API startup logs.