When :verify_commit is set to true, after updating the mirror
`git verify-commit <revision>` will be run on the revision that is
about to be deployed to check if it has a valid signature. This
will allow a user to be certain that the code they are about to
deploy was signed by an authorized author, and that they are not
in danger of deploying malicious code in an attack scenario such as
https://github.blog/2012-03-04-public-key-security-vulnerability-and-mitigation/
* (#2044) (#1957) Update git.rake - configurable max concurrent connections
Default git_max_concurrent_connections is set to 10 hosts per group.
Default git_wait_interval is set to 3 seconds.
This enables deployments for large number of servers with default Gitlab or similar git server configuration with default SSH settings (max 10 concurrent connections).
* ADD: rspec tests for default values
* UPDATE: docs/documentation/getting-started/configuration/index.markdown
Capistrano gems shouldn't be loaded within a Rails (or any) app. They
are intended to be used by the cap command, not within Rails itself. At
best, `require: true` (the default) is unnecessary; at worst, it can
cause conflicts as encountered here:
https://stackoverflow.com/q/48493332/4625365
Update our docs to recommend `require: false` just to be safe.
* Configurable releases and shared directory name
* configurable releases and shared directory names changelog
* rspecs for custom folder configuration
* corrected changelog with pull request details
* reverting formatting changes that break build
* adding extra spaces to rspec
* extra new line removed, formatting errors from rspec
* Extend documentation with :shared_directory, :releases_directory, and :current_directory
* Do not warn about unrecognized *_directory vars
* Fixed wrong `ask` usage examples.
* Removed redundant `set` from `ask` examples.
Also added some explanation about `ask` not prompting the user
immediately.
