What's already configured
After the one-click deployment, Leneex brings up the official directus/directus Docker container on top of a connected database (typically PostgreSQL), with the required KEY, SECRET, and database connection variables already set — Directus won't start without them. The container is set to restart automatically on failure via Docker's restart policy, so there's no need to manage the process through systemd manually.
First login to Directus Studio
Directus doesn't pre-create an admin account in the database. On first access at your server's address, Studio shows an onboarding screen where you set the administrator's email and password yourself. Login details, or the relevant environment variables, are normally delivered in the Leneex account dashboard alongside the server info.
Working with data and automation
Directus doesn't generate its own database schema from scratch — it connects to an existing table structure, so the first practical step is usually creating the needed tables via a SQL client or directly from the Data Studio interface, which will offer to configure collections based on what it finds. For recurring tasks — webhook notifications, scheduled data syncs, or transformations — the built-in Flows module handles it visually, without writing code.