Tag Info

Hot answers tagged

20

Clone the gitosis git repository again and then install it again using the --record option: sudo python setup.py install --record uninstall.txt Which will produce a text file containing all the installed files. Then just delete them. sudo cat uninstall.txt | xargs rm -rf You may want to remove the git user: userdel -f git as well as the git group: ...


16

Once you've pulled the repository you should be able to go: git checkout 3ef0d...


14

Yes. But it shouldn't be much of a slowdown unless you have names instead of IPs in there, have the PARANOID option set, or ident turned on (by asking for username info). And it will only slow down the initial connection, not affect anything once the connection is established and passing data. You could try time tcpdmatch sshd 1.2.3.4 and time tcpdmatch ...


13

Gitosis by itself does not have a remove function because of the way it is managed through git commits. If you remove the repository from the gitosis.conf and commit the change then the repository is no longer accessible. You can re-enable it later or you can eventually log into the server and remove the file from the gitosis repositories/ directory. I ...


7

You can actually see the efficiency on GitHub as to how fast this is. You are not going to cause a significant bottleneck with that many keys. Though as documented in their blog from 2009, they have changed how ssh keys are retrieved, from a database. Hat Tip: @Jeremey But, you created over 8k keys, you can test again with 50k keys. Those keys don't need ...


6

The gitosis username is just a default, likely selected to not conflict if you already had a git user. The gitosis package in Debian asks what username and directory you want to use, although they might be low priority questions and not asked by default, it should be the same way in Ubuntu. You can run the command sudo dpkg-reconfigure gitosis to ...


5

But I don't understand, a server by definition shouldn't have any closed port and I can't find a way to see if they are. I think you are slightly mistaken. A server, by definition, serves. What it serves is chosen by the server administrator. Technically, a server can have all of its ports closed, although that wouldn't be a very useful server... ...


4

As requested, a bit of a tutorial on groups. Hopefully this isn't too elementary. By default, most user accounts are also part of a group of the same name. To determine what groups an account is a member of, use the groups command. # groups root root : root bin daemon sys adm disk wheel The first one listed is the primary group, and will be the default ...


4

I would definitely advice gitolite. We use gitosis in house, manage a bunch of repositories that are about 20G in size compressed and have a lot of developers accessing them 24/7. The server usage is very light, never had an issue. Gitolite only improves upon gitosis and provides much finer grain of access control. I think we would be moving in that ...


4

As you discovered, the root user can sudo to any other user, so just stick an extra sudo in front. sudo sudo -H -u git gitosis-init < /home/ec2-user/id_rsa.pub Please don't kick yourself too hard.


3

If you want to grant a user (such as git in your examples) access to another user's space, put them in the same group and set group rights accordingly. If you need more complex access control list functionality, you should look into POSIX ACLs as provided by getfacl(1) and setfacl(1).


3

I'm not sure if you made a mistake while pasting your question in but are you 100% positive you used: git clone git@SERVER:gitsos-admin.git and not git@SERVER:gitosis-admin.git... It's a subtle change but your example shows you trying to clone gitsos-admin.git and not gitosis-admin.git


3

1: As far as installing gitosis goes, you fetch its "source" to whatever directory you please. The setup.py script has default locations it will use for installing everything to. Debian's gitosis package will install the files listed here. As for your code, gitosis manages the repository in the "git" user's home directory. From there you will need to ...


3

I've been reading the following article, which is closely related: How do I tell Git for Windows where to find my private RSA key? and it gave a good hint: The HOME-Variable is crucial, but it didn't work out the way I thought. After a lot of reasearch and trying I found this article: ...


3

git push --force is really the only one that you need to worry about. The other one that could cause issues would be removing a branch, but at least with gitolite if you can't push --force then you can't delete a branch.


3

There are usually 2 ways to manage this sort of problem ; You have a bare repository centralizing your application somewhere on the server, and one clone of this repository (with a working tree) in each httpdocs folder you then set a post-receive hook on the bare repo to update all httpdocs clones of this repository, usually a shell script will suffice ...


3

The answer is the first sentence of the second link you have posted: "Gitosis stores repositories in the git user's home directory." If you have followed the tutorial from the third link you've posted, you should have created user git on your system, and Gitosis should be creating new repositories in the home directory of this user as long as you run ...


2

You have to log into the machine and remove the repository there and then you have also to remove the repository from the gitosis configuration file.


2

I had this error and solved it by giving my "git" ssh user membership in group Administrators. The hint to do this came from http://www.cygwin.com/ml/cygwin/2008-07/msg00276.html


2

Internally the git clone is going to be doing ssh git@support, and Git's "remote end hung up unexpectedly" error message usually means that ssh failed to log into the server. So run that ssh command yourself and see what error message you get -- that might enlighten you already. Or if not, add -vvv to get a bunch of debugging output. (I'm a little ...


2

When you add an SSH key to gitosis-admin.git repository it is automatically checked out during the commit and the ~/.ssh/authorized_keys file for the gitosis user is updated to call gitosis-serve for the given SSH key. What repositories the user can actually manage is of course dependent on which repositories in the gitosis.conf that they have been given ...


2

Git uses templates to set up new repositories. I don't know if Gitorious uses these same templates, but it's worth checking out. On my system they exist at /usr/local/share/git-core/templates/hooks.


2

Well, I finally figured out what my difficulty was. Gitosis doesn't care what you name the key files in the keydir. So, even though I have two keys that both have username@host1 and username@host2 I can name those files username_host1 and username_host2 in the keydir. Heck, I could call them raspberry and apple. Then I just need to use the filenames I ...


2

I'm unclear on your description of what keys and configuration files reside on what systems. However, if you are accustomed to being able to use your private key from a box to which you have not copied it, then you are doing so through use of SSH agent forwarding. Try removing 'no-agent-forwarding' from the option list that you quoted above and see if that ...


2

Why not just add their public keys to the gitosis server? Or have them use dedicated keys for gitosis that they have installed on both S1 and H1? Then there's nothing more to install.


2

If some process on your live server immediately accesses the just-pulled content (i.e. you cannot work with git checkout 3ef0d after pull), you should consider tagging the version you want to deploy in production and specifically checkout that tag on production, so that pulling does not immediately change your working directory. Otherwise you'd risk somebody ...


2

I would recommend using Gitolite instead of Gitosis since it isn't supported anymore. Here is a guide on how to setup Gitolite: How to install and setup a Git Repository Server using Gitolite on Linux Ubuntu 10.04 & 11.04 [Development Environment]


2

Any ideas what could cause this? This usually indicates either (a) a configuration error in your gitosis.conf, or (b) a missing public key in your Gitosis keydir. To further diagnose the problem: Check out the admin repository. Since you can log into the server, you can run: git checkout /path/to/gitosis/repos/gitosis-admin.git This will give you ...


2

1) Clone Gitosis admin repo: $ git clone git@SERVER:gitosis-admin.git 2) Add Dev1's and tech_geek's SSH public keys to gitosis-admin/keydir (rename each public key id_rsa.pub) as dev1.pub and tech_geek.pub. Add to file gitosis-admin/gitosis.conf [group developers] members = dev1 tech_geek [group new_project] writable = new_project members = @developers ...


2

Gitosis is obsolete, use Gitolite



Only top voted, non community-wiki answers of a minimum length are eligible