
Security News
Follow-up and Clarification on Recent Malicious Ruby Gems Campaign
A clarification on our recent research investigating 60 malicious Ruby gems.
== Mongrel Cluster Plugin
Tool to help start/stop/restart multiple mongrel servers to use behind a load balancer like Apache 2.2 (mod_proxy_balancer), Lighttpd, Pound, Pen or Balance. This plugin adds an option to specify a number of Mongrel servers to launch, a range of ports, and a configuration file for the cluster. Use "-h" to see command syntax.
Configure cluster and write configuration file: mongrel_rails cluster::configure
Start cluster: mongrel_rails cluster::start
Restart cluster: mongrel_rails cluster::restart
Stop cluster: mongrel_rails cluster::stop
== Capistrano Recipes
Add to config/deploy.rb: require 'mongrel_cluster/recipes'
Variables: mongrel_servers: Number of Mongrel servers to start. mongrel_port: Starting port to bind to. mongrel_address: Address to bind to. mongrel_environment: Rails environment to run as. mongrel_conf: Path to conf file. Defaults to /etc/mongrel_cluster/app_name.conf mongrel_user: User to run mongrels in cluster as. Unset by default mongrel_group: Group to run mongrels in cluster as. Unset by default.
On Capistrano 2 you get then get the following tasks:
mongrel:cluster:configure Configure the cluster with variables. mongrel:cluster:start: Start Mongrel processes on the app server. mongrel:cluster:stop: Stop the Mongrel processes on the app server. mongrel:cluster:restart: Restart the Mongrel processes on the app server by starting and stopping mongrel_cluster. deploy:restart: Calls mongrel:cluster:restart to allow Mongrel to be used with the standard Capistrano deploy task. deploy:start: Calls mongrel:cluster:start to allow Mongrel to be used with the standard Capistrano deploy task. deploy:stop: Calls mongrel:cluster:stop to allow Mongrel to be used with the standard Capistrano deploy task.
On Capistrano 1 you get the same tasks, but without the namespace:
configure_mongrel_cluster: Configure the cluster with variables. start_mongrel_cluster: Start Mongrel processes on the app server. stop_mongrel_cluster: Stop the Mongrel processes on the app server. restart_mongrel_cluster: Restart the Mongrel processes on the app server by starting and stopping mongrel_cluster. restart: Calls restart_mongrel_cluster to allow Mongrel to be used with the standard Capistrano deploy task. spinner: Calls start_mongrel_cluster to allow Mongrel to be used with the standard Capistrano cold_deploy task.
== Starting clusters at boot
FAQs
Unknown package
We found that mongrel_cluster demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
A clarification on our recent research investigating 60 malicious Ruby gems.
Security News
ESLint now supports parallel linting with a new --concurrency flag, delivering major speed gains and closing a 10-year-old feature request.
Research
/Security News
A malicious Go module posing as an SSH brute forcer exfiltrates stolen credentials to a Telegram bot controlled by a Russian-speaking threat actor.