CorefinityCorefinityDocs
Open the Control PanelControl Panel
Platforms · 3 of 4

What a Laravel site has on Corefinity, what differs there, and its queue workers and scheduler.

On this page

A Laravel site runs on PHP, nginx, MariaDB and Redis, with queue workers and the scheduler already running. A new site is an empty site to deploy into, or a fresh application with no admin login.

What differs on Corefinity

ConfigurationThe application's .env reads the database settings from the site (DB_*).
Deployments.env and storage are kept between deployments. See Connect a repository.
MigrationsA deployment runs php artisan migrate --force only when its pipeline is set to. See Pipeline.
Queue workersWorkers run php artisan queue:work beside the site: 1 on sizes S and M, 2 on L.
Schedulerphp artisan schedule:run runs every minute as a built-in scheduled task. See Scheduled tasks.
Web rootpublic, with uploads in storage/app/public.

Queue workers and scheduler

Software & services adds Queue workers and Scheduler to the Services card.

Details… beside Queue workers shows the command the workers run and the jobs waiting on each queue.

Reload workers makes them finish their current job, then start again on the latest code; deployments do this for you.

The Laravel section

The site page has a Laravel section, under Overview. Each tool shows the Artisan command it runs; Platform tools covers running them.

ToolWhat it does
Clear cachesClears the config, route, view, event and application caches.
Reload queue workersTells the workers to finish their current job and start again on the latest code.
Run migrationsRuns outstanding migrations. A backup is taken first unless you untick it.
Link storageCreates the public/storage link to storage/app/public.
Was this helpful?
Open in ClaudeOpen in ChatGPT