Chuckcms Laravel Package

Getting Started

Install the package via Composer:

composer require chuckbe/chuckcms

Publish configuration and assets, then run migrations:

php artisan vendor:publish --provider="ChuckCMS\ChuckCmsServiceProvider" --tag=config
php artisan vendor:publish --provider="ChuckCMS\ChuckCmsServiceProvider" --tag=assets
php artisan migrate

Start by reviewing config/chuckcms.php and the package’s route files. The first practical use case is bootstrapping an admin panel: create an admin user (registration is disabled by default in v0.2.15, so use a seeder or php artisan tinker), assign the necessary roles/permissions, then visit /admin (or the configured admin path) to create your first page or module entry.

Implementation Patterns

• Admin scaffolding – Use the package’s built-in models and controllers as a base for custom modules. Extend or override controllers via route model binding and view composers rather than editing vendor files.
• Datatable listings – The release bumps datatable dependencies and adds select datatable support. Use this for related-data pickers (e.g., selecting a parent page or file manager folder) inside your own custom admin screens.
• File manager integration – The package now attaches permissions to file manager routes. In your own modules, mirror this by wrapping file manager actions in can: middleware or @can directives so uploads and deletions respect role assignments.
• Permissions-first defaults – Registration is disabled by default from v0.2.15. Treat user creation as an explicit administrative action: seed roles/permissions in a dedicated seeder, then create users through the admin UI (if enabled) or an Artisan command.
• Module workflow – Define module metadata in config, then use the package’s datatable and form builders to keep CRUD screens consistent. For custom logic, hook into the package’s service provider events or publish and extend its views.

Gotchas and Tips

• Registration is off by default – After upgrading to v0.2.15, new installs will not expose /register. Either enable it in config (if appropriate) or document an internal user-creation path (seeder, Artisan command, or admin panel).
• File manager permissions are route-level – The new permission checks apply to the package’s file manager routes. If you have custom file manager endpoints, add equivalent authorization yourself.
• Datatable dependency bump – If you have published or overridden datatable assets, re-publish assets and check for JavaScript API changes, especially around the new select extension.
• Clear caches after config changes – Run php artisan config:clear and php artisan permission:cache-reset (if using Spatie permissions) after changing defaults or permissions, especially in local development.
• Early-stage API – This is a 0.x release; pin the version in composer.json and review changelogs before upgrading. Extension points (events, view composers, route overrides) are safer than subclassing internal classes.