DocsProduction

Production

Deploy Warriorfolio safely — Filament access, assets, Faker, and hosting notes.

Warriorfolio deploys like any Laravel 11 app, with two extra concerns: authorizing the Filament panel outside local, and optional Faker usage if you run seeders in production.

#On this page

Pre-flight checklist

Essential steps before deploy.

Step	Command / action
Env	Copy .env, set APP_ENV=production, APP_DEBUG=false, strong APP_KEY
URL	APP_URL with no trailing slash
Dependencies	composer install --no-dev --optimize-autoloader
Front build	npm ci && npm run build
Cache	php artisan config:cache && php artisan route:cache && php artisan view:cache
Storage	php artisan storage:link on the server
Migrations	php artisan migrate --force

403 on /admin (Filament)

In non-local environments, Filament may deny panel access until your User model explicitly allows it.

php

1<?php
2
3namespace App\Models;
4
5use Filament\Models\Contracts\FilamentUser;
6use Filament\Panel;
7use Illuminate\Foundation\Auth\User as Authenticatable;
8
9class User extends Authenticatable implements FilamentUser
10{
11    public function canAccessPanel(Panel $panel): bool
12    {
13        return str_ends_with($this->email, '@yourdomain.com') 
14            && $this->hasVerifiedEmail();
15    }
16}

Hosting

Compatible with Laravel Cloud, Forge, Vapor, VPS + Nginx, or any PHP 8.2+ host that supports Node for the build step.

Point the web root to public/
Schedule php artisan schedule:run if you add cron-dependent features
Run a queue worker if offloading mail or heavy jobs