Weave Code
Installer Laravel Package
survos/installer
A Composer-based installer for Survos packages that streamlines adding components to PHP applications, automating setup and configuration steps so teams can bootstrap features faster with less manual wiring and fewer repetitive install tasks.
survos/installer is a lightweight Composer helper for streamlining the post-install setup of Survos and Symfony packages. It provides reusable installer logic so bundle authors can prompt for configuration values, write environment variables, and run the usual scaffolding steps without duplicating boilerplate across projects.
- Interactive prompts for collecting configuration during
composer install - Automatic
.env/.env.localupdates with sensible defaults - Reusable installer traits for Symfony bundle authors
- Composer scripts and events integration for repeatable setup
Designed to keep package installation predictable and idempotent, it reduces manual README steps and makes first-run configuration consistent across development and CI environments.
Frequently asked questions about Installer
- What is survos/installer and what problem does it solve?
- survos/installer is a Composer plugin that installs configuration files for Survos packages. It is a setup helper for PHP projects, aimed at reducing manual wiring and boilerplate so you can get from composer require to a working configuration faster. The available overview does not list every Survos package it supports.
- How do I install survos/installer with Composer?
- Install it with Composer, for example composer require survos/installer. Because it is a Composer plugin, Composer 2.2 and newer may ask you to allow the plugin before it can run. After installation, the plugin handles installing the relevant Survos package configuration files.
- Does survos/installer work with Laravel?
- It is a Composer plugin for PHP projects, not a Laravel-only package, but it can be used in Laravel applications that depend on Survos packages. Laravel-specific behavior is not described in the provided overview, so check the package source or docs for any framework integration details.
- Which configuration files does survos/installer install?
- It installs package configuration files for Survos packages, but the available context does not enumerate the exact filenames or paths. Run it in a test project or review the plugin source to see precisely which files it writes before applying it to an existing application.
- Do I need to register a service provider after using survos/installer?
- The installer focuses on configuration-file installation; service provider registration is typically defined by the individual Survos packages. Check each package's documentation for provider registration or auto-discovery behavior rather than assuming the installer handles it.
- Should survos/installer be a dev dependency or a production dependency?
- If you only need it during initial project setup, requiring it with composer require --dev survos/installer keeps it out of production dependencies. If your deployment process runs the installer to generate config, keep it in require instead. The provided overview does not mandate either approach.
- Is it safe to run survos/installer in production?
- Treat it like any setup tool that writes files: run it in a fresh or version-controlled project and review the generated config before deploying. Many teams generate config locally and commit it rather than executing the installer during production releases. The overview does not describe production-specific safeguards.
- Which PHP and Laravel versions does survos/installer support?
- The available context does not specify PHP or Laravel version constraints. Check the require section of the package's composer.json on Packagist before adding it to a project, especially if you are on an older Laravel version.
- How do I test that survos/installer configured my project correctly?
- Install it in a disposable test project or branch, run the setup, and inspect the generated configuration files with git diff. Then boot your application and confirm the relevant Survos packages load with those defaults. This catches unexpected file writes before they reach a shared codebase.
- What are alternatives to survos/installer?
- Alternatives include manually publishing or copying vendor configuration files, using Laravel's vendor:publish for Laravel packages, or following package-specific install commands. survos/installer is specifically aimed at automating that wiring for Survos packages. Check its Packagist page and source repository for release history and issue tracking.
Weaver
How can I help you explore Laravel packages today?