Skip to content
Nevelav0.5.0
Nevela 0.5.0: users, roles and permissions: a Users screen, a Roles screen, and a dashboard that shows each person only what their role allows.Users, roles and permissions

Deploying

Nevela is two apps. Deploy each the way you would deploy any Laravel or Next.js app.

The Laravel app

Section titled “The Laravel app”
  • Use a production database rather than the SQLite file, and run php artisan migrate --force on each deploy.
  • Commit the generated code. Nothing is generated at deploy time, so the server does not need the web app’s folder.
  • Check who holds which role. A generated policy asks for a permission; in an app from before 0.5.0 the policies still allow any signed-in user until you change them.
  • Install with composer install --no-dev --optimize-autoloader. A new app has Composer’s optimized autoloader turned off, because building it made creating an app take minutes longer; production should have it, and the flag turns it on.
  • Run php artisan config:cache and php artisan route:cache as usual. Nevela’s routes are cached with the rest.

The web app

Section titled “The web app”

The web app needs one setting: NEVELA_API_URL, the address of the Laravel API including its prefix, for example https://api.example.com/api. The Next.js server must be able to reach that address; visitors’ browsers do not need to.

In production the token cookie is marked Secure, so the web app must be served over HTTPS.

Checklist

Section titled “Checklist”
  • Roles and policies reviewed, and the sample users deleted
  • NEVELA_API_URL points at the production API, with its prefix
  • Both apps served over HTTPS
  • At least one user created on the server with php artisan nevela:user. The starter admin@example.com account is not there, and should not be