I am planning an upgrade from Bitbucket v4.13 to Bitbucket 6.5, and in the documentation I have read that I need to migrate any settings from my existing server.xml file to a new properties file.
However, in looking at my existing installation of Bitbucket, I cannot find the server.xml file.
In my home directory, there is no shared directory.
There is a /conf directory, but I do not see a server.xml file there either.
I am on Ubuntu 14.04. Is there an alternate type of configuration that could result in not having a server.xml file?
After more digging, I found there are two main folders on my server for Bitbucket, one in /opt and one in /var. I didn't realize the one in var existed because it was still named "stash" as we started using Bitbucket long before it was named so.
Sorry for the trouble, I have solved my own issue everyone.
Bitbucket Server 4.0 - 4.14: <Bitbucket home directory>/shared/server.xml
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As I said above, I could not find a shared directory, so this isn't helpful.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What is the mapping of your home directory? Also have you performed a search?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I had been looking in: /opt/atlassian/bitbucket/... but instead found the files in:
/var/atlassian/application-data/stash/...
I am working on an installation that I did not install myself, and I am also unfamiliar with installing Bit Bucket server, so I wasn't sure what the home directory would be, nor where to begin looking for it.
Also, I believe we initially installed back in the day when Bit Bucket was Stash, which possibly means I'm working on a different directory structure.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.