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 > >>>>>>> <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 > > > -- > > 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
