I have a sandbox environment for Stash. I am wondering what the easiest way to refresh it from our production environment is?
In JIRA I can just do an XML dump and import it into the Sandbox instance. Nice an easy, just have to update application links, license, etc.
The stash version is 3.3.
To be honest, I find this documentation a bit confusing. The way I read it, please correct me if I am wrong, is that the sections that pertains to me is section 2 "Migrating Stash Data to a different machine". The database for the Sandbox is an external MySQL db, which is the same for production just on a different MySQL server. So I think I have to do the following. * Do a mysqldump of the *production* database. * Backup the *production* HOME directory(tar and zip). This is "/var/atlassian/application-data/stash" in my case. * Shut down stash on the *sandbox* server. * Do a mysqldump on the database for the *sandbox*. Just in case. * Backup the *sandbox* stash HOME directory(tar and zip). Just in case. * Restore the *production* mysqldump file to the *sandbox* database. * Move/rename the *sandbox* HOME directory. * Extract the *production* HOME directory to the *sandbox* HOME directory. * Restart stash on *sandbox*. Seems all a bit complex :-( I think it could be made simpler if Stash provided an export/import functionality like JIRA for the database.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs