Komentarze do wasil.org

Skomentuj GitLab installation on Fedora 16 (with gitolite), którego autorem jest Daniel Craig Jallits

Daniel Craig Jallits — Thu, 10 May 2012 14:51:53 +0000

I may also be worth mentioning that if you are doing this in an environment that uses Plesk Panel the only directory and its contents that need chown apache:apache is the /var/www/gitlabhq directory. Otherwise, if you follow these instructions all your Plesk controlled virtual hosts will loose their Plesk assigned owner:group permissions.

Skomentuj GitLab installation on Fedora 16 (with gitolite), którego autorem jest Daniel Craig Jallits

Daniel Craig Jallits — Thu, 10 May 2012 05:28:20 +0000

Has anyone ever encountered „uninitialized constant Linguist::BlobHelper”. I am doing this on a Media Temple DV4 box which is CentOS 5.

I did a Google search and someone else is having this same problem within the last 24 hours, but they just posted their error anonymously in pastebin. You can see their post here: http://pastebin.com/SKrqnEC3

Skomentuj iptables i blokowanie stron WWW, którego autorem jest Piotrek

Piotrek — Wed, 09 May 2012 20:41:30 +0000

Oj dawno już nie zaglądałem do tego skryptu ;)
Nie mam też obecnie możliwości sprawdzenia tej teorii, ale wydaje mi się, że wystarczyłoby zamienić linijkę z poleceniem iptables w pętli for na coś w stylu:
iptables -A OUTPUT -p tcp --dport 80 -s $SIEC -d $STRONY_IP -j ACCEPT
To doda instrukcję pozwalającą wychodzić ruchowi na zewnątrz z sieci wewnętrznej do konkretnych IP odczytanych za pomocą nazwy domenowej.
a na sam koniec całego skryptu dodać instrukcję:
iptables -P OUTPUT DROP
wydaje mi się, że w teorii to powinno zadziałać. No jakoś tak plus minus :)
A no i oczywiście jakaś regułka pozwalająca wracać pakietom, żeby się nie okazało, że te co wyjdą już nie mogą wrócić i cała komunikacja pada ;)

Skomentuj iptables i blokowanie stron WWW, którego autorem jest Krystian

Krystian — Wed, 09 May 2012 16:43:38 +0000

A ja właśnie szukam takiego rozwiązania, aby blokował WSZYSTKO dla danego IP z sieci wew. i pozwalał wejść na wybrane strony z listy jak w tym skrypcie.

Da się jakoś ten skrypt tak pozmieniać?:)

Skomentuj GitLab installation on Fedora 16 (with gitolite), którego autorem jest Harish Pillay

Harish Pillay — Fri, 06 Apr 2012 14:54:10 +0000

Thanks for writing this up. I started with installing gitosis and that is working just fine.

As I am also working with openshift.redhat.com, they use ruby and I am concerned that in pulling in the version of ruby that you’ve described here for gitlab, I don’t want to have to worry about the newer version not working with openshift.

I will experiment with this anyway, and report back here (and on my blog).

Thanks for documenting this.

Harish

Skomentuj GitLab installation on Fedora 16 (with gitolite), którego autorem jest VL

VL — Tue, 20 Mar 2012 22:27:51 +0000

Would you mind having a look at this page http://66.84.10.89/

after more than 20 hours I still cant figure out what’s the problem.

I’ve tried both your solutions with giving rights to apache and „edit Gemfile and in lines containing „git:” remove everything after first comma, for example:” but it dont make any difference.

Thanks

Skomentuj GitLab quick installation script – Fedora 16, którego autorem jest Jonathon Wyza

Jonathon Wyza — Mon, 27 Feb 2012 17:11:58 +0000

One note. charlock-holmes requires libicu-devel to install during the bundle install. Adding it to the yum install fixes that problem.

Skomentuj GitLab installation on Fedora 16 (with gitolite), którego autorem jest Piotrek

Piotrek — Sat, 25 Feb 2012 21:58:14 +0000

Hi,
Check your file gitlab.yml, which is located in (according to my tutorial) in /var/www/gitabhq/config directory. There is line saying: host: localhost
In my installation it works for me, but you may have to change ‘localhost’ to your_hostname.

Directory /home/git/repositories has to be accessible by Apache user, who should be in ‘git’ system group. To make it accessible you have to set directory permissions, so they will allow that. This is what chmod does. Chown just makes sure that this directory (and subdirectories) are owned by git user and his group.

Application (GitLab) is run by Apache user, so you have to make sure that this user can log in via SSH to git user account with SSH key. To check it, please log in as Apache user or if you are root:
su – apache
and try command: ssh git@localhost or ssh git@{your_hostname}

If it succeeds and does not prompt for password, then it is working correctly and I would have to have more details to help you.

I hope you’ll get it working in no time :)

Best Regards,
Piotrek

Skomentuj GitLab installation on Fedora 16 (with gitolite), którego autorem jest Ashwin

Ashwin — Sat, 25 Feb 2012 17:14:17 +0000

Hi Piotrek,

you have made a wonderful work here. Installation went fine.

When I try to create a new project I am having this error:

Application cant get access to your gitolite system.
1. Check ‘config/gitlab.yml’ for correct settings.
2. Make sure web server user has access to gitolite. Setup tutorial
3. Try:
sudo chmod -R 770 /home/git/repositories/
sudo chown -R git:git /home/git/repositories/

I do not understand how to proceed here. Any thoughts?
I am running Fedora 15.

Skomentuj GitLab installation on Fedora 16 (with gitolite), którego autorem jest Piotrek

Piotrek — Fri, 10 Feb 2012 22:05:08 +0000

Hi. This is what worked for me: in your GitLab directory find file named Gemfile and edit it. Search for lines which have reference to package download path and duplicate them, comment out original and delete this reference from copy so it will look like all other package entries. There is one for git/grit and 2 or 3 more. You can disable them one by one to see which are problematic.

Good luck :)

Piotrek