The thing is we are a small team but from different physical locations: europe, asia, america etc.
Currently we setup our only Stash server in Hong Kong to compromise accessibility and network speed.
But sometime the push/pull performance is not so idea (only 10-50k/s while we have over 1Gb data to push).
I've checked out Stash Data Center solution but it seems not quite suitable for a tiny team like us.
So I'm wondering if it's possible to setup a simple distributed stash repositories to let our developer push/pull code from local server while the local servers will synchronise repository data with a single master server in Hong Kong.
(Stash management website access don't need to be distributed as it's not performance critical, so does the database which only need to store permissions / meta data if I'm right)
This is something we'd like to help solve at some point. In the meantime, you can refer to this answer which has some suggestions: https://answers.atlassian.com/questions/319336/is-it-possible-to-setup-a-read-only-mirror-for-stash
In short, you can use a mirroring add-on to keep a remote copy up to date. Those users can set their fetch URL to the local mirror, and the push URL to point back to the central Stash server.
Thanks a lot. This plugin seems very interesting: https://marketplace.atlassian.com/plugins/com.englishtown.stash-hook-mirror I'll investigate if it is suitable for my situation as we probably need bi-directional synchronisation instead of a readonly copy.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are you really _pushing_ lots of data? If so I'd love to hear more about what you're using git for. It seems very strange to be pushing 1Gb (which your question hinted at), as no one writes that much code in one go ;)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you're not pushing lots of data, you can have separate fetch and push URLs (fast local fetch for big clones, slow remote push for small pushes), which is what I'd recommend.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Roger, what are the Stash licensing considerations if you deploy a second stash instance acting only as a mirror? Can that count as a "development" instance or does it require its own license?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry I missed your question earlier. Currently you'd need a full license as it's considered a production instance also, but you could add fewer users to it.
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.