Re: [gitorious] Re: Two bugs after Gitorious installation
On Tue, Jul 6, 2010 at 4:03 PM, Mike Jackson imikejack...@gmail.com wrote: Ruby: I could not figure out the difference between normal ruby and enterprise ruby so I defaulted to the normal ruby that ships with Ubuntu 10.04. If Enterprise Ruby is pretty much a drop in replacement then that could certainly be used. I can make some notes in the gitorious installation section noting such. There are actually quite a few Ruby versions out there these days: - Ruby 1.8.6, aka. MRI (Matz' Ruby Implementation). An older Ruby, still in use some places - Ruby 1.8.7: a partial back port of some features found in Ruby 1.9. Does not change *everything*, most Rails sites uses this these days - Ruby 1.9.1: the first official release of YARV (Yet Another Ruby VM), which introduces quite a few incompatible changes compared to 1.8.6. We used this version on gitorious.org previously, but found encoding issues (1.9 is encoding aware) and lacking Rails support to be show stoppers - Ruby 1.9.2: The 1.9 release targeted by the Rails team. - Ruby Enterprise Edition: A 1.8.7 build with some major performance enhancements which make a big difference when deploying Rails apps. This is what gitorious.org uses, but it is not in any Linux distro repositories afaik In addition to a few implementations not written in C: - JRuby: written in java, running on the JVM. A very fast Ruby, Gitorious currently doesn't run on jruby - Rubinius: Ruby written in Ruby. Inspired by Smalltalk implementations, Rubinius implements only some bare primitives in C; most of Rubinius is written in Ruby itself. I haven't tried running Gitorious under Rubinius, it may work in Rails 3 Cheers, - Marius -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
Re: [gitorious] Re: Two bugs after Gitorious installation
And there's IronRuby (*hides*). That's Ruby on top of the DLR (.Net Dynamic Language Runtime). It's supposed to run rails: http://ironruby.net/Documentation/Real_Ruby_Applications/Rails Nope, didn't test if that works. Might be interesting to try for people that are in a Windows only shop maybe? From what I've seen, IronRuby isn't doing too sharp in performance benchmarks and so on. There is also a Smalltalk implementation of Ruby around somewhere, can't remember its name. Anyway, the easiest way to handle these Rubies is to get RVM (Ruby Version Manager): http://rvm.beginrescueend.com/ It's got lots of awesome documentation, and is really simple to work with. Just use your package maintainers Ruby to host rvm, and use rvm to install and keep Rubies up to date (also includes Enterprise Edition). Regards, Christian -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
Re: [gitorious] Re: Two bugs after Gitorious installation
On Wed, Jul 7, 2010 at 2:32 PM, Christian Johansen chrisj...@gmail.comwrote: From what I've seen, IronRuby isn't doing too sharp in performance benchmarks and so on. There is also a Smalltalk implementation of Ruby around somewhere, can't remember its name. Maglev! I can't believe I forgot Maglev: http://ruby.gemstone.com/ Anyway, the easiest way to handle these Rubies is to get RVM (Ruby Version Manager): http://rvm.beginrescueend.com/ It's got lots of awesome documentation, and is really simple to work with. Just use your package maintainers Ruby to host rvm, and use rvm to install and keep Rubies up to date (also includes Enterprise Edition). Second that! Cheers, - Marius -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
Re: [gitorious] Re: Two bugs after Gitorious installation
Glad it worked out for you. You are correct about the error below. I
have corrected it in both the source and the online version. Thanks
for the heads up.
--
Mike Jackson
imikejackson gmail * com
On Jul 7, 2010, at 2:15 AM, Alberto wrote:
Hi Mike,
we did it!
Following your guide I managed to move Gitorious from
http://servername/gitorious
to http://servername, without starting from scratch but just adjusting
what was wrong.
Moving the entire environment also fixed the login page issue.
I noticed something in your guide :
/var/www/gitorious.bluequartz.net/gitorious/log/*log {
missingok
notifempty
sharedscripts
postrotate
/etc/init.d/git-daemon restart /dev/null 2/dev/null || true
/etc/init.d/git-ultrasphinx restart /dev/null 2/dev/null ||
true
/bin/touch /var/www/gitorious/tmp/restart.txt /dev/null 2/
dev/null || true
endscript
}
Shouldn't /bin/touch /var/www/gitorious/tmp/restart.txt /dev/null
2/dev/null || true be changed into /bin/touch /var/www/
gitorious.bluequartz.net/gitorious/tmp/restart.txt /dev/null 2/dev/
null || true ?
Anyway everything seems ok now!
Many thanks again,
Alberto
On Jul 6, 7:28 pm, Mike Jackson imikejack...@gmail.com wrote:
The issue with the login page is related to the fix I described. A
good suggestion to figure out if you have thins setup correctly is to
use something like VirtualBox to create a Linux Virtual Machine and
test your installs on that virtual machine. Once you can replicate a
good install a few times in a row then you can use the same setup
instructions on a real linux setup. Worked for me. I ended up
running through the installation about 8 or 10 times before I had
everything correct.
--
Mike Jackson
imikejackson gmail * com
On Jul 6, 2010, at 11:33 AM, Alberto wrote:
That's great,
I'll try to see if I can fix my issue with your suggestion, but I
suppose it would be better to start from scratch another time
(hopefully the last one).
Any ideas about the wrong displaying of the login page? Should your
advice fix this one too?
Thank you,
Alberto.
Mike Jackson wrote:
I think the issue is that Gitorious requires you to deploy it
into a
top level directory of your web server. Basically there are
directories in the gitorious project that the web server directly
accesses: public is one of those.
This is why when you setup your server if the web root is in /var/
www
and you name your server gitorious.mycompany.com then you should
have
the gitorious checked out from git into /var/www/
gitorious.mycompany.com/gitorious
In the apache configuration files you also will setup a virtual
host
gitorious.mycompany.com that points to that directory.
This is the configuration for my own gitorious.bluequartz.net:
VirtualHost *:80
ServerName gitorious.bluequartz.net
DocumentRoot /var/www/gitorious.bluequartz.net/gitorious/public
# Enable X-SendFile for gitorious repo archiving to work
XSendFile on
XSendFileAllowAbove on
# Possible values include: debug, info, notice, warn, error,
crit,
# alert, emerg.
LogLevel warn
#
# The following directives define some format nicknames for use
with
# a CustomLog directive (see below).
#
LogFormat %h %l %u %t \%r\ %s %b \%{Referer}i\ \%{User-
Agent}i\ combined
LogFormat %h %l %u %t \%r\ %s %b common
LogFormat %{Referer}i - %U referer
LogFormat %{User-agent}i agent
CustomLog /var/log/apache2/gitorious_access.log combined
TransferLog /var/log/apache2/gitorious_access.log
ErrorLog /var/log/apache2/gitorious_error.log
/VirtualHost
Note the ServerName and the Document Root. Does that help?
--
Mike Jackson
imikejackson gmail * com
On Jul 6, 2010, at 10:18 AM, Alberto wrote:
Wow, that's really accurate.
I wish I have found this before, but google-ing for a Gitorious
install guide doesn't take to it.
I'm going to give it a look, probably it's better if I start form
sketch another time following your guides (Ubuntu and Gitorious)
Any thoughts about my two issues anyway?
Many many thanks,
Best regards,
Alberto
On Jul 6, 2:42 pm, Mike Jackson imikejack...@gmail.com wrote:
Take a look
athttp://www.bluequartz.net/projects/ElectronicImaging/SCMService/html/
...
This covers how I setup my ubuntu server and how I then deployed
gitorious to it. There is specific information on how I setup
apache
and where everything is installed into.
--
Mike Jackson
imikejackson gmail * com
On Jul 6, 2010, at 6:55 AM, Alberto wrote:
Whoa!
I am really sorry but that's too technical to me, can you
explain it
with simpler words please?
Anyway I should have access to the DNS so if you know something
easier
to do on it, please tell me.
Thanks a lot,
Alberto.
On Jul 6, 11:56 am, Benjamin Podszun
benjamin.pods...@gmail.com
wrote:
Hi there.
On Tue, Jul 6, 2010 at 10:15 AM, Marius Mårnes Mathiesen
marius.mathie...@gmail.com wrote:
On Tue, Jul 6, 2010 at 8:44 AM, Alberto
Re: [gitorious] Re: Two bugs after Gitorious installation
Thanks for the list. This is all definitely a learning experience. I may take a look at Ruby Enterprise. Any type of speed up I can get for my server would be most welcome. (Old PPC G4 1.25 GHZ Single Processor). Hopefully an upgrade to x86_64 hardware will be coming later this year. When it comes to server CPU Arch what areas do you find to be the most beneficial to running a gitorious server: Pure CPU Speed. More Cores HyperThreading vs real cores (Intel Core i5-750 versus Core i5-650) Larger L2 Cache size Obviously Lots of RAM and a Fast Storage system are required. Thanks -- Mike Jackson imikejackson gmail * com On Jul 7, 2010, at 8:09 AM, Marius Mårnes Mathiesen wrote: On Tue, Jul 6, 2010 at 4:03 PM, Mike Jackson imikejack...@gmail.com wrote: Ruby: I could not figure out the difference between normal ruby and enterprise ruby so I defaulted to the normal ruby that ships with Ubuntu 10.04. If Enterprise Ruby is pretty much a drop in replacement then that could certainly be used. I can make some notes in the gitorious installation section noting such. There are actually quite a few Ruby versions out there these days: - Ruby 1.8.6, aka. MRI (Matz' Ruby Implementation). An older Ruby, still in use some places - Ruby 1.8.7: a partial back port of some features found in Ruby 1.9. Does not change *everything*, most Rails sites uses this these days - Ruby 1.9.1: the first official release of YARV (Yet Another Ruby VM), which introduces quite a few incompatible changes compared to 1.8.6. We used this version on gitorious.org previously, but found encoding issues (1.9 is encoding aware) and lacking Rails support to be show stoppers - Ruby 1.9.2: The 1.9 release targeted by the Rails team. - Ruby Enterprise Edition: A 1.8.7 build with some major performance enhancements which make a big difference when deploying Rails apps. This is what gitorious.org uses, but it is not in any Linux distro repositories afaik In addition to a few implementations not written in C: - JRuby: written in java, running on the JVM. A very fast Ruby, Gitorious currently doesn't run on jruby - Rubinius: Ruby written in Ruby. Inspired by Smalltalk implementations, Rubinius implements only some bare primitives in C; most of Rubinius is written in Ruby itself. I haven't tried running Gitorious under Rubinius, it may work in Rails 3 Cheers, - Marius -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
Re: [gitorious] Re: Two bugs after Gitorious installation
I had this issue and it was resolved by making sure all the
permissions were set correctly on all the gitorious files/directories,
the repository folder and making sure the correct user was used when
launching the polling scripts.
Even on my slow server creating a new repository takes about 10
seconds total. One key item was adding the wwwdata user to the git
group which allows the web server to write to the git repository
location. (this is specified in my guide). Also setting the /etc/
init.d/ scripts to the proper userid was also key.
--
Mike Jackson www.bluequartz.net
On Jul 7, 2010, at 10:08 AM, Alberto wrote:
Happy to help :-)
I've got one more question :
Is there a way to log-in into Gitorious using the corporate LDAP
system ?
I gave a look at OpenID-LDAP but it doesn't seem the right solution to
me.
It also would be great if LDAP will create the same groups inside
Gitorious.
Another issue I've noticed is that when you create a new repository,
its page continue to loop on the This repository is being created,
it will be ready pretty soon… message.
To solve this issue I usually restart the poller script located into
gitorious/script folder.
Am I right or is there something wrong with the installation?
About this issue, I get some strange log entries into the
production.log file.
Thank you,
Alberto
On Jul 7, 3:53 pm, Mike Jackson imikejack...@gmail.com wrote:
Glad it worked out for you. You are correct about the error below. I
have corrected it in both the source and the online version. Thanks
for the heads up.
--
Mike Jackson
imikejackson gmail * com
On Jul 7, 2010, at 2:15 AM, Alberto wrote:
Hi Mike,
we did it!
Following your guide I managed to move Gitorious fromhttp://servername/gitorious
tohttp://servername, without starting from scratch but just
adjusting
what was wrong.
Moving the entire environment also fixed the login page issue.
I noticed something in your guide :
/var/www/gitorious.bluequartz.net/gitorious/log/*log {
missingok
notifempty
sharedscripts
postrotate
/etc/init.d/git-daemon restart /dev/null 2/dev/null ||
true
/etc/init.d/git-ultrasphinx restart /dev/null 2/dev/null
||
true
/bin/touch /var/www/gitorious/tmp/restart.txt /dev/null 2/
dev/null || true
endscript
}
Shouldn't /bin/touch /var/www/gitorious/tmp/restart.txt /dev/null
2/dev/null || true be changed into /bin/touch /var/www/
gitorious.bluequartz.net/gitorious/tmp/restart.txt /dev/null 2/
dev/
null || true ?
Anyway everything seems ok now!
Many thanks again,
Alberto
On Jul 6, 7:28 pm, Mike Jackson imikejack...@gmail.com wrote:
The issue with the login page is related to the fix I described. A
good suggestion to figure out if you have thins setup correctly
is to
use something like VirtualBox to create a Linux Virtual Machine and
test your installs on that virtual machine. Once you can
replicate a
good install a few times in a row then you can use the same setup
instructions on a real linux setup. Worked for me. I ended up
running through the installation about 8 or 10 times before I had
everything correct.
--
Mike Jackson
imikejackson gmail * com
On Jul 6, 2010, at 11:33 AM, Alberto wrote:
That's great,
I'll try to see if I can fix my issue with your suggestion, but I
suppose it would be better to start from scratch another time
(hopefully the last one).
Any ideas about the wrong displaying of the login page? Should
your
advice fix this one too?
Thank you,
Alberto.
Mike Jackson wrote:
I think the issue is that Gitorious requires you to deploy it
into a
top level directory of your web server. Basically there are
directories in the gitorious project that the web server directly
accesses: public is one of those.
This is why when you setup your server if the web root is in /
var/
www
and you name your server gitorious.mycompany.com then you should
have
the gitorious checked out from git into /var/www/
gitorious.mycompany.com/gitorious
In the apache configuration files you also will setup a virtual
host
gitorious.mycompany.com that points to that directory.
This is the configuration for my own gitorious.bluequartz.net:
VirtualHost *:80
ServerName gitorious.bluequartz.net
DocumentRoot /var/www/gitorious.bluequartz.net/gitorious/public
# Enable X-SendFile for gitorious repo archiving to work
XSendFile on
XSendFileAllowAbove on
# Possible values include: debug, info, notice, warn, error,
crit,
# alert, emerg.
LogLevel warn
#
# The following directives define some format nicknames for use
with
# a CustomLog directive (see below).
#
LogFormat %h %l %u %t \%r\ %s %b \%{Referer}i\ \%{User-
Agent}i\ combined
LogFormat %h %l %u %t \%r\ %s %b common
LogFormat %{Referer}i - %U referer
LogFormat %{User-agent}i agent
CustomLog /var/log/apache2/gitorious_access.log combined
TransferLog /var/log/apache2/gitorious_access.log
ErrorLog
Re: [gitorious] Re: Two bugs after Gitorious installation
Take a look at http://www.bluequartz.net/projects/ElectronicImaging/SCMService/html/index.html This covers how I setup my ubuntu server and how I then deployed gitorious to it. There is specific information on how I setup apache and where everything is installed into. -- Mike Jackson imikejackson gmail * com On Jul 6, 2010, at 6:55 AM, Alberto wrote: Whoa! I am really sorry but that's too technical to me, can you explain it with simpler words please? Anyway I should have access to the DNS so if you know something easier to do on it, please tell me. Thanks a lot, Alberto. On Jul 6, 11:56 am, Benjamin Podszun benjamin.pods...@gmail.com wrote: Hi there. On Tue, Jul 6, 2010 at 10:15 AM, Marius Mårnes Mathiesen marius.mathie...@gmail.com wrote: On Tue, Jul 6, 2010 at 8:44 AM, Alberto alberto.pil...@gmail.com wrote: After two weeks of unlucky attempts to get the system working, now everything seems running except the two following problems : - The login (https://servername/gitorious/login) page shows only text, without images or other graphics. If I remeber correctly this page should show a simple big orange-colored login / register interface. I'm still able to login and browse the rest of the environment though. Alberto, Deploying Gitorious on a sub directory currently does not work with regard to the location of stylesheet resources; these reference image files from / - which would not work in your case. One thing that would resolve this is to use relative URLs in the CSS files. In stead of: background-image: url(/foo/bar.gif) you would use background-image: url(../foo/bar.gif) that is, reference the images relative to the directory containing the CSS files themselves. I suppose what most people do is deploy Gitorious on a virtual host, which would not require these modifications. I stumbled upon this limitation as well. If you cannot use this solution right away (for example if you don't control DNS or cannot change each and every client's HOSTS file): That was exactly the situation I was in. A workaround (I only did that for a very limited deployment): - Edit the /etc/hosts file on the server, add 127.0.0.1 someinvalid.vhost.here - Deploy gitorious in a vhost with that name on the server - Enable mod_proxy - Create a definition like this for your default (/) site in apache Location /git ProxyPasshttp://theLocalOnlyVhostName ProxyPassReversehttp://yourRealHostName/git /Location Hope that helps. But removing that limitation from gitorious itself would be great, obviously. Regards, Ben -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
Re: [gitorious] Re: Two bugs after Gitorious installation
On Tue, Jul 6, 2010 at 2:42 PM, Mike Jackson imikejack...@gmail.com wrote: Take a look at http://www.bluequartz.net/projects/ElectronicImaging/SCMService/html/index.html Mike, What a great guide, nice work! - Marius -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
Re: [gitorious] Re: Two bugs after Gitorious installation
On Jul 6, 2010, at 8:52 AM, Marius Mårnes Mathiesen wrote: On Tue, Jul 6, 2010 at 2:42 PM, Mike Jackson imikejack...@gmail.com wrote: Take a look at http://www.bluequartz.net/projects/ElectronicImaging/SCMService/html/index.html Mike, What a great guide, nice work! - Marius -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com Thanks. There will be some minor adjustments as I find issues to fix. If the gitorious team would like to include this guide they are more than welcome. I just ask for proper attribution. The original was written using Doxygen and then converted to HTML using Doxygen and LaTex/PDF using Doxygen and LaTex. -- Mike Jackson imikejackson gmail * com -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
Re: [gitorious] Re: Two bugs after Gitorious installation
Hi. Thanks. There will be some minor adjustments as I find issues to fix. If the gitorious team would like to include this guide they are more than welcome. I just ask for proper attribution. The original was written using Doxygen and then converted to HTML using Doxygen and LaTex/PDF using Doxygen and LaTex. Looks really great and useful. My feedback: Something that bugs me with both this and any other guide I've seen so far though is the selection of packages (which probably just gets copied and pasted from document to document). What are these packages for? - git-svn - git-cvs - sqlite* - tcl* - postfix The guide doesn't use phpmyadmin (Thanks for that, btw!), so why install it? Bottom line: Please let's strip these list of packages down to the required minimum and remove the cruft. Gitorious devs would probably know best about this, but the packages listed above should be a start. Another thing: After having to deal with ruby1.9 for a while (ugh.. An experience that seriously hurt the language's perception here, since it was my first exposure to it) I went to enterprise ruby following some recommendations I got on the way and it runs a) far more stable b) using quite a lot less memory I'd go therefor go for enterprise ruby in the guide as well (and install it before you install the gems accordingly). Nice work, Ben -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
Re: [gitorious] Re: Two bugs after Gitorious installation
That's great,
I'll try to see if I can fix my issue with your suggestion, but I
suppose it would be better to start from scratch another time
(hopefully the last one).
Any ideas about the wrong displaying of the login page? Should your
advice fix this one too?
Thank you,
Alberto.
Mike Jackson wrote:
I think the issue is that Gitorious requires you to deploy it into a
top level directory of your web server. Basically there are
directories in the gitorious project that the web server directly
accesses: public is one of those.
This is why when you setup your server if the web root is in /var/www
and you name your server gitorious.mycompany.com then you should have
the gitorious checked out from git into /var/www/
gitorious.mycompany.com/gitorious
In the apache configuration files you also will setup a virtual host
gitorious.mycompany.com that points to that directory.
This is the configuration for my own gitorious.bluequartz.net:
VirtualHost *:80
ServerName gitorious.bluequartz.net
DocumentRoot /var/www/gitorious.bluequartz.net/gitorious/public
# Enable X-SendFile for gitorious repo archiving to work
XSendFile on
XSendFileAllowAbove on
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn
#
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
#
LogFormat %h %l %u %t \%r\ %s %b \%{Referer}i\ \%{User-
Agent}i\ combined
LogFormat %h %l %u %t \%r\ %s %b common
LogFormat %{Referer}i - %U referer
LogFormat %{User-agent}i agent
CustomLog /var/log/apache2/gitorious_access.log combined
TransferLog /var/log/apache2/gitorious_access.log
ErrorLog /var/log/apache2/gitorious_error.log
/VirtualHost
Note the ServerName and the Document Root. Does that help?
--
Mike Jackson
imikejackson gmail * com
On Jul 6, 2010, at 10:18 AM, Alberto wrote:
Wow, that's really accurate.
I wish I have found this before, but google-ing for a Gitorious
install guide doesn't take to it.
I'm going to give it a look, probably it's better if I start form
sketch another time following your guides (Ubuntu and Gitorious)
Any thoughts about my two issues anyway?
Many many thanks,
Best regards,
Alberto
On Jul 6, 2:42 pm, Mike Jackson imikejack...@gmail.com wrote:
Take a look
athttp://www.bluequartz.net/projects/ElectronicImaging/SCMService/html/
...
This covers how I setup my ubuntu server and how I then deployed
gitorious to it. There is specific information on how I setup apache
and where everything is installed into.
--
Mike Jackson
imikejackson gmail * com
On Jul 6, 2010, at 6:55 AM, Alberto wrote:
Whoa!
I am really sorry but that's too technical to me, can you explain it
with simpler words please?
Anyway I should have access to the DNS so if you know something
easier
to do on it, please tell me.
Thanks a lot,
Alberto.
On Jul 6, 11:56 am, Benjamin Podszun benjamin.pods...@gmail.com
wrote:
Hi there.
On Tue, Jul 6, 2010 at 10:15 AM, Marius Mårnes Mathiesen
marius.mathie...@gmail.com wrote:
On Tue, Jul 6, 2010 at 8:44 AM, Alberto alberto.pil...@gmail.com
wrote:
After two weeks of unlucky attempts to get the system working,
now
everything seems running except the two following problems :
- The login (https://servername/gitorious/login) page shows only
text,
without images or other graphics. If I remeber correctly this
page
should show a simple big orange-colored login / register
interface.
I'm still able to login and browse the rest of the environment
though.
Alberto,
Deploying Gitorious on a sub directory currently does not work
with regard
to the location of stylesheet resources; these reference image
files from /
- which would not work in your case. One thing that would resolve
this is to
use relative URLs in the CSS files. In stead of:
background-image: url(/foo/bar.gif)
you would use
background-image: url(../foo/bar.gif)
that is, reference the images relative to the directory containing
the CSS
files themselves.
I suppose what most people do is deploy Gitorious on a virtual
host, which
would not require these modifications.
I stumbled upon this limitation as well. If you cannot use this
solution right away (for example if you don't control DNS or cannot
change each and every client's HOSTS file): That was exactly the
situation I was in.
A workaround (I only did that for a very limited deployment):
- Edit the /etc/hosts file on the server, add 127.0.0.1
someinvalid.vhost.here
- Deploy gitorious in a vhost with that name on the server
- Enable mod_proxy
- Create a definition like this for your default (/) site in
apache
Location /git
ProxyPasshttp://theLocalOnlyVhostName
ProxyPassReversehttp://yourRealHostName/git
/Location
Hope that
Re: [gitorious] Re: Two bugs after Gitorious installation
The issue with the login page is related to the fix I described. A
good suggestion to figure out if you have thins setup correctly is to
use something like VirtualBox to create a Linux Virtual Machine and
test your installs on that virtual machine. Once you can replicate a
good install a few times in a row then you can use the same setup
instructions on a real linux setup. Worked for me. I ended up
running through the installation about 8 or 10 times before I had
everything correct.
--
Mike Jackson
imikejackson gmail * com
On Jul 6, 2010, at 11:33 AM, Alberto wrote:
That's great,
I'll try to see if I can fix my issue with your suggestion, but I
suppose it would be better to start from scratch another time
(hopefully the last one).
Any ideas about the wrong displaying of the login page? Should your
advice fix this one too?
Thank you,
Alberto.
Mike Jackson wrote:
I think the issue is that Gitorious requires you to deploy it into a
top level directory of your web server. Basically there are
directories in the gitorious project that the web server directly
accesses: public is one of those.
This is why when you setup your server if the web root is in /var/www
and you name your server gitorious.mycompany.com then you should have
the gitorious checked out from git into /var/www/
gitorious.mycompany.com/gitorious
In the apache configuration files you also will setup a virtual host
gitorious.mycompany.com that points to that directory.
This is the configuration for my own gitorious.bluequartz.net:
VirtualHost *:80
ServerName gitorious.bluequartz.net
DocumentRoot /var/www/gitorious.bluequartz.net/gitorious/public
# Enable X-SendFile for gitorious repo archiving to work
XSendFile on
XSendFileAllowAbove on
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn
#
# The following directives define some format nicknames for use
with
# a CustomLog directive (see below).
#
LogFormat %h %l %u %t \%r\ %s %b \%{Referer}i\ \%{User-
Agent}i\ combined
LogFormat %h %l %u %t \%r\ %s %b common
LogFormat %{Referer}i - %U referer
LogFormat %{User-agent}i agent
CustomLog /var/log/apache2/gitorious_access.log combined
TransferLog /var/log/apache2/gitorious_access.log
ErrorLog /var/log/apache2/gitorious_error.log
/VirtualHost
Note the ServerName and the Document Root. Does that help?
--
Mike Jackson
imikejackson gmail * com
On Jul 6, 2010, at 10:18 AM, Alberto wrote:
Wow, that's really accurate.
I wish I have found this before, but google-ing for a Gitorious
install guide doesn't take to it.
I'm going to give it a look, probably it's better if I start form
sketch another time following your guides (Ubuntu and Gitorious)
Any thoughts about my two issues anyway?
Many many thanks,
Best regards,
Alberto
On Jul 6, 2:42 pm, Mike Jackson imikejack...@gmail.com wrote:
Take a look
athttp://www.bluequartz.net/projects/ElectronicImaging/SCMService/html/
...
This covers how I setup my ubuntu server and how I then deployed
gitorious to it. There is specific information on how I setup
apache
and where everything is installed into.
--
Mike Jackson
imikejackson gmail * com
On Jul 6, 2010, at 6:55 AM, Alberto wrote:
Whoa!
I am really sorry but that's too technical to me, can you
explain it
with simpler words please?
Anyway I should have access to the DNS so if you know something
easier
to do on it, please tell me.
Thanks a lot,
Alberto.
On Jul 6, 11:56 am, Benjamin Podszun benjamin.pods...@gmail.com
wrote:
Hi there.
On Tue, Jul 6, 2010 at 10:15 AM, Marius Mårnes Mathiesen
marius.mathie...@gmail.com wrote:
On Tue, Jul 6, 2010 at 8:44 AM, Alberto
alberto.pil...@gmail.com
wrote:
After two weeks of unlucky attempts to get the system working,
now
everything seems running except the two following problems :
- The login (https://servername/gitorious/login) page shows
only
text,
without images or other graphics. If I remeber correctly this
page
should show a simple big orange-colored login / register
interface.
I'm still able to login and browse the rest of the environment
though.
Alberto,
Deploying Gitorious on a sub directory currently does not work
with regard
to the location of stylesheet resources; these reference image
files from /
- which would not work in your case. One thing that would
resolve
this is to
use relative URLs in the CSS files. In stead of:
background-image: url(/foo/bar.gif)
you would use
background-image: url(../foo/bar.gif)
that is, reference the images relative to the directory
containing
the CSS
files themselves.
I suppose what most people do is deploy Gitorious on a virtual
host, which
would not require these modifications.
I stumbled upon this limitation as well. If you cannot use this
solution right away (for example if you don't control DNS or
cannot
change each and every client's HOSTS file): That was exactly the
situation I was in.
A
