tobischulz / artisan-forge-deploy Goto Github PK

Add a --force option to force new deployment without to confirm the deploy on CLI.

Add tests

Maybe it becomes handy to manage all sites and deployment trigger urls through artisan commands.

Add new site url to .env file (maybe with a dialog when options are empty)

php artisan forge:add --site=production --url=https://..

Site names will be used to generate new keys as in Issue #2 .

So the --site=my-site will generate this key in the .env file:

FORGE_DEPLOY_MY_SITE_URL=https://..

List all configured sites in .env

php artisan forge:sites

Collects all the keys in the .env file with FORGE_DEPLOY_ and shows the site names out of the key.

To make this command more flexible the command should have options to deploy on one of multiple environments (staging or production).

php artisan forge:deploy --site=staging
php artisan forge:deploy --site=production

If the command will called without any of this option, a dialog should ask for staging or production if both are configured in .env file.

The .env file should have a new configuration like:

FORGE_DEPLOY_STAGING_URL=https://...
FORGE_DEPLOY_PRODUCTION_URL=https://...

The --site option should be optional. If its empty the default env key will be used.

FORGE_DEPLOY_URL=https://...

As laravel have his own http client since laravel 7.x this package should use this instead the guzzle client itself.

https://laravel.com/docs/7.x/http-client