Laravel
What a Laravel site has on Corefinity, what differs there, and its queue workers and scheduler.
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
| Configuration | The application's .env reads the database settings from the site (DB_*). |
| Deployments | .env and storage are kept between deployments. See Connect a repository. |
| Migrations | A deployment runs php artisan migrate --force only when its pipeline is set to. See Pipeline. |
| Queue workers | Workers run php artisan queue:work beside the site: 1 on sizes S and M, 2 on L. |
| Scheduler | php artisan schedule:run runs every minute as a built-in scheduled task. See Scheduled tasks. |
| Web root | public, 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.
| Tool | What it does |
|---|---|
| Clear caches | Clears the config, route, view, event and application caches. |
| Reload queue workers | Tells the workers to finish their current job and start again on the latest code. |
| Run migrations | Runs outstanding migrations. A backup is taken first unless you untick it. |
| Link storage | Creates the public/storage link to storage/app/public. |
Related
Was this helpful?