Add support for Redmine/Gitolite splitted configuration

[Hugodby]

For some reasons I need to have gitolite and redmine on two separates instances.
After some tests I found that the plugin kept trying to connect to localhost even if I changed :ssh_server_domain value.
It appears that 'localhost' is hardcoded in lib/redmine_git_hosting/config/gitolite_base.rb and lib/redmine_git_hosting/gitolite_wrapper.rb. By changing 'localhost' with value from :ssh_server_domain everything works fine.

[n-rodriguez]

For some reasons I need to have gitolite and redmine on two separates instances.

This cannot work. See here : http://redmine-git-hosting.io/faq/#can-i-install-gitolite-and-redmine-on-different-servers-

[Hugodby]

With the pull-request I made, it works fine.
To make it work :

• Both servers must have redmine and git user with each one using the same UID, e.g. adduser --uid 10001 git.
• git home directory needs to be available from both servers. You could use NFS.

Everything else is just as in the tutorial.

About the latency, think about cloud computing. It's all about isolate and scale your app. I don't see any problem here.

[n-rodriguez]

About the latency, think about cloud computing. It's all about isolate and scale your app. I don't see any problem here.

Of course it works, but this is not a common configuration. It was a deliberate choice to not provide this feature to not add too much complexity.

[Hugodby]

I understand but that kind of setup will become more and more common.
I'm using Docker and I don't see a better solution than one service per container (one with ssh for gitolite, one with nginx-passenger for redmine).
But it's still a great plugin !

[n-rodriguez]

Thanks! I'm not against adding this feature... but I still have questions... What about Sidekiq worker?
In a such configuration (2 Dockerized Redmine instances with 1 Dockerized Gitolite with NFS share or Docker mounted volumes) where would you put Sidekiq worker if you decide to use it, knowing that it must acts as a FIFO to keep Gitolite config file consistent across Redmine instances?

[Hugodby]

I'm not familiar with Sidekick, redis... Using Docker you have to isolate every process in a different container. I found that : https://github.com/mperham/sidekiq/wiki/Deployment

Also, I'm deploying 1 redmine/ 1 gitolite, not a centralized gitolite for every redmine. It could be possible to do so but as you said it will involve a lot more complexity to keep Gitolite config file consistent.

[spiette]

This is great, exactly what I need, thanks!

[n-rodriguez]

Added in commit 10aec4c

(2 Dockerized Redmine instances with 1 Dockerized Gitolite with NFS share or Docker mounted volumes) where would you put Sidekiq worker if you decide to use it, knowing that it must acts as a FIFO to keep Gitolite config file consistent across Redmine instances?

I answer myself : with 2 more containers :

• one container with a full Redmine instance within but you only start the Sidekiq worker (not the webserver) AND with the NFS share mounted inside (like the regular Redmine instances)
• one container with a Redis Server inside.

The Redis container must accessible by all Redmine instances (Webserver + Worker).

This might need a bit of configuration (mostly container communication) but it should work.