Manual for local install

[Anish Patel]

Hello,
Sorry if this is a repost, but is there any type of manual for a
local gitorious install? I would like to be able to recover from the
console if i ever need to. Right now if i mess up something i can
rewind my VM.. but i would really like to know how to administer the
install.

Thanks!
Anish

[Kelketek Titikilik Rritaa]

The gitorius wiki and this group are the primary resources. As wonderful and open source as gitorious is, it is very much a DIY project requiring a significant amount of Linux administration skill to properly install and maintain. Gitorious offers paid installation and support if you're in an enterprise situation or have money to burn.

Having worked with an enterprise installation, I would say it's rather helpful.

Having set up a local install, I will say that there are some things I still don't have working right, and it's a point of personal frustration for me. I imagine I'll get the last bits figured out eventually. Speaking of which, I'm going to dive in once more and try to figure out why tarballs aren't working while I'm thinking about it...

--
To post to this group, send email to gito...@googlegroups.com
To unsubscribe from this group, send email to
gitorious+...@googlegroups.com

[Anish Patel]

Hi Kelketek,
    Thanks for your response.  What i am looking for is ways to fix permissions on repos/projects incase people makes mistakes.
I made one about a week ago where i removed all admin rights from a repo.  luckly no one had commited to it so i was able to delete it and re create it, but you can imagine the pickle that one would be in if that happened.

If someone could point me to what part of the Rails code one would look at so they could use the admin console it would be great too.


thanks
anish

[Kelketek Titikilik Rritaa]

I wasn't aware Gitorious had its own admin console-- unless you mean the Linux root shell? If there is such a thing, it appears I've been missing out. Please tell me where this is.

The administrative user can edit a project's settings by clicking on a project and choosing to edit it from the side bar. More complex permissions are set by selecting which teams own the project. You can create teams from the teams link at the top of gitorious. They can be given their own team administrators who can be used to delegate permissions.

Permissions will get more interesting in the private repositories. I'm not familiar with them yet since they haven't been pushed down the mainline pipe yet.

If you're talking about UNIX/Linux permissions, remember that your coders should not be editing the files directly on the server. They should be using the instructions gitorious gives them--making use of the git and ssh clone and push links. The repo file permissions will stay consistant so long as Gitorious is the one managaing them.

Now, I think the guide I read instructed us to set up two users-- one named git and one named gitorious. (It may just have been one and I misremember) In your gitorious.yml file in the config folder of the gitorious directory, there is a place where you specify where the repos wil be located. Change to that directory. Explore around there, but don't change anything. Use an ls -l to check the permissions on the files and the folders. They should be consistent throughout. You can use the find, chmod, and chown commands to deal with them. I'd give examples but I'm writing this from my phone.

[Anish Patel]

where your gitorious is installed.

RAILS_ENV=<env> scripts/console


this will put you into an admin style console (remove users for real etc)
this is also the place you can fix repo perms (i think) for when you (or someone else) locks someone out of a repo/project.


thanks
anish