- How do I install rikudou/installer in a Laravel project?
- Install it with Composer, for example composer require rikudou/installer, and remember that as a Composer plugin it must be allowlisted in your project's config.allow-plugins setting since Composer 2.2. The repository is archived, so treat the install as an experiment in a branch rather than a production dependency. Verify the plugin's Composer and PHP requirements from its composer.json before running it.
- Does rikudou/installer support Laravel 11 or PHP 8.3?
- There is no published compatibility matrix, and the repository is archived, so there is no confirmed support for Laravel 11, Laravel 12, PHP 8.3, or PHP 8.4. The package is framework-agnostic rather than Laravel-aware, so it does not track Laravel's package:discover or vendor:publish conventions. Check the last commit's composer.json constraints and test on your target PHP version before relying on it.
- What problem does rikudou/installer solve compared with php artisan vendor:publish?
- It lets a package ship an install recipe that Composer applies during install or update, writing config files, service registrations, or scaffolding into the consuming project. That is conceptually similar to Symfony Flex recipes and fills a gap Laravel leaves after package auto-discovery, which covers providers and aliases but not config publishing, .env keys, migration ordering, or asset scaffolding. In practice you may end up running it alongside vendor:publish rather than replacing it.
- Why does Composer ask me to allow rikudou/installer as a plugin?
- Composer 2.2 and later require Composer plugins to be explicitly allowlisted via config.allow-plugins because plugins execute with your user's privileges during dependency resolution. If you do not allowlist it, Composer may warn and continue, but the installer's recipes will silently never run. Add the allowlist entry deliberately and review what the plugin can write before enabling it in CI.
- Is rikudou/installer safe to use in production or CI pipelines?
- Its only real strength is that it runs at install time and adds no production runtime footprint or request-path latency. The risk is that recipes are an unconstrained file-mutation channel, and the documentation does not describe sandboxing, a dry-run mode, or a diff-review contract. In CI or deploy pipelines, gate it behind an internal review or use a fork with a pinned, audited recipe set. Silent no-op behavior when allow-plugins is missing is another operational hazard.
- Are rikudou/installer recipes declarative config or executable PHP code?
- The available description does not specify the recipe format, and that single answer changes the risk tier from manageable to code review per package. If recipes are declarative YAML or JSON diffs, the review surface is smaller; if they are executable PHP, every recipe is arbitrary code execution at install time. Inspect the plugin source and any example recipes before adopting it.
- Is rikudou/installer idempotent, and can I uninstall or revert changes?
- Idempotency is not documented, so repeated installs may overwrite or duplicate files and create merge conflicts in a shared repository. Uninstall or revert support is also not stated, which suggests state may be one-way. Test repeated installs on a disposable branch and keep your project under version control so you can inspect and revert any file mutations.
- Is rikudou/installer still maintained?
- The repository is archived, has zero stars and zero dependents, and shows no compatibility matrix for modern PHP or Composer 2.7.x. Composer's plugin events have shifted across 2.x, so an unmaintained plugin is a latent CI break on the next Composer upgrade. Treat it as a design reference for the recipe idea rather than a dependency you plan to rely on.
- What are the best alternatives to rikudou/installer in Laravel?
- Laravel's built-in php artisan vendor:publish, package:discover, and install commands cover many config-publishing and provider-registration cases without a Composer plugin. For repeatable setup you can also use custom Composer scripts, a project-specific installer command, or a maintained recipe system such as Symfony Flex if you are working outside Laravel. If you need .env key prompting or migration ordering, write a small internal Artisan command rather than depending on an archived plugin.
- What license does rikudou/installer use, and can I fork it?
- It uses the WTFPL, which is maximally permissive and allows you to relicense an internal fork. That convenience comes with no warranty, no patent grant, and no indemnification, so legal may flag the lack of IP assurance if the recipe mechanism becomes load-bearing. If you fork it, pin your fork, document the recipe format, and add the dry-run and idempotency guarantees the original lacks.