To quote the capybara README you linked: "Capybara's Rspec matchers, however, are smart enough to handle either form." That means that should have_no_content and should_not have_content are functionally equivalent.
But thanks for pointing that out, I didn't even know there was a difference.
Most rails applications have more dependencies, like a sphinx server for example. How would you go about launching these (e.g. in case of a server restart)?
Can something like Foreman be used for this task?
I guess it makes sense to take precautions if the webservice you are using is down.
Is it possible to automatically re-queue the job if it fails because it cannot reach the webservice?
To quote the capybara README you linked: "Capybara's Rspec matchers, however, are smart enough to handle either form." That means that
should have_no_content
andshould_not have_content
are functionally equivalent.But thanks for pointing that out, I didn't even know there was a difference.
Most rails applications have more dependencies, like a sphinx server for example. How would you go about launching these (e.g. in case of a server restart)?
Can something like Foreman be used for this task?
The capistrano recipe symlinks it to
/etc/nginx/sites-enabled/
I guess it makes sense to take precautions if the webservice you are using is down.
Is it possible to automatically re-queue the job if it fails because it cannot reach the webservice?