Download the PHP package survos/installer without Composer
On this page you can find all versions of the php package survos/installer. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download survos/installer
More information about survos/installer
Files in survos/installer
Package installer
Short Description Composer plugin for installing configuration files and updating .env and .gitignore, based on survos/installer
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package installer
survos/installer
By survos
A Composer plugin that applies a bundle's recipe to the host project on install/update, and reverses it on removal — a lightweight, in-bundle stand-in for symfony/recipes-contrib.
Forked from endroid/installer, which
only copies files. This fork adds the rest of what a Flex recipe does: merging
.env and .gitignore, printing post-install notes, and undoing all of it when
the package is removed.
Why this exists
Recipes-contrib is the "real" mechanism, but it lives in a separate repo and
must be kept in lockstep with every bundle release. During active development
that round-trip is painful. This plugin lets a bundle carry its own recipe
(recipe/ at the package root), so the recipe ships and versions with the code.
The recipe format is identical to a Symfony Flex recipe (recipe/manifest.json).
That is deliberate: when a bundle stabilizes, publishing to
survos/recipes is just copying the recipe/
directory into the recipes repo — no format conversion. The plugin is the
stopgap; recipes-contrib is the destination.
What it does
On composer require / composer update of a package that contains a recipe/:
env— adds variables to the project.envinside a scoped block###> vendor/package ###…###< vendor/package ###(comments preserved).gitignore— adds patterns to.gitignorein the same scoped-block style.copy-from-recipe— copies recipe files into the project, never overwriting files the user already has.post-install-output— prints the next-steps block to the console.
On composer remove, each of the above is reversed: scoped blocks are
stripped from .env/.gitignore and recipe-copied files are removed (only if
unchanged), leaving user edits intact.
Recipe layout
recipe/manifest.json
Standard Flex manifest format:
The resulting .env block:
Installation
For local development against a path checkout:
Disabling for specific packages
Status
Under active development — see PLAN.md. The recipe-format decision
(Flex manifest.json) and testing strategy are settled there; the code is
mid-migration from an older multi-directory convention.
Versioning
MAJOR.MINOR.PATCH. Lock your dependencies for production and test on upgrade.
License
MIT. See the LICENSE file.
All versions of installer with dependencies
composer-plugin-api Version ^2.0
symfony/finder Version ^7.4|^8.0
symfony/yaml Version ^7.4|^8.0