Skip to main content
A Solution is an extension package: it adds flow actions and console screens to the platform. The Solutions page of the admin panel lists the Solutions installed on your installation; this page lists the ones you can find and install. On a platform you run yourself, that page links here through Find more Solutions.

​
Available Solutions

Building your own? See Building a Solution.

​
Installing a Solution

A Solution is a Composer package added on top of Core with a composer overlay, so Core’s own composer.json and composer.lock stay untouched.
1

Describe the package in composer.overlay.json

At Core’s root (the file is git-ignored), name the package’s repository and a version:
2

Install it

It installs the package against Core’s locked versions and refuses one that would move them. In an image or CI, add -- --require-overlay so a missing overlay file is an error.
3

Update the platform

It checks the Solution’s manifest and console interface, runs migrations and publishes the interface. A Solution that fails the checks is refused here and never reaches the admin panel.
4

Turn it on

Installing does not turn a Solution on. Each workspace turns it on from Solutions in the admin panel (Solutions), or with php artisan solutions:activate <id> --tenant=<slug>.
A plain composer install (an upgrade or a rebuild) drops the overlay package until composer overlay is run again, and later Composer commands run with COMPOSER=composer.local.json; see keep using the overlaid manifest. The overlay file, post-install steps and the options of composer overlay are described in Development setup. The Find more Solutions link is the platform setting solutions.marketplace_url, by default this page. Point it at your own catalogue, or make it empty to hide the link:
A platform that sells Solutions through an operator package shows its own offers instead, and no link.