- Install
laravel/fortify:^1.42and the package’s required Spatie Permission v8. - Exclude
laravel/fortifyandlaravel/passkeysfrom Laravel package discovery in the application’sextra.laravel.dont-discover. Studio registers Fortify only when standalone mode is enabled. Do not enable this mode over an existing Fortify installation; reuse host authentication there instead. - Publish/apply the usual Studio core migrations, Spatie permission migrations,
and
media-studio-auth-migrations. Never run the optional account migration in an existing host application merely to connect its user model. - Configure:
- Build/distribute the React assets under
packages/react/dist, or adapt the bundled views to your deployment’s asset publication. The optional provider serves the JS/CSS entry assets under/studio/auth/assets. - Create an initial account using
php artisan media-studio:account EMAIL --name=NAME. Passwords are entered using hidden prompts, not command-line arguments. - Set your real HTTPS
APP_URL, persistentAPP_KEY, private database/cache, secure session cookies and working mail configuration. Run the application’s normal scheduler/queue workers. Do not expose the loopback demo guard publicly.
TenantResolver and invitation/admission rules; changing the tenant model does
not migrate existing workspaces automatically. Registration grants Studio
operations within the registered account’s authorized workspace boundaries;
workspace membership and server authorization still apply to every resource.
The standalone module is not enabled in the existing local demo because its
existing library belongs to the demo principal. Enabling a new user database is
not an implicit migration of that identity or its workspace memberships.
SMTP and host mail integration
All Studio member/share invitations and standalone account emails use the same mail selection. Default behavior preserves the host application’s mailer:mail.default: