What is the best way to set up the staging process on a Ruby on Rails project?

Question

Ruby on Rails

We now have two servers. One for production (production), the other for stage (stage).
The stage server is as close as possible to production. We are now posting various features on it so that we can test it later, including for our clients. But sometimes different features break each other and it's not always clear what exactly broke.
What is the best way to organize the process so that different features can be separated?

Answer 1

Use a special service for raising teatro.io stages
1. you will have one stage for the master branch
2. an independent stage will be automatically created for each branch, you can then give a link to it to both testers and managers.

Answer 2

Increase the number of staging. Running, for example, autotests, manually testing the QA manual and also showing "features" to the client on the same staging is not good.
If you develop the idea, then you can use to separate staging into trunk / stable. For example, during the sprint, product features are deployed to trunk staging, QA manual is checked there, stable build is formed at the end of the sprint, QA automation is checked.
In addition, it is good practice to have build servers with CI for running unit tests and deploying to staging.
By the way, this practice is not strictly tied to RoR.

Answer 3

Get more servers. We have, for example, 5 test sites (test-1, test-2, ...), staging and production.