0.05
Low commit activity in last 3 years
A long-lived project that still receives updates
Deploy an application and bundled gems via rsync
2021
2022
2023
2024
2025
2026
0.04
No release in over 3 years
Low commit activity in last 3 years
There's a lot of open issues
Multiconfig extension is similar to [multistage](https://github.com/capistrano/capistrano-ext) extension. But it's not only about 'stage' configurations. It's about any configuration that you may need. Extension recursively builds configuration list from configuration root directory. Each config...
2021
2022
2023
2024
2025
2026
0.03
No commit activity in last 3 years
No release in over 3 years
https://github.com/capistrano/notification-center
2021
2022
2023
2024
2025
2026
0.02
No commit activity in last 3 years
No release in over 3 years
There's a lot of open issues
Create postgres dumps, download and replicate locally.
2021
2022
2023
2024
2025
2026
0.02
No commit activity in last 3 years
No release in over 3 years
Allows making tasks for git-based projects conditional based on the specific files to be deployed.
2021
2022
2023
2024
2025
2026
0.01
No commit activity in last 3 years
No release in over 3 years
Fast download and restore dumps using edge features of Postgres 9.x
2021
2022
2023
2024
2025
2026
0.01
No commit activity in last 3 years
No release in over 3 years
Deployment event creation on (google) calendar service
2021
2022
2023
2024
2025
2026
0.01
No release in over 3 years
Low commit activity in last 3 years
CapistranoMulticonfigParallel is a simple ruby implementation that allows you to run multiple tasks in parallel for single or multiple applications and uses websockets for inter-process communication and has a interactive menu
2021
2022
2023
2024
2025
2026
0.01
No commit activity in last 3 years
No release in over 3 years
Get all instances in an AutoScaling group by AutoScaling EC2 Tag and depoy.
2021
2022
2023
2024
2025
2026
0.01
No commit activity in last 3 years
No release in over 3 years
Confirm before deploy, Make sure you are not deploying the wrong branch, and remind you should deploy it after code review! Please use it, because I write it after deployed a wrong branch to our production server! ;(
2021
2022
2023
2024
2025
2026
0.01
No commit activity in last 3 years
No release in over 3 years
enables to watch logs on multiple deploying hosts concurrently with colored hostnames
2021
2022
2023
2024
2025
2026
0.01
No commit activity in last 3 years
No release in over 3 years
Oftenly local dev machine is much more powerfull than the remote one (VPS, for example). Every deploy system need to recompile all the assets in packs folder (by default). If the project is large, it'll take to much time and remote machine processor load that it would be much more easier to ...
2021
2022
2023
2024
2025
2026
0.01
No commit activity in last 3 years
No release in over 3 years
With every commit tag the local and remote branch with a tag
2021
2022
2023
2024
2025
2026