Documentation for larsasub v0.12.0.
On an older version? Your release notes ship with the package (CHANGELOG.md).
Installation
LarsaSub is distributed through the private composer repository on larsasub.eu. Access is tied to your license: you authenticate with your account e-mail and a license token from the customer portal.
Requirements
- PHP ^8.3
- Laravel ^12.0 | ^13.0
- A LarsaSub license (pricing)
- Mollie API credentials (for payment processing)
1. Get your license token
After purchase you receive a license token by e-mail. You can create additional tokens and revoke old ones at any time under Licenses in the customer portal. A token's plain value is shown exactly once; store it in your secrets manager.
Create one token per environment (production, staging, CI): revoking one then never breaks the others. Token behavior, rotation and the update-window rules are covered in Licensing & repository.
2. Register the repository
In your application root:
composer config repositories.peters-development composer https://larsasub.eu
composer config http-basic.larsasub.eu you@company.com YOUR-LICENSE-TOKEN
This writes the credentials to auth.json. Add auth.json to .gitignore. In CI, provide the credentials via the COMPOSER_AUTH environment variable instead:
COMPOSER_AUTH='{"http-basic":{"larsasub.eu":{"username":"you@company.com","password":"YOUR-LICENSE-TOKEN"}}}'
3. Install the package
composer require peters-development/larsasub
php artisan larsasub:install
larsasub:install publishes the config, runs the migrations and seeds the payment methods. Continue with the quick start to make your first model billable.
Admin companions (optional, included)
License holders can also install the admin companions from the same repository, at no extra cost. Pick the one that matches the admin panel you already run:
composer require peters-development/larsasub-nova # Laravel Nova 5
composer require peters-development/larsasub-filament # Filament 5
The Filament companion is a panel plugin — register it on the panel that manages billing:
use PetersDevelopment\LarsaSub\Filament\LarsaSubPlugin;
$panel->plugins([LarsaSubPlugin::make()]);
How licensing affects updates
composer update serves every version released during your license period. After your license expires those versions remain installable, on fresh servers and in CI; you only stop receiving newer releases until you renew. The full rules, including token rotation and expiry semantics, are on Licensing & repository.
Troubleshooting
- 401 on install: the token was revoked or mistyped, or the e-mail doesn't match the account that owns the license. Check both in the portal. After rotating a token, remember that CI secrets and every server's
auth.jsonneed the new value too. - Version not found: the release was published after your license expired. Either pin an older version or renew.
- Dependency conflict on
guzzlehttp/guzzle: parts of the Mollie OAuth chain require Guzzle 7. If your app already uses Guzzle 8, install withcomposer require peters-development/larsasub -Wto allow the downgrade.