I upgraded to stash 3.8 using .tar.gz in staging and left the server.xml file under the $STASH_INST/conf directory and it came up fine. However, the upgrade and readme documentation indicate that in version 3.8 it's location must be changed to home/shared and the mysql driver should also be moved to stash home/lib. It seems to be running fine with both files in the old installation directories. Do I really need to move them from installation directories to home directories? https://confluence.atlassian.com/display/STASH/Stash+upgrade+guide
As you observed it will work if you don't have the files under the
However, as of 3.8, we changed Stash to source these files from
STASH_HOME so when customers upgrade, there is no need to manually update the new installation with previous customizations (i.e. MySQL driver or
To explain it further, our upgrade process basically consists of (this is all done by the installer and no manual intervention is required):
You see? The content of the
STASH_INSTALLATION always changes (they are always fresh from the installers we release) but the
STASH_HOME is the one that is kept with your data through the upgrade process. Hence changing the code to source those files from
STASH_HOME ensures that customers won't have to execute these steps manually after each upgrade in the future.
In case you have files in both directories, Stash will prioritize the ones on
STASH_HOME for the same reasons.
Thank you for the explaination. I have my own scripts that wget the tar.gz package, installs it, diffs our customized files in our installation directory with yours and makes the changes accordingly, with an echo to the screen to make sure it's done properly. Sounds like maybe I should try using your installer now and decommission my custom scripts.
Shouldn't the new tar.gz installation package exclude the server.xml file now that it's supposed to live under home? What about the web.xml file? Could that be moved to home as well? My scripts modfiy both of those files for our own customization as well as modify the INST start and stop .sh files and our environment settings.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot