These recipes set up an AWS OpsWorks instance to run delayed_job workers for a Rails application.
By default, 4 delayed_job workers will be configured. To customize this, you may override the delayed_job.pool_size attribute in your stack's custom JSON:
{
"delayed_job": { "pool_size": 6 }
}
Specify an alternate delayed_job script location by overriding the delayed_job.path_to_script attribute in your stack's custom JSON. The default, bin was added in Rails 4. For pre-Rails 4 projects, set it to script:
{
"delayed_job": { "pool_size": 3, "path_to_script": "script" }
}
By default, workers will read from all queues. You can also specify custom queues parameters by adding attributes corresponding to each instance name and worker process. You can set a specific value for --sleep-delay seconds with a sleep_delay parameter. A special default pool can be specified to supply configuration for instances that don't otherwise appear in the JSON:
{
"delayed_job": {
"YOUR_APP_NAME": {
"pools": {
"worker1": {
"0": { "queues": "highpriority,images" },
"1": { "queues": "emails" },
"2": { "queues": "bidding", "sleep_delay": 1 }
},
"default": {
"0": { "queues": "emails" },
"1": { "queues": "emails" },
"2": { "queues": "emails" }
}
}
}
}
}
Create a custom layer for the delayed_job instances. Add the AWS-OpsWorks-Rails-App-Server security group to the layer, so that the instances have the usual cache and database access. Then, assign this cookbook's custom chef recipes to OpsWorks events as follows:
- Setup:
opsworks_delayed_job::setup - Configure:
opsworks_delayed_job::configure - Deploy:
opsworks_delayed_job::deploy - Undeploy:
opsworks_delayed_job::undeploy - Shutdown:
opsworks_delayed_job::stop
- Attributes should be better structured (allowing customization without requiring all worker processes to be listed).
© 2013-2015 Joey Aghion, Artsy. MIT License.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent