Solution skill
Deploy a Laravel app on self-hosted Stormkit via Admin runtime settings
Complete solution
Shows how to fix deploy a Laravel app on self-hosted Stormkit via Admin runtime settings. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Go to your Profile, then Admin, then the Runtimes section, and add two runtimes: nix:php at version 8.5, and nix:php85Packages.composer at latest. The composer package must match the PHP version: using nix:phpPackages.composer installs an older composer and will trip you up.
Steps
- You can deploy a Laravel app on self-hosted Stormkit today. Go to your Profile, then Admin, then the Runtimes section, and add two runtimes: nix:php at version 8.5, and nix:php85Packages.composer at latest. The composer package must match the PHP version: using nix:phpPackages.composer installs an older composer and will trip you up. A working setup the maintainer verified: install command composer update && composer install --no-dev --prefer-dist --optimize-autoloader, build command php artisan key -generate && php artisan config:cache && php artisan route:cache && php artisan view:cache, output and build folder both ./, and start command php -S the all-interfaces address:9007 -t public with a PORT env var set to 9007. Known rough edges: the port is not assigned dynamically yet, and you may need php artisan config:clear && php artisan route:clear && php artisan cache:clear after deploy unless SESSION_DRIVER is database or redis.
- Source: https://github.com/stormkit-io/stormkit-io/issues/2 (Stormkit)
When to use
You are seeing this: You can deploy a Laravel app on self-hosted Stormkit today. Use this skill when you run into "Deploy a Laravel app on self-hosted Stormkit via Admin runtime settings".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
Versions mentioned in the source: 8.5. If you are on something much newer or older, the details may have shifted.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Sources
- https://github.com/stormkit-io/stormkit-io/issues/2
Evidence
In gh:stormkit-io/stormkit-io#2, the issue was: A feature request asked for first-class Laravel deployment on Stormkit. The maintainer investigated installing PHP through the mise runtime manager, worked through compile dependencies, and landed on a scalable approach: install PHP and Composer as admin-level runtimes. In the admin area, under Runtimes, add nix:php version 8.5 and nix:php85Packages.composer version latest. They then proved the flow works end to end with a sample app, including install, build, and start commands, and closed the issue as solvable. The requester thanked them.. The verified answer: You can deploy a Laravel app on self-hosted Stormkit today. Go to your Profile, then Admin, then the Runtimes section, and add two runtimes: nix:php at version 8.5, and nix:php85Packages.composer at latest. The composer package must match the PHP version: using nix:phpPackages.composer installs an older composer and will trip you up.. Issue URL: https://github.com/stormkit-io/stormkit-io/issues/2
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_3qme_B4QEDMuPraTFfU8rw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Deploy a Laravel app on self-hosted Stormkit via Admin runtime settings <span>— Vectle</span></a>