Forum Discussion

SydneyL's avatar
SydneyL
Mentor
3 months ago

Tips on keeping stage and prod in alignment?

Hello developer friends!

I am newer to GitHub, so please forgive me if I use the wrong terms here. :)

I was wondering if anyone had any tips or tricks on how to "roll back" stage changes to bring staging back in line with prod on a regular basis? I've searched for how to do this more broadly, but what I've found doesn't seem to align well with a situation like Khoros, where there are a few developer admins with GitHub access, but everyone else is making changes directly on the site UI.

Essentially, I want to be able to "undo" any unnecessary changes on Stage from people testing or experimenting before say, a Khoros update, so that we can test the new version with the site mirroring Prod as closely as possible.

Any advice is welcome - and thanks in advance! :)

2 Replies

  • Publish the first set of workspaces to Staging. Create a project with everything (including connections). Import that project into the production environment and reconfigure the connections in the production environment. Now you can go back to the staging environment are remove the connections from the project.

  • SydneyL's avatar
    SydneyL
    Mentor
    2 months ago

    Thanks Thint1984 - I'm not sure this really addresses what I was trying to achieve, though.

    What I've wound up doing is keeping a branch of my own separate from Prod and Stage. When I want to sync or revert changes on either side, I push whichever one is "correct" at the time to my branch, make sure to note any affected files, and then push over to the other side, keeping an eye out for any conflicts and resolving them based on whichever environment is the current "source of truth."

    I've also been quite strict with who has designer access in general, minimizing the need to rein in any changes on Stage in the first place.