Install PagibleAI CMS in Laravel

Install PagibleAI CMS in an existing Laravel 11, 12 or 13 application. The core CMS works without an AI provider, so you only need API keys for the AI tools you intend to use.

Before you start, confirm that:

• Your Laravel application runs normally.
• Composer is available.
• Laravel can connect to your database.
• APP_URL contains the URL you use to open the application, including a local development port.

If you still need a Laravel application, follow the Laravel installation guide. Select Laravel 11 or 12 from the documentation version menu when that matches your application.

Create a Laravel project if you do not already have one:

composer create-project laravel/laravel pagible
cd pagible

Configure the database connection and APP_URL in .env before installing the CMS. For Laravel's local server, use:

APP_URL=http://localhost:8000

Install PagibleAI CMS from the application directory:

composer require aimeos/pagible
php artisan cms:install

The installer publishes the package configuration and assets, prepares the database, runs the migrations, and creates the public storage link. You do not need to run the initial migration a second time.

A successful installation ends with:

Congratulations! You successfully set up Pagible CMS!

Fresh Laravel applications contain a static public/robots.txt file, which web servers deliver before Laravel receives the request. If it contains custom rules, copy them into the robots.txt configuration element of the root page and publish the page. Then remove the static file to enable the dynamic route, which also adds the sitemap and news sitemap URLs:

rm public/robots.txt

Alternatively, configure the web server to pass /robots.txt to Laravel even when the static file exists. The same applies to /security.txt, which is generated from the security configuration element of the root page, if you have a static public/security.txt file. See robots.txt, security.txt and Sitemaps for details.

Grant the admin role to an existing application user:

php artisan cms:user --role=admin editor@example.com

Replace the address with the user's actual email address. If no matching user exists, the command creates one and asks you for a password.

Use the narrowest suitable role:

• viewer can read CMS content.
• editor can edit content but cannot publish or permanently delete it.
• publisher can manage and publish content.
• admin receives every CMS permission.

Run php artisan cms:user --roles to display the configured roles. See Authorization and Permissions for individual permissions, custom roles, and application authorization adapters.

Confirm that Laravel registered the admin route, then start the local server:

php artisan route:list --path=cmsadmin
php artisan serve

The route list should contain GET|HEAD cmsadmin/{path?} with the name cms.admin. For the local server, open http://localhost:8000/cmsadmin. In another environment, append /cmsadmin to the configured APP_URL. Sign in with the user you configured and check that you can:

• Open the page tree.
• Create and save a draft page.
• Upload an image or another file.
• Preview the draft without publishing it.

If an upload URL points to the wrong host or port, correct APP_URL and run php artisan optimize:clear.

Include these commands in your application update or deployment process after Composer installs new package versions:

php artisan vendor:publish --force --tag=cms-admin --tag=cms-graphql
php artisan vendor:publish --tag=cms-theme
php artisan migrate --force

The first command replaces the compiled administration assets and the GraphQL schema files. The theme command leaves existing published theme files untouched. Review theme changes before overwriting customized files. Use migrate --force only in a trusted, automated production deployment.

Add credentials only for the functions you use. For example:

GEMINI_API_KEY="..."
OPENAI_API_KEY="..."
DEEPL_API_KEY="..."

CMS_AI_WRITE_API_KEY="${GEMINI_API_KEY}"
CMS_AI_REFINE_API_KEY="${OPENAI_API_KEY}"
CMS_AI_TRANSLATE_API_KEY="${DEEPL_API_KEY}"

Each AI function has separate provider, model, API-key, and optional base-URL settings in the PagibleAI configuration. This lets you mix providers instead of configuring every supported service.

Keep credentials in environment variables or a secrets manager. Do not commit a populated .env file. After changing cached configuration, run php artisan optimize:clear.

Add only the features required by your application:

• Protect public forms with the hCaptcha configuration guide.
• Set CMS_MULTIDOMAIN=true when separate page trees must resolve through different domains.
• Use shared-database tenant isolation as described in Multi-Tenancy SaaS Setup. PagibleAI CMS does not support one database connection per tenant.
• Enable synchronized editor sessions with Real-Time Updates using Laravel Reverb.
• Send signed notifications to external services when content changes with the aimeos/pagible-webhooks package, as described in Webhooks.
• Purge changed pages and removed files from Cloudflare, Fastly or Varnish with the aimeos/pagible-cdn package, as described in CDN Cache Purging.
• If users sign in through single sign-on, set CMS_ADMIN_LOGIN to your login URL, e.g. https://example.com/login?redirect=_url_. When the session expires, the admin panel opens this page instead of asking for the password and replaces _url_ with the admin URL.
• When embedding the Vue administration interface in another Laravel backend, use the maintained PagibleAI admin layout as the source. It contains the current import map, routes, plugin data, storage settings, and optional Reverb configuration.

Before serving the CMS in production:

• Set APP_URL to the final HTTPS URL.
• Use persistent storage for uploaded files and include it in your backups.
• Run Laravel's scheduler every minute as described in Laravel task scheduling.
• Check registered tasks with php artisan schedule:list. The output should include cms:publish every 30 minutes and model:prune daily.
• Run a queue worker with an asynchronous queue connection. The CMS uses queued jobs, e.g. for refreshing the cache of pages that use a changed shared element or file, version pruning and file cleanup. Set CMS_QUEUE_CONNECTION and CMS_QUEUE to use a dedicated queue; the sync driver is supported too and runs the jobs inline. Search index updates are only queued if Laravel Scout's scout.queue setting is enabled; they then use Scout's queue connection.
• Use a managed web server and PHP process manager instead of php artisan serve.
• Rebuild cached configuration after environment changes.

PagibleAI CMS registers cms:publish every 30 minutes and model:prune daily. Do not add duplicate schedules to routes/console.php. Soft-deleted CMS records become eligible for pruning after 30 days by default.