Deploy Capell like the Laravel app it is
Capell is not a hosted CMS sitting beside the application. It runs inside Laravel, so deployment should look like Laravel deployment: Composer packages, migrations, setup commands, queues, cache, assets, search, and smoke checks.
That makes CMS releases easier to reason about because content surfaces, package changes, and public delivery are part of the same operational workflow.
Deployment checks worth keeping
Deployment is where package-led capability becomes real. Capell favors setup commands and testable release steps over hidden manual admin work.
Deployment questions
Deploy Capell as application code, content fixtures, and package state that can be reviewed together.
Is Capell deployed separately from Laravel?
No. Capell runs in the Laravel app. Deploy Composer packages, migrations, config, assets, content seeders, and checks together.
Should search be rebuilt during release?
When CMS content or package data changes, search and discovery outputs should be refreshed as part of the release or post-release process.
Can deployment include public page checks?
Yes. Route smoke tests help catch missing pages, broken renderers, and accidental editor metadata leaks before users see them.
Release CMS changes with the app that owns them
Start with the install path, then connect deployment to operations so production releases include the CMS health checks your site depends on.