System administrator, integrator
Installing EAS on the server
Deployment on Ubuntu, first login to the admin panel and checking the work.
- 1
Prepare the server
Ubuntu 22.04+. **Minimum for a pilot:** 2 cores, 4 GB RAM, 80 GB SSD - up to ~8 cameras, 30 sensors, 2 controllers. For a large object, see separate instructions for calculating hardware (100 cameras / 100 sensors / 10 controllers - guideline 12–16 cores, 32 GB RAM, 2–4 TB for archive). Static IP, ports 8000 (admin panel) and access of access control panels to the server.
Tip: Detailed tables: /docs/server-sizing/
- 2
Run the installer
On the Ubuntu server, run one command (see the block below) - the script will download the current bundle from the hub (manifest.json), unpack and launch the native installation: PostgreSQL, Python venv, eas-server, Home Assistant, first setup wizard. Time: from 30 minutes to 2 hours.
curl -fsSL https://asceas.ru/eas-hub/install/install-eas-from-hub.sh | sudo EAS_ACCEPT_EULA=1 bash -s -- --accept-eula
Tip: Without Home Assistant: curl -fsSL https://asceas.ru/eas-hub/install/install-eas-from-hub.sh | sudo EAS_ACCEPT_EULA=1 bash -s -- --accept-eula --without-ha. Release manifest: https://asceas.ru/eas-hub/manifest.json
- 3
What has already been done automatically
After the wizard, the following work without manual commands: the eas-server service (admin panel :8000), the home-assistant service (:8123), the “Local Home Assistant” entry (127.0.0.1:8123) in the EAS database. Check: systemctl is-active eas-server home-assistant and curl -s -o /dev/null -w "%{http_code}" http://127.0.0.1:8123/ - usually 302 (onboarding page).
Tip: For HA out of the box, ≥4GB RAM is recommended. On weak VMs the first response :8123 may take 10-20 minutes after pip.
- 4
Login to the EAS admin panel for the first time
Open http://<server IP>:8000/admin, log in with the credentials from eas.bootstrap.credentials and change the password. The wizard in non-interactive mode (curl | bash) creates the admin user automatically.
Tip: For HTTPS, configure nginx or Caddy before uvicorn - do not leave only HTTP in production.
- 5
Onboarding Home Assistant (browser only)
Home Assistant cannot be fully configured from the terminal: open http://<IP server>:8123, create an HA administrator account (name, password, time zone, geolocation). This is a separate password from EAS - not to be confused with admin in eas.bootstrap.credentials.
Tip: If :8123 does not open: journalctl -u home-assistant -n 50 - wait until pip finishes when installing for the first time.
- 6
HA token and link to EAS
In Home Assistant: profile (bottom left icon) → “Security” → “Long-living access tokens” → “Create token”. Copy the line. In EAS: “Administration” → “Home Assistant” (or “Integrations” → “Open Home Assistant” button) → next to the “Local Home Assistant” line, click “Token / change” → insert the token → save → “Synchronize entities”.
Tip: Alternative for HA in another subnet: "HA Wizard" button on the same page (subnet + token).
- 7
Check the server status
Log in as administrator. The header displays the login, role and theme of the interface. Open “Administration → Server and Services” - make sure that the eas-server service is active and the disk is not full.
- 8
Activate your license
Go to the “License” tab, enter the trial or permanent license key and click “Activate”. Without a license, some functions will be limited.
