famoser / agnes
Creates & deploys releases safely to various environments.
Installs: 4 182
Dependents: 2
Suggesters: 0
Security: 0
Stars: 0
Watchers: 1
Forks: 0
Open Issues: 0
pkg:composer/famoser/agnes
Requires
- ext-json: *
- ext-zip: *
- guzzlehttp/guzzle: ^7.2
- symfony/console: ^5.0 || ^6.0 || ^7.0 || ^8.0
- symfony/dotenv: ^5.0 || ^6.0 || ^7.0 || ^8.0
- symfony/yaml: ^5.0 || ^6.0 || ^7.0 || ^8.0
Requires (Dev)
- phpstan/phpstan: ^1.12
- rector/rector: ^1.2
- squizlabs/php_codesniffer: ^4.0
- dev-main
- v4.3.7
- v4.3.6
- v4.3.5
- v4.3.4
- v4.3.3
- v4.3.2
- v4.3.1
- v4.3.0
- v4.2.4
- v4.2.3
- v4.2.2
- v4.2.1
- v4.2.0
- v4.0.1
- v4.0.0
- v3.0.0
- v2.0.5
- v2.0.4
- v2.0.3
- v2.0.2
- v2.0.1
- v2.0.0
- v1.0.1
- v1.0
- v0.18
- v0.17
- v0.16
- v0.15
- v0.14
- v0.13
- v0.12
- v0.11
- v0.10
- v0.9
- v0.8
- v0.7.1
- v0.7
- v0.6
- v0.5.1
- v0.5
- v0.4
- v0.3
- v0.2
- v0.1
- dev-update-deps
- dev-next
This package is auto-updated.
Last update: 2026-02-09 11:42:02 UTC
README
Release and deploy safely.
Install with
composer require famoser/agnes --dev
Then run commands
php vendor/bin/agnes release v1.0 main`
commands
| Command | Example |
|---|---|
build |
build maint builds the release from the main branch |
release |
release v1.0 main creates the release v1.0 from the main branch |
deploy |
deploy *:*:dev v1.0 installs on all instances matching *:*:dev the release v1.0 |
rollback |
rollback *:*:dev rolls back instances matching *:*:dev to the previous release |
clear |
clear *:*:dev clears surplus & invalid installations on the *:*:dev instances |
copy |
copy example:example.com:dev production copies the shared data to the instance example:example.com:dev its production stage |
run |
run *:*:dev my_script runs the script called my_script on the *:*:dev instances |
for details on the commands use the --help argument.
to easily remember the order of the arguments, observe that the target is always first.
config
By default, the file called agnes.yml in your project root is taken as configuration (use --config-file to change).
Further, you may supply a config folder which contains:
- additional
.ymlfiles which will all be merged with the main config file (handy to separate policies and server config) - other files which are needed for the installation but not part of the repository (like
.env.localfiles)
In the config files, you can use placeholders like %env(KEY) which are replaced by environment variables upon loading the config.
You can define environment variables in a .env or .env.local file in your project root.
Full example config in sample.yml.
advanced config
if you have an SSH connection configured you can speed up command execution greatly by caching the connection in ~/.ssh/config:
Host *
ControlPath /tmp/ssh-%r@%h:%p
ControlMaster auto
ControlPersist yes