Query: how to setup a dev instance with DB replication

[Jaspotn0612]

Expected Behavior (or desired behaviour if a feature request)

This isn't really a bug and I guess it's not so much a feature request so I'll put it in as a query so then it can be marked as closed/resolved when a suitable answer is given.

We have to instances of Snipe-IT locally set up, one for test and one for prod. Both are working however we're now wondering what method others have used for keeping the test version in sync on a manual basis so as we try new things in test we can copy the prod database over so any test users can do what they need in that system for trials before they use the prod system. This is mostly adding/removing assets/users to get a feel of the system or see how a potential change will look.

However we've found that doing this causes issues with the keys that are generated in the system, they are changed to the prod system which makes the data inaccessible with the test system as the keys don't match the install. There are other things such as a colour scheme to identify the test from prod but that can be changed again after the refresh, but if there's a way to do a refresh without overwriting the colour scheme it will mean any potential confusion is avoided.

Can anyone explain how they have set up a test/prod scenario with data refresh from prod to test so we can get it right.

Thanks

[Jaspotn0612]

Can anyone suggest how they've set up a dev/prod instance with database replication? Or does no-one else ever worry about keeping their two instances, if they have them, in sync, if even once a month?

[stale]

Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

[Jaspotn0612]

Yes still relevant, no replies have been provided.

[stale]

Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!

[stale]

Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

[Jaspotn0612]

yes still relevant

[stale]

Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!

[snipe]

This is really sort of outside the scope of Snipe-IT support. Replication, either by formal MySQL replication setup or by manual DB dump then import set up on a cron job, will exactly duplicate the data from the main to the replicated database.