Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I got my Rails processes (using thin) to wait until beanstalkd is running. The recipe I used is:
The way I start beanstalkd is:
If the start is slow (I added a sleep in front of it), the pid file doesn't exist and I was have problems with Complex throwing errors. I now catch the errors and assume the test is "false" in that case. It probably should chnage it so that nothing is thrown but this got me working.
If I start beanstalkd the recommended way of not setting the pid file I get some sort of hang due to locking issues. That may be a Ruby bug. I am using Ruby 1.9.1 p378. I'll do some more experimenting and see if I can strengthen it up a bit.
Is God dead? The google groups looks like a ghost town. Is there a new kid on the block? With the current level of documentation (basically the single front page), doing anything unusual (like using Complex) requires a lot of work. And the code is not well documented so it makes it hard. It kinda seems like someone's freshman project. I'm surprised so many people suggested I use it.