When you later want to clone the repository from the git server on the Drobo, you have to tell your client git software where the server-side software is because, again, the PATH information on the Drobo host isn’t set up. Repeat the last part of step 2 (copying the public SSH keys) for every new contributor you want to add to your git repositories.Ĭloning a Repository from the Drobo Git Server That’s it! Repeat Steps 3 & 4 for every new repository you want to add to your Drobo git server. Finally, you can push your local repository to your Drobo server Git config /mnt/DroboFS/Shares/DroboApps/git/bin/git-receive-packĬhange the string archive in each command to the name of the remote if you used a different name. Git config /mnt/DroboFS/Shares/DroboApps/git/bin/git-upload-pack Now we need to tell git on the client computer where it can find the needed software on the Drobo: Finally, I called the remote archive in this example. Also, drobo.ip.address need to be replaced with the IP address of your Drobo on your local network. Git remote add archive course, change path/to/my-repository.git to the path to the git repository folder you created on the Drobo in Step 3. So we need to tell git on the client computer where the git software can be found on the server (the Drobo).Ĭd into your repository directory on your client computer, and set up a remote: The reason is the Drobo doesn’t set up the PATH environment variable for the install apps (i.e., git) such that the git software can be found for non-interactive shell session, which is what git uses to communicate with the server. Now this is the not-so-straightforward step. Step 4 - Connect Local Repository to Drobo Server Once made, cd into it and init a bare git repository: You can find the shares at:Ĭd into one of the shares and make a directory with its name ending in. Now you need to make a repository folder on one of your shares. Log onto the Drobo as git user: ssh If you did Step 2 correctly, you shouldn’t need to enter a password. ssh/authorized_keys and log out of the drobo as both git and admin. The public key is usually in ~/.ssh/id_rsa.pub on unix-like systems. ssh/authorized_keys file for editing, and insert the public ssh key from your client computer (where you git repositories are). Sudo adduser -h /mnt/DroboFS/home/git git For example: ssh logged in, you need to create a git user and then set the user up so that you can use password less login: Log onto the Drobo via ssh using your admin credentials. Install the DropBear and Git SCM Drobo apps onto the Drobo using the Drobo dashboard. This may work on other NAS models, but I cannot personally verify that. This wasn’t so straight forward, but I got it working and decided to document it here in case others are interested. I wanted to use my drobo as a git server that I could push my repositories to mostly for back up reasons, but also to enable light collaboration with users also on my LAN.
0 Comments
Leave a Reply. |