Weave Code
Installer Laravel Package
photoncms/installer
Photon CMS Installer streamlines setting up Photon CMS in a Laravel application. It walks through the installation workflow, publishing assets, configuring the CMS, and preparing your database so you can get a Photon-powered site running with minimal manual setup.
Photon CMS application installer.
Frequently asked questions about Installer
- What is photoncms/installer used for?
- It is a Composer package that streamlines setting up PhotonCMS inside a Laravel application. It runs a guided installation workflow, checks PHP extensions and permissions, and publishes config, assets, and migrations. It is not a runtime library; it is a one-time provisioning tool tied to PhotonCMS.
- How do I install photoncms/installer with Composer?
- On a compatible Laravel 5.x-era application, you would add it with Composer and run the installer's Artisan workflow. In practice, treat it as a provisioning-only dependency, pin an exact version, and commit your composer.lock. Do not add it to a modern Laravel production require block, because its PHP and illuminate constraints are unlikely to resolve.
- Which Laravel and PHP versions does PhotonCMS Installer support?
- The package targets the Laravel 5.x-era generation, roughly PHP 7.0 to 7.2. It is not built for Laravel 9, 10, or 11 on PHP 8.1+. Expect Composer dependency resolution to fail first, followed by removed-framework-API failures if constraints are relaxed by hand.
- Is photoncms/installer safe to use in production?
- No, it should not be reachable or runnable in production. Installers of this class can write .env, seed an admin user, run migrations, and register routes, so an exposed installer endpoint is a privilege-escalation risk. Verify route registration and self-disable behavior, and run it only in an ephemeral provisioning container or developer workstation.
- Does photoncms/installer register routes or Artisan commands?
- The package advertises Laravel-friendly Artisan command integration, and the security evaluation flags this installer class as potentially registering HTTP routes and Artisan commands. You must inspect the service provider to confirm exact route registration, guards, and post-install disable logic. Treat verification of route registration and self-disable behavior as a mandatory adoption gate.
- Is photoncms/installer idempotent if I run it again?
- Assume it is not idempotent. The evaluation warns that re-runs can overwrite .env, config, and storage scaffolding, and a failed migration or seed can leave a half-built schema without rollback. Use a throwaway container for each attempt and capture the post-install state as a versioned artifact.
- Should photoncms/installer be in require or require-dev?
- For an existing PhotonCMS deployment, put it in require-dev, pin an exact version, and commit the composer.lock. Run it only during provisioning in an ephemeral container, never as part of the production runtime. This keeps the installer out of the deploy path and limits its attack surface.
- How can I evaluate photoncms/installer before adopting it?
- Time-box a spike in a throwaway container against your target PHP and Laravel baseline. Success criteria should be a working admin login and a rendered content page, not merely a successful Composer install. Kill the spike if the framework constraints do not resolve cleanly.
- Is photoncms/installer maintained or abandoned?
- The evaluation reports zero stars, zero dependents, no visible test or CI signal, and no security policy or disclosure channel. The bus factor is one, and the adopting team owns vulnerability response end to end. That makes it a high-risk dependency even before considering framework drift.
- What alternatives exist to photoncms/installer?
- If you are not already on PhotonCMS, use Laravel's first-party installer or hand-roll your provisioning instead of adopting this package. If you are evaluating PhotonCMS itself, treat the installer as reference-only: read it for the expected directory layout and bootstrap sequence, then do not add it as a dependency. For modern Laravel projects there is no meaningful migration path from this installer.
Weaver
How can I help you explore Laravel packages today?