Not only mod passenger, gitlabhq codebase is uses ruby 1.9. features, so we'll need to package ruby 1.9 also. Also we need to test it against existing gitolite rpm<br><br><div class="gmail_quote">On Tue, Mar 20, 2012 at 8:09 PM, Stas Sușcov <span dir="ltr"><<a href="mailto:stas@nerd.ro">stas@nerd.ro</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">În data de Tue, 20 Mar 2012 16:32:15 +0200, Kevin Fenzi <<a href="mailto:kevin@scrye.com" target="_blank">kevin@scrye.com</a>> a scris:<div class="im">
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Mon, 19 Mar 2012 23:42:59 +0200<br>
Stas Sușcov <<a href="mailto:stas@nerd.ro" target="_blank">stas@nerd.ro</a>> wrote:<br>
<br>
</blockquote>
<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If all this stuff sounds interesting, I would be happy to present a<br>
draft on how we could solve FedoraHosted transition to Gitlab, and<br>
ensure its well maintained from now on.<br>
<br>
Lately I started to hang on<br>
#fedora-summer-coding|#<u></u>jbosstesting@freenode, but I'm not sure whom I<br>
should query. I can't see Dan either online.<br>
<br>
I also have a Github account: <a href="https://github.com/stas" target="_blank">https://github.com/stas</a><br>
and a resume: <a href="http://stas.github.com/resume.html" target="_blank">http://stas.github.com/resume.<u></u>html</a><br>
<br>
Thanks in advance for reading this, and I'm looking forward for your<br>
reply.<br>
</blockquote>
<br></div>
Well, the big hurdles with this project were mentioned in the previous<br>
thread. To my mind the first big problem is getting mod_passenger<br>
packaged, and thats something that you may not have much control over.<br>
(It will be done when it's done).<br>
<br>
Next would be making sure that there's a group of people who know how<br>
to manage/maintain/operate things so that after the summer is over<br>
there's not a abandonded proof of concept no one can use. ;)<br>
<br>
</blockquote>
<br>
Thanks a lot for openness! :)<br>
<br>
Not sure passenger is the problem.<br>
Gitlab uses the awesome Resque[1], so you will need something like foreman[2] to run the app with it's workers all together (at least this is the easiest way to do that).<br>
I would go with a different stack like unicorn[4] as the webserver and use apache (if you really want to keep it, other-way I would consider nginx) as a reverse proxy.<br>
<br>
[1]: <a href="https://github.com/gitlabhq/gitlabhq/blob/master/Gemfile#L29" target="_blank">https://github.com/gitlabhq/<u></u>gitlabhq/blob/master/Gemfile#<u></u>L29</a><br>
[2]: <a href="http://devcenter.heroku.com/articles/procfile#developing_locally_with_foreman" target="_blank">http://devcenter.heroku.com/<u></u>articles/procfile#developing_<u></u>locally_with_foreman</a><br>
[3]: <a href="https://github.com/gitlabhq/gitlabhq/blob/master/Procfile.production" target="_blank">https://github.com/gitlabhq/<u></u>gitlabhq/blob/master/Procfile.<u></u>production</a><br>
[4]: <a href="https://github.com/blog/517-unicorn" target="_blank">https://github.com/blog/517-<u></u>unicorn</a><div class="HOEnZb"><div class="h5"><br>
______________________________<u></u>_________________<br>
infrastructure mailing list<br>
<a href="mailto:infrastructure@lists.fedoraproject.org" target="_blank">infrastructure@lists.<u></u>fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/infrastructure" target="_blank">https://admin.fedoraproject.<u></u>org/mailman/listinfo/<u></u>infrastructure</a></div></div></blockquote></div><br>