There are 4 posts filed in Rails (this is page 1 of 1).
When pushing changes to your website you want to test them in an environment similar to your production one – without the fear of breaking something for your customers: voilà, staging.
Staging should mirror production in most aspects, but some things just have to be different e.g. crash-reporting, limiting access Continue reading
There exists some confusing information on how to implement password protection for your staging environment. I found the following config suitable: Use your production env for staging and configure the required password with an env-variable.
Add to your config/deploy/production.rb:
if ENV['STAGING_PASSWORD']
config.middleware.insert_after(::Rack::Runtime, "::Rack::Auth::Basic", "Staging") do |u, p|
[u, p] == ['staging', ENV['STAGING_PASSWORD']]
end
end
If you already have a nodejs dependency, I recommend the following solution for headless testing instead of my first one. Continue reading
After some struggle I found a working solution for integration testing with enabled javascript on my headless ubuntu setup.