change path to repositorys?

Where can I change the path to the repositorys and so on?

I will save these data on a NAS.

2 answers

1 accepted

You need to move the whole STASH_HOME folder, you cannot move the repo data only.

N.B. Since Stash accesses this folder quite heavily, there is a potentially big performance impack of moving this to a non-local disk. Consider adding more local disk space instead of moving the home folder.

Hi Wolfgang,

Unfortunately there is no way to change the path where Stash store repositories internally and we do not intend to provide this functionality for technical reasons. You should be aware, though, that you can locate the repositories path on disk if you browse through the "Repository Settings" on Stash UI. This issue has been raised in the past and our development team has replied to it:

  • I like to have all my data (and therefore also repositories) in a standard location so that I don't have to remember location for each type of data on the server separately. FishEye was easy to set to the location of my SVN repositories. I just learned from your support that the same is not currently possible for GIT repositories in Stash. I'm sure that such possibility would be appreciated by many users and system administrators.

As opposed to FishEye which only works with external repositories in Stash we not only access the repositories but actively manage them (e.g. create the repo, change config settings, modify files). The built in assumption is that Stash owns the repositories compared to FishEye where the built in assumption is that something else owns the repositories and FishEye only access them in a read-only fashion. 
We expect a certain directory layout to be followed (as outlined on and encourage users to not move the home directory if possible. The reason for that is that there are absolute paths being used when repositories are forked and moving the repositories requires us to rewrite those paths.
For Stash Data Center we also require the repositories to be available on a network mount in addition to other directories that are in the shared sub directory.
We are therefore not considering making the path the the repositories configurable. 
As a workaround you could create a symlink to STASH_HOME/shared/data to make the repositories available.

Hope this helps.

Having STASH_HOME in a NFS is ok, but you have to make sure that this is very well tuned. Stash is I/O intensive in the way it does caching and a badly tuned NFS could cause bad performance issues and weird bahaviour.

I hope you understand.


Suggest an answer

Log in or Join to answer
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

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&nbsp...

714 views 0 4
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot