- What is shipu/web-installer used for?
- Shipu Web Installer adds a browser-based setup wizard to Laravel applications. It checks server requirements and folder permissions, configures the .env file and database connection, runs migrations, and creates the first admin user. It is intended for first-boot configuration when an operator cannot run CLI commands.
- How do I install shipu/web-installer in a Laravel app?
- Install it with Composer and rely on standard Laravel package auto-discovery, then publish its config and assets and use the installer routes. Pin the dependency to ^1.0.1 and explicitly exclude v1.0.0, which is known to break config caching. Exercise the full flow in a disposable environment before using it in a real deployment.
- Which Laravel and PHP versions does shipu/web-installer support?
- The supported Laravel and PHP ranges are not stated in the release data provided. You must confirm them in the package composer.json and test against your target Laravel and PHP versions before adoption. Do not assume compatibility with current Laravel releases without that check.
- Does shipu/web-installer work with config:cache in production?
- Version 1.0.1 fixes config:cache failures caused by closures in the published configuration, which made v1.0.0 unsafe for pipelines that run php artisan config:cache. Since config caching is a common production default, verify config:cache, route:cache, and optimize as part of acceptance testing. The initial defect suggests deployment-time behavior may not be well covered by CI.
- How do I disable or lock the web installer after installation?
- The package is expected to provide guardrails such as a post-install lock, route middleware, and environment checks, but the release notes do not evidence them. Verify the actual lock mechanism and document disabling the installer as a mandatory post-install step. Also consider blocking the installer routes at the web server or removing the package after setup.
- Is it safe to leave the Laravel web installer accessible in production?
- No. A web-reachable installer that writes .env and creates an administrator is effectively an unauthenticated privileged endpoint until it is disabled. Restrict access with network controls, an environment allowlist, signed URLs, or middleware if supported, and remove or block it immediately after installation. Treat the installer as a first-boot tool, not a permanent route.
- Can Shipu Web Installer configure the database and create the first admin user?
- Yes. The package is designed to collect database connection details, write the .env configuration, run migrations, and create the initial admin account through the browser. Test this flow against a throwaway database first so you can confirm permissions, credentials, and admin provisioning behave as expected.
- What happens if the Laravel web installer fails midway through installation?
- The recovery path for a partial .env write or a half-migrated database is not documented in the provided information. Before using it, test failure scenarios in a disposable environment and back up any existing .env and database state. Plan a manual recovery procedure rather than assuming the installer is transactional.
- Can I use Shipu Web Installer in Docker or on a read-only filesystem?
- The package writes .env directly, so a read-only filesystem or immutable container will need a writable volume or an alternative configuration injection method. Containerized deployments that rebuild caches on boot should use v1.0.1 or later and verify config:cache, route:cache, and optimize steps. Confirm the package's file-writing behavior against your runtime before relying on it.
- Is shipu/web-installer actively maintained and well tested?
- The project is at v1.0.x with a single maintainer, one external contributor, and a thin test matrix implied by its release history. The v1.0.1 patch repaired deployment-time config caching, which is a sign to test carefully around your own pipeline. Plan for vendoring or forking if long-term maintenance becomes a concern.