Deploy an application to a remote Linux machine and restart a service using systemctl or other commands
A webpack plugin wrapper for the deploy-restart module
A set of utility and general-purpose React hooks.
Utilities for creating robust overlay components
Sometimes you want to reload your app bundle during app runtime. This package will allow you to do it.
Terminal and Web console for Kubernetes
React context helpers.
Custom files/globs to restart Vite server
Production Quality Meteor Deployments
Restart the app for new architecture
Compiles your TS app and restarts when files are modified.
Deployment system for PM2
LaunchDarkly SDK for JavaScript - common code
LaunchDarkly SDK for JavaScript - common code
A supervisor program for running nodejs programs
LaunchDarkly Server SDK for JavaScript - common code
Cloudflare builder for next apps
Fast, disk space efficient package manager
JavaScript library to run Salesforce metadata deploys and retrieves
Run a process in the background and attach to it
Restarts your app when files are modified
Pick a package fetcher by type
Deploy AWS Lambda functions from command line using a json or yaml config file.
deploy and retrieve commands for sf
a Foreman wrapper with extra utilities.
A deployment framework for rails apps
manage forever process through capistrano
A set of Capistrano3 tasks to controll a deployed Rpush installation. The tasks include: restart, start, status, and stop.
Ruby gem specify for git hooks.
== DESCRIPTION: seesaw: [verb] to change rapidly from one state or condition to another and back again. Seesaw is a replacement/addition to the mongrel_cluster gem and allows you to perform a safe rippling restart of your mongrel cluster without dropping any requests. Let's say you have a mongrel cluster setup with 7 individual mongrels on your server. Let's also say that you have to deploy a code update and restart all of your mongrels but your site is really busy and you cannot afford any downtime whatsoever. When you execute: mongrel_rails seesaw::bounce This will happen: 1. your webserver configuration is switched to only use the front half of your mongrel pack (mongrels 1-4) 2. the webserver (apache or nginx) is gracefully restarted 3. the back half of your mongrel pack (mongrels 5-7) is restarted 4. your webserver configuration is switched to only use the back half of the pack 5. the webserver is gracefully restarted 6. front half mongrels are restared 7. webserver configuration switched back to full cluster configuration 8. webserver restarted one last time
No description provided.
No description provided.