First run

After the container starts for the first time, you need to run database migrations (if you have not already done so via the entrypoint) and create the first user account so you can log in to the panel.

Running migrations

Via the Docker entrypoint (recommended)

Set RUN_MIGRATIONS=true (the default) when starting the container. The entrypoint runs php artisan migrate --force automatically after the database becomes reachable, before Octane starts.

docker run ... -e RUN_MIGRATIONS=true noixdev/inventorix:latest

You will see migration output in the container logs:

Waiting for database at db:3306...
Database is up.
...
Running migrations.

Manual migration

If RUN_MIGRATIONS is false, run migrations manually with docker exec:

docker exec -it <container_name> php artisan migrate --force

Or, outside Docker, from the application root:

php artisan migrate --force

Creating the first admin user

Inventorix does not ship a make:filament-user command (the generic Filament installer). The first user is created by running the database seeder.

Caution

The DatabaseSeeder creates a demo user with the password Start23!. Change this password immediately after first login. The seeder is intended for development and initial setup only — do not run it on an instance that already has production data.

Run the seeder:

docker exec -it <container_name> php artisan db:seed

This creates a user with the following credentials:

Field	Value
Email	hello@noix.dev
Password	Start23!
Name	noix
Panel access	enabled (login_enabled = true)

After logging in, go to Settings → General Settings to update the application name and other defaults, then navigate to the Users resource to create your own user account and disable or delete the seed user.

First login

1. Open your browser at http://<host>:8000 (or your configured APP_URL).
2. Log in with the seeded credentials above.
3. You will land on the panel dashboard, which shows asset stats and warranty widgets.

Tip

If you have Microsoft Entra ID configured (MS_LOGIN_ENABLED=true), the login page also shows a “Login via Entra ID” button. You can use either method.

Queue worker (Horizon)

The Octane server that the entrypoint starts handles HTTP requests, but queued jobs (such as CSV import processing and warranty digest emails) require a running Horizon process.

Start Horizon in a second container with the same image:

docker run -d \
  --env-file .env.production \
  --name inventorix-horizon \
  noixdev/inventorix:latest \
  php artisan horizon

Confirm Horizon is running by visiting /horizon on your app container. You should see the Horizon dashboard with a green “Running” status.

Note

If Horizon is not running, queued jobs will not be processed. Asset CSV imports triggered from the panel will appear to hang until a worker picks them up. Warranty notification emails sent via warranty:scan-expiries do not go through the queue (they are sent synchronously by the command), so they work without Horizon.

Verify the installation

After first login and Horizon startup, confirm everything is working:

1. Create a Manufacturer, an Asset Type, and an Asset Model under their respective resources.
2. Create a test Asset and verify it appears in the asset list.
3. Navigate to QR Code Generator and generate a QR code for the test asset.
4. Navigate to Evaluation and open any report to confirm PDF rendering works.
5. Check /horizon and confirm the queue worker shows “Running”.