How to deploy Rails to a Staging Environment

[@darkpill]

I’m giving this one a thumbs up already. 👍🏻

[@pk-all-day]

Helpful. Thank you!

[@justicerie]

Super helpful video once again, thanks Chris.

[@rjmccollam2626]

Very very excited about this. Hoping for some Hatchbox specific examples.

[@GorailsTV]

Covered Heroku but the same applies anywhere. ❤️

[@ameft]

I always had a staging app on heroku which is identical as the production app (also as environment), when your approach of creating a specific staging environment in rails better?

[@GorailsTV]

You can use it to modify how the app works (like with email interceptors, different credentials, etc) if it's marked as staging instead of production.

[@johnquarto]

I have a question which really struck me as not-optimal: around 9:15 or so you describe setting up a remote for heroku-staging since a remote of heroku is already set for production. It seems to me, if you're going to do the entire effort of setting up a staging environment, that you should redefine the heroku remote to point at your staging environment. The reason being that if you're going to use a heroku pipeline then why would you ever want to push directly to production from the CLI? All you can do is hurt yourself. You always would want to push to staging. and then in the Heroku pipeline dashboard promote from staging to production. Given that not all your projects will need pipelines, there's a real chance you will mistakenly type 'git push heroku main' and then goof up your production server. Just remove that chance altogether (or if you must, give production its own 'heroku-production' remote name as a just-in-case).

[@GorailsTV]

Yep, if you are using pipelines you can do that.