We (http://blitz.io) are on the bamboo-mri-1.9.2 stack and have worker processes that do various things, like emails and what not. We use our own CouchDB cluster and would like to store persistent information for each worker (like the last update_seq for the _changes feed). Is there an ENV that identifies the worker 'id' like worker-1, worker-2, etc?
The goal is to have each worker store some persistent state in CouchDB that identifies itself so that when they get cycled daily, the workers resume from where they left off. Thanks, K. --- http://blitz.io http://twitter.com/pcapr http://blog.mudynamics.com -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
