[et_pb_section fb_built=”1″ admin_label=”Header Image and Title” _builder_version=”4.9.0″ _module_preset=”default” background_enable_image=”off” background_size=”contain”][et_pb_row _builder_version=”4.9.0″ _module_preset=”default”][et_pb_column type=”4_4″ _builder_version=”4.9.0″ _module_preset=”default”][et_pb_image src=”https:\/\/richrijnders.com\/file\/2020\/12\/git-on-drobo-with-xcode.jpg” alt=”Git on Drobo Title Image” title_text=”Git on Drobo with Xcode” align=”center” _builder_version=”4.9.0″ _module_preset=”default”][\/et_pb_image][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section fb_built=”1″ admin_label=”Introduction” _builder_version=”4.7.7″ _module_preset=”default” custom_padding=”||0px|||”][et_pb_row _builder_version=”4.7.7″ _module_preset=”default”][et_pb_column type=”4_4″ _builder_version=”4.7.7″ _module_preset=”default”][et_pb_text ol_item_indent=”5px” _builder_version=”4.7.7″ _module_preset=”default” text_orientation=”justified”]<\/p>\n
In this tutorial we will endeavor to set up our Drobo 5N (or 5N2) as a Git server. That is, the Drobo will host\u00a0Remote Git Repositories<\/em>\u00a0for our local Xcode projects that are under Git source control. With this setup, we can work on our Xcode projects on our desktop or laptop computers, make and commit changes to our\u00a0Local Git Repository<\/em> and then\u00a0push<\/em> those changes to the remote repository which resides on our Drobo. This will allow us to collaborate with other developers on our projects. They will be able to\u00a0clone<\/em> our projects from the Drobo to their own computers so that they can work on the code, check in their changes, and then push<\/em> those changes back up to the Drobo. \u00a0We can then\u00a0branch\u00a0<\/em> and\u00a0fork<\/em> our projects for even more flexibility, safety, and control over our code base.<\/p>\n This setup will actually allow you to use the Drobo as a remote repository for any<\/em> project you have under Git control (Xcode or otherwise) by using the Git command line interface (CLI) from a terminal window. \u00a0But in current releases, Xcode for Mac OS X has included support for Git \/ GitHub built right in to the IDE. Our goal is to get our Drobo hosted Git server working seamlessly from within the Xcode IDE.<\/p>\n This question was asked of me more than once while I researched issues related to getting this setup working. It is true that Xcode has pretty good support for interfacing with the GitHub web service, however; there are several reasons why you might want to setup up your own Git server on your own Drobo, instead:<\/p>\n There may be any number of reasons\u00a0why<\/em> you want to do this. Not the least of which is my own: Because some enterprising hacker created a Git port that runs on Drobo and, by golly, I should be able to get it working with Xcode!<\/em> That is all the justification any hack worth his\/her salt needs! \u00a0So let us begin.<\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section fb_built=”1″ admin_label=”The Pieces” _builder_version=”4.7.7″ _module_preset=”default” custom_margin=”2px|||||” custom_padding=”4px||12px|||”][et_pb_row column_structure=”3_5,2_5″ _builder_version=”4.7.7″ _module_preset=”default” min_height=”309px” custom_margin=”0px|auto||auto||” custom_padding=”||0px|||”][et_pb_column type=”3_5″ _builder_version=”4.7.7″ _module_preset=”default”][et_pb_text ol_position=”outside” ol_item_indent=”20px” admin_label=”Text” _builder_version=”4.7.7″ _module_preset=”default” text_orientation=”justified” width=”94.4%” custom_padding=”||0px|||”]<\/p>\n I will assume that we already have a running and configured Drobo 5N or 5N2. Likewise, I will assume that we have one or more desktop or laptop computers on the same network as our Drobo NAS with Xcode installed for development (otherwise this effort is for naught). Given these, here is what we are going to install and\/or configure in order to reach our goal:<\/p>\n [\/et_pb_text][\/et_pb_column][et_pb_column type=”2_5″ _builder_version=”4.7.7″ _module_preset=”default”][et_pb_image src=”https:\/\/richrijnders.com\/file\/2020\/12\/puzzle-pieces-shopping-cart.jpg” title_text=”puzzle-pieces-shopping-cart” admin_label=”Image: Puzzle Pieces in Shopping Cart” _builder_version=”4.7.7″ _module_preset=”default” custom_margin=”||-1px|||”][\/et_pb_image][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.7.7″ _module_preset=”default” custom_padding=”0px||4px|||”][et_pb_column type=”4_4″ _builder_version=”4.7.7″ _module_preset=”default”][et_pb_text ol_position=”outside” ol_item_indent=”20px” _builder_version=”4.7.7″ _module_preset=”default” text_orientation=”justified” min_height=”360px”]<\/p>\n And if you get all the way through with this setup, there is a bonus code snippet I created to make your Xcode + Drobo + Git administrative tasks a bit easier!<\/strong><\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section fb_built=”1″ admin_label=”Drobo Git Share and Drobo Apps” _builder_version=”4.7.7″ _module_preset=”default” min_height=”2834.3px” custom_margin=”||-2px|||” custom_padding=”||0px|||”][et_pb_row admin_label=”Drobo Apps” _builder_version=”4.7.7″ _module_preset=”default”][et_pb_column type=”4_4″ _builder_version=”4.7.7″ _module_preset=”default”][et_pb_text _builder_version=”4.7.7″ _module_preset=”default” text_orientation=”justified”]<\/p>\n The first thing we need to do is to install the Git SCM and Dopbear<\/em> apps on our Drobo. \u00a0This is a pretty straight forward process. Just open the Drobo Dashboard on your computer and connect to the Drobo you want to use as your Git server (yes, people often have more than one Drobo). \u00a0Click on the “Drobo Apps” item in the left-hand menu. Select the “Category” button to sort all the available apps, then scroll all the way down to the “System Utilities” section.<\/p>\n [\/et_pb_text][et_pb_image src=”https:\/\/richrijnders.com\/file\/2020\/12\/drobo-apps-install.png” title_text=”drobo-apps-install” show_in_lightbox=”on” admin_label=”drobo-apps-install” _builder_version=”4.7.7″ _module_preset=”default”][\/et_pb_image][et_pb_text _builder_version=”4.7.7″ _module_preset=”default” text_orientation=”justified”]<\/p>\n In the System Utilities section you will find the two apps we need: “Dropbear” and “Git SCM”. \u00a0Installing the apps is straight forward. Just double click each app and then select “Install”. \u00a0Do this for each of the two apps. \u00a0Once they are installed, the little “LED” underneath the app icons will turn green and you are good-to-go.\u00a0<\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row admin_label=”Create the GIT Share” _builder_version=”4.7.7″ _module_preset=”default”][et_pb_column type=”4_4″ _builder_version=”4.7.7″ _module_preset=”default”][et_pb_text _builder_version=”4.7.7″ _module_preset=”default” text_orientation=”justified”]<\/p>\n Now we are going to create a location on the Drobo to house all our Git repositories. In reality, you can just create a directory on any of your existing Drobo\u00a0Shares<\/em>, but I recommend creating a dedicated share just for your Git. This location or share never has to be mounted<\/em> so there is no point in putting it on an existing share where all of the Git nuts and bolts can be viewed by users of the Drobo!<\/p>\n [\/et_pb_text][et_pb_image src=”https:\/\/richrijnders.com\/file\/2020\/12\/drobo-shares.png” title_text=”drobo-shares” show_in_lightbox=”on” admin_label=”image: drobo-shares” _builder_version=”4.7.7″ _module_preset=”default”][\/et_pb_image][et_pb_text _builder_version=”4.7.7″ _module_preset=”default” text_orientation=”justified”]<\/p>\n Again, connect to your Drobo with the Drobo Dashboard. In the left-side menu, click “Shares” and then click the “Share Settings” button.\u00a0<\/p>\n [\/et_pb_text][et_pb_image src=”https:\/\/richrijnders.com\/file\/2020\/12\/drobo-shares-settings.png” title_text=”drobo-shares-settings” show_in_lightbox=”on” admin_label=”image: drobo-shares-settings” _builder_version=”4.7.7″ _module_preset=”default”][\/et_pb_image][\/et_pb_column][\/et_pb_row][et_pb_row column_structure=”1_2,1_2″ _builder_version=”4.7.7″ _module_preset=”default” custom_margin=”|auto|35px|auto||”][et_pb_column type=”1_2″ _builder_version=”4.7.7″ _module_preset=”default”][et_pb_text _builder_version=”4.7.7″ _module_preset=”default” text_orientation=”justified” custom_margin=”||-25px|||”]<\/p>\n In the Settings panel, make sure you have the “Shares” view selected. In the left pane you should see a list of all of the existing Shares on the the Drobo. Below the left pane is an “Add” button to create a new Share. Click it.\u00a0<\/p>\n In the “Add Share” popup window, specify a name for the new share. “GIT” seems sort of obvious, but you can name it as you like. \u00a0For the purpose of the rest of this tutorial I will refer to the share as “GIT”. \u00a0Don’t worry about the Time Machine options, just enter the name for the new share and press “OK”.<\/p>\n You should now see the new “GIT” share listed in the “Shares” panel with all the other Drobo Shares. There is no need to\u00a0mount<\/em> the share or authorize any Drobo Users to use it, just move on to the next section where we are going to do some command line work!<\/p>\n [\/et_pb_text][\/et_pb_column][et_pb_column type=”1_2″ _builder_version=”4.7.7″ _module_preset=”default”][et_pb_image src=”https:\/\/richrijnders.com\/file\/2020\/12\/drobo-add-new-share.png” title_text=”drobo-add-new-share” show_in_lightbox=”on” admin_label=”Image: drobo-add-new-share” _builder_version=”4.7.7″ _module_preset=”default”][\/et_pb_image][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section fb_built=”1″ admin_label=”Create Git User” _builder_version=”4.7.7″ _module_preset=”default” custom_padding=”4px|||||”][et_pb_row _builder_version=”4.7.7″ _module_preset=”default” custom_margin=”0px||0px||false|false” custom_padding=”0px||0px||false|false”][et_pb_column type=”4_4″ _builder_version=”4.7.7″ _module_preset=”default”][et_pb_text _builder_version=”4.7.7″ _module_preset=”default” text_orientation=”justified” min_height=”334px”]<\/p>\n Now we will create a user named “git” on our Drobo. \u00a0This user ID will own all of the Git Remote Repositories created on the Drobo. It will create all of the Git directories and artifacts, so it will own all of the objects and we can be sure that it always has the authority to manipulate the archives on behalf of the Git clients\/users.<\/p>\n Note that you will\u00a0NOT<\/em> be creating “git” as a “Drobo User” through the Drobo Dashboard! This user will be created in the Drobo OS as a regular OS user. The reason for this is that Drobo Users – those created through the Drobo Dashboard – are not true “user” ID’s at the OS level. \u00a0In fact, if you SSH over to your Drobo using your Drobo Admin ID and then check the contents of the \/etc\/passwd<\/em> file, you will see that the only Drobo User ID in the file is the Admin.<\/p>\n So go ahead and open up the terminal<\/em> app (command line) on your computer and\u00a0SSH over to your Drobo using your Drobo Admin ID and the IP address of your Drobo. \u00a0If you don’t know the IP address of your Drobo, you can find it in the Drobo Dashboard under “Drobo Settings” and selecting “Network”. \u00a0Write it down or memorize it since you will be using it a lot.<\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row column_structure=”1_3,2_3″ _builder_version=”4.7.7″ _module_preset=”default” min_height=”249px” custom_margin=”0px||0px||false|false” custom_padding=”0px||0px||false|false”][et_pb_column type=”1_3″ _builder_version=”4.7.7″ _module_preset=”default”][et_pb_text _builder_version=”4.7.7″ _module_preset=”default” text_orientation=”justified”]<\/p>\n After your terminal session connects with the Drobo, you will be prompted to enter the admin password for the Drobo. Note that this is the password for the Drobo admin, not for your computer, since you are logging into the Drobo OS. If you successfully log on to the Drobo, you will be presented with a command prompt. You will know that you are now on the Drobo because the command prompt will change from your computer name to the Drobo name, as shown here.<\/p>\n [\/et_pb_text][\/et_pb_column][et_pb_column type=”2_3″ _builder_version=”4.7.7″ _module_preset=”default”][et_pb_image src=”https:\/\/richrijnders.com\/file\/2020\/12\/ssh-successful.png” title_text=”ssh-successful” show_in_lightbox=”on” admin_label=”Image: ssh-successful” _builder_version=”4.7.7″ _module_preset=”default”][\/et_pb_image][et_pb_text _builder_version=”4.7.7″ _module_preset=”default” text_orientation=”justified” custom_margin=”0px||0px||false|false” custom_padding=”0px||0px||false|false”]<\/p>\n Further, entering “whoami” will show that you are currently running as your Drobo Admin User and entering “pwd” shows you are, indeed, on your Drobo file system.<\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.7.7″ _module_preset=”default” custom_margin=”0px||0px||false|false” custom_padding=”0px||0px||false|false”][et_pb_column type=”4_4″ _builder_version=”4.7.7″ _module_preset=”default”][et_pb_text _builder_version=”4.7.7″ _module_preset=”default” min_height=”386px” custom_padding=”16px|||||”]<\/p>\n So now we are going to create our “git” user ID. At the Drobo command line enter:<\/p>\n You will be prompted to enter your Drobo admin password and then you will be prompted to enter a new password for the new “git” user id. Enter the desired password (twice). If successful, you will see a message telling you “passwd: password for git changed by root”<\/em> or something to that effect. To confirm that your new “git” user was successfully created, type:<\/p>\n You may be prompted to enter your Drobo admin password again if it has been some time since the previous command. If successful, you will be returned to the command prompt. To confirm that you are now running as the new “git” user, enter:<\/p>\n If the output is “git” then you have successfully created the new “git” user ID. Type “exit” to revert to the Drobo admin user ID, then type “exit” again to log out of the Drobo and return to the command line on your own computer.<\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section fb_built=”1″ admin_label=”Add SSH Certificates” _builder_version=”4.7.7″ _module_preset=”default” custom_padding=”||3px|||”][et_pb_row admin_label=”Row” _builder_version=”4.7.7″ _module_preset=”default”][et_pb_column type=”4_4″ _builder_version=”4.7.7″ _module_preset=”default”][et_pb_text _builder_version=”4.7.7″ _module_preset=”default” text_orientation=”justified” custom_margin=”0px||0px||false|false” custom_padding=”0px||16px||false|false”]<\/p>\n In this next step, we are going to take the\u00a0public SSH key<\/em> from our computer and add it to the “.authorized_keys” file of the “git” user on the Drobo. This will allow us to issue SSH commands from our computer to the Drobo without having to enter the “git” user’s password every time. This means that other users\/computers will also be able to issue SSH\/Git commands from their<\/em> computers without you having to distribute the “git” password to everyone (so long as you have also added\u00a0thier<\/em> SSH public key to the “git” user’s .authorized_keys<\/em> file, as well). Now you can control who can access and use the Git repository on the Drobo without having to create new Drobo users or distribute the git password. Only those computers for which you have added the public SSH key to the git user’s .authorized_keys<\/em> file will be able to use the Git repository.<\/p>\n So you should now be back at the command prompt in\u00a0terminal<\/em> on your computer (after exiting the Drobo at the end of the previous section). First, let’s see if you already have an SSH\u00a0keypair<\/em> generated for your computer. \u00a0From the command line, navigate to your user’s\u00a0home<\/em> directory and then check that you are indeed there:<\/p>\n Your terminal screen should look something like this:<\/p>\n [\/et_pb_text][et_pb_image src=”https:\/\/richrijnders.com\/file\/2020\/12\/terminal-cd-home-pwd.png” title_text=”terminal-cd-home-pwd” show_in_lightbox=”on” _builder_version=”4.7.7″ _module_preset=”default” custom_padding=”||23px|||”][\/et_pb_image][et_pb_text _builder_version=”4.7.7″ _module_preset=”default” text_orientation=”justified” custom_margin=”||||false|false” custom_padding=”||||false|false”]<\/p>\n To check if you already have an SSH KeyPair created on your computer. Enter:<\/p>\n If you already have a keypair created, the output will list three files:<\/p>\n If this is the case, you can skip the next part for creating the SSH KeyPair and move on to “Copying The Public Key”.<\/p>\n If, instead, the output of the “ls” command was<\/p>\n <\/span><\/p>\n then you do not yet have an SSH KeyPair. No worries, we will generate one below.<\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.7.7″ _module_preset=”default” text_orientation=”justified” min_height=”1078px” custom_padding=”19px||25px|||”]<\/p>\n If you need to create an SSH KeyPair, first make sure you are in your user’s\u00a0home<\/em> directory:<\/p>\n You should see the home path for your user id like<\/p>\n If you are in the right place, then start the key generation process by typing<\/p>\n You will be prompted to enter a file name to save the KeyPair. Just hit ENTER to accept the default.<\/p>\n You will then be prompted to enter a passphrase for the new key. You can just hit enter for no password. If you do enter a password, keep in mind that you will occasionally have to re-enter that password when issuing Git commands or performing Git functions in your projects. You will be prompted again to confirm the passphrase (or ENTER again for no passphrase). The result should look something like this<\/p>\n You have successfully generated your SSH KeyPair. So now we will copy the public key to our clipboard and paste it in to the “git” user’s “authorized_keys”<\/em> file on the Drobo.<\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.7.7″ _module_preset=”default” text_orientation=”justified”]<\/p>\n Again, start by opening the terminal\u00a0<\/em>app on your computer and\u00a0making sure you are in your home directory by typing<\/p>\n Now we will output the contents of our public ssh key file to the screen. Type<\/p>\n The output will be a long string of gibberish that looks something like this:<\/p>\n Select the entire public key string and copy it to your clipboard (CMD+C).\u00a0Now we want to SSH over to our Drobo and log in as our “git” user<\/p>\n You will be prompted to enter the password for the “git” user on the Drobo. After you enter the password you will be in a command line session on the Drobo. You will know this because the command line prompt will have changed to the name of your Drobo instead of the name of your computer.<\/p>\n First, let’s make sure that we are running as the “git” user and are in the “git” user’s home directory using the “whoami” and “pwd” commands:<\/p>\n If your session looks like the above, we are doing something right. \u00a0So now, let’s make sure that the proper directories and files exist for our “git” user’s SSH. Enter:<\/p>\n Your output should say<\/p>\n because we haven’t created one yet. To create the required directory and set its permissions enter:<\/p>\n To create the “authorized_keys” file and set its permissions enter<\/p>\n Now that we have the required file, open the .ssh\/authorized_keys file in your favorite command line editor, paste in the public key you copied from your computer (CMD+V), and save the file. If you haven’t installed a command line text editor on your Drobo, it does come natively with\u00a0vi<\/em> installed. You can search the internet for a quick tutorial on using vi<\/em>, but in general your steps will be something like this:<\/p>\n You can enter “cat .ssh\/authorized_keys” to verify that your public key is in the file. \u00a0Now that we have done that, let’s test that it is working as expected. Type “exit” to sign out of the Drobo and get back to your computer’s command line.<\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.7.7″ _module_preset=”default” text_orientation=”justified”]<\/p>\n Back at your computer’s\u00a0terminal<\/em> command line, you should just be able to hit the UP arrow key to bring back the last command you entered and it should be the command to SSH into the Drobo using the “git” user. \u00a0If not, just re-enter the command:<\/p>\n This time, when you press enter you should be taken straight-away to the command prompt for your Drobo\u00a0without having to enter the “git” user’s password<\/em>. \u00a0If that is what happened then congratulations, your SSH keys are working as expected! \u00a0Type “exit” to log off the Drobo and get back to your computer’s\u00a0command line again.<\/p>\n Now we are going to test that we can run a command from our computer that will execute as the “git” user on the Drobo. At your computer’s command line, enter:<\/p>\n If the response you recieved was “git” then we have success! This means that you entered the “whoami” command from your computer, it was executed on the Drobo as the “git” user and it returned that fact to your computer’s command line all the way from the Drobo! \u00a0And you doubted me…<\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section fb_built=”1″ admin_label=”Creating Symbolic Links to the Git Server Executables” _builder_version=”4.7.7″ _module_preset=”default” custom_padding=”4px||0px|||”][et_pb_row admin_label=”Row” _builder_version=”4.7.7″ _module_preset=”default” custom_padding=”||0px|||”][et_pb_column type=”4_4″ _builder_version=”4.7.7″ _module_preset=”default”][et_pb_text _builder_version=”4.7.7″ _module_preset=”default” text_orientation=”justified”]<\/p>\n Now that we have a “git” user ID on the Drobo and a way to execute commands as “git” remotely via SSH, we obviously want “git” to execute Git commands, right? \u00a0On the Drobo, the Git SCM app installs the Git Executable files in<\/p>\n But by default, our “git” user ID does not have this location in its PATH environment variable and so it cannot execute any of the commands from there because it will not find them. While logged in via SSH as the “git” user ID we can see our current PATH variable and using the\u00a0type<\/em> commend we see that our shell has no idea where to find the Git executable files:<\/p>\n As the section title says, we are going to add a symlink<\/em> for each of the Git executables into the “\/bin” directory because “\/bin” is in the default PATH and that will enable the “git” user shell to locate them. But first, I think some additional explanation is required here because some “obvious” solutions will not work and some work-arounds offered on the Internet will only partially solve the problem.<\/p>\n <\/p>\n OK, so maybe that’s a bit hyperbolic. Of course you can modify the PATH environment variable and it will work. You can do this temporarily in your current shell with the export<\/em> command or permanently by modifying the\u00a0\/etc\/profile<\/em>\u00a0 file with the additional path to the Git executables. What I should have said is that it is\u00a0insufficient<\/em> for our needs to modify the PATH variable. Allow me to illustrate.<\/p>\n Here I have already modified the PATH variable to include the path to the Git executables. If I now use the\u00a0type\u00a0<\/em>command, I can see that the shell does in fact locate the desired command:<\/p>\n So now I can execute any of the desired Git commands from the command line while SSH’d into my Drobo as the “git” user. But there is still a problem. \u00a0Look what happens if I try to execute the command from\u00a0my computer’s\u00a0<\/em> command line:<\/p>\n What gives? I modified the PATH variable permanently for the “git” user. Each time I log in via SSH to a command line shell as “git” on my Drobo, I can see the correct path added to the PATH variable and I can execute Git commands willy-nilly. So why does this change not affect the SSH’d commands from my computer to the Drobo? As it turns out (and by that I mean I discovered after hours of researching on the Internet) that\u00a0Dropbear<\/em> (you remember, that Drobo App we use as an SSH server on the Drobo) does not allow modification of the PATH variable for non-interactive shells<\/strong><\/em>. That is why no matter what you do to the PATH variable of the “git” user’s shell, issuing “echo \\$PATH” via SSH still shows only “\/usr\/bin:\/bin”.<\/p>\n Modifying the PATH environment variable is insufficient because Git commands issued remotely via SSH will still fail!<\/p>\n <\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.9.0″ _module_preset=”default” text_orientation=”justified” hover_enabled=”0″ sticky_enabled=”0″]<\/p>\n Yeah, yeah – “Is insufficient for our purposes”.<\/p>\n You might have seen some suggestions on the Internet directing you navigate to the project root directory on your computer and issue the commands<\/p>\n What this essentially does is create a section in the local .git\/config<\/em> file that looks something like this:<\/p>\n This tells the local Git configuration (the one for the project on your local computer) where to find those Git commands on the Remote Git server system. Beside the inconvenience of having to enter these for every local project, there are still a few other problems with this solution:<\/p>\n It does not work for all Git commands. It may work for the git push\u00a0<\/em>but not other operations. You would still have to run\u00a0git clone<\/em> with a bunch of “–” switches and pass the path strings directly in the command each time.<\/p>\n Worst of all,\u00a0it does not work within the Xcode IDE!<\/em><\/strong>\u00a0 That is our goal, is it not? This solution may partially work if you want to issue all your Git commands from the command line in\u00a0terminal<\/em>, but if you try to\u00a0push\u00a0<\/em>your project from the Xcode IDE menu (Source Control –> Push…) then you will immediately get this error:<\/p>\n [\/et_pb_text][et_pb_image src=”https:\/\/richrijnders.com\/file\/2020\/12\/git-batch-redeive-pack-not-found.png” title_text=”git-batch-redeive-pack-not-found” show_in_lightbox=”on” _builder_version=”4.7.7″ _module_preset=”default” custom_margin=”0px||0px||false|false” custom_padding=”0px||0px||false|false”][\/et_pb_image][et_pb_text _builder_version=”4.7.7″ _module_preset=”default” text_orientation=”justified” custom_margin=”0px||0px||false|false” custom_padding=”0px||0px||false|false” hover_enabled=”0″ sticky_enabled=”0″]<\/p>\n The reason for this is because Xcode does not recognize the settings for the remote path in the\u00a0.git\/config<\/em> file and so does not send them with the appropriate switches when issuing the remote commands via SSH.<\/p>\n <\/p>\n So the solution I have found that actually works (for our purposes) is to create\u00a0symbolic links<\/em> or “SYMLINKS” for each of the Git executables in one of the directories that\u00a0is<\/em> in the default PATH of the “git” user when executing a\u00a0non-interactive<\/em> shell. So from your\u00a0terminal<\/em> app on your computer, SSH back to the Drobo using the Drobo Admin<\/strong> user account:<\/p>\n Enter the admin password and you should be in the command line shell of the Drobo. \u00a0Now navigate to the \/bin directory:<\/p>\n Now, just enter each of the following commands one at a time:<\/p>\n You can check that all of the symlinks have been created by typing<\/p>\n You should see a list of all the symbolic links you just create, like so:<\/p>\n Type “exit” to get back to your computer’s command line. Now if we use the\u00a0type<\/em> command through SSH again, we see that our Git executable files are properly located:<\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section fb_built=”1″ admin_label=”Creating and Priming the Project’s Remote Repository” _builder_version=”4.7.7″ _module_preset=”default” custom_padding=”||10px|||”][et_pb_row _builder_version=”4.7.7″ _module_preset=”default” custom_padding=”5px||11px|||”][et_pb_column type=”4_4″ _builder_version=”4.7.7″ _module_preset=”default”][et_pb_text _builder_version=”4.7.7″ _module_preset=”default” text_orientation=”justified”]<\/p>\n Now that we have all of our infrastructure in place, let’s create and initialize the remote repository for a given project. \u00a0As an example, let’s say we have an Xcode project on our local computer called “Udder” and it is created in a directory called ~\/Projects\/Udder<\/span> and it is already under local Git control. We want to\u00a0push\u00a0<\/em>this project and all the existing\u00a0commits<\/em> to our Drobo hosted Git server.\u00a0The steps in this (and the next) section must be done for each new project that you wish to be hosted on the Drobo Git server.<\/p>\n [\/et_pb_text][et_pb_image src=”https:\/\/richrijnders.com\/file\/2020\/12\/git-local-repo-udder.png” title_text=”git-local-repo-udder” show_in_lightbox=”on” admin_label=”git-local-repo-udder” _builder_version=”4.7.7″ _module_preset=”default”][\/et_pb_image][et_pb_text _builder_version=”4.7.7″ _module_preset=”default”]<\/p>\n The first thing we need to do is to create a location for the project on the Drobo Git Server. This is simply a matter of creating a directory on the Drobo under the “GIT” share that we created earlier, and then\u00a0initializing<\/em> that directory using the git init<\/em> command. So, once again, open your\u00a0terminal<\/em> app and SSH on over to the Drobo using the “git” user ID.<\/p>\n Once you have a Drobo command line, navigate to the “GIT” share we created earlier.<\/p>\n Now create a directory for our project. You could actually name it whatever you want, but common convention is to give it the same name as the project folder on your own computer and add the “.git” extension to it. (Caution! If the original project directory name has spaces or special characters, it’s better to create the remote repository name replacing the spaces or special characters with a hyphen – or underscore _ otherwise you will encounter problems adding the remote location to the Xcode project in the next section).<\/em><\/p>\n Our project folder was named “Udder” so we will create a directory named “Udder.git”.<\/p>\n Now we will navigate into the new directory.<\/p>\n Once inside the directory, we want to initialize it for Git use. To do this, we will use the “git init” command with the “–bare” option. \u00a0This option creates all the necessary Git artifacts, but does not create a\u00a0working<\/em> copy of the project as nobody will be editing code here directly.<\/p>\n Once you see the response:<\/p>\n Then you know you have successfully created and initialized a Git Remote Repository! This location will now be the “url” of the Git Remote and referenced like in the following:<\/p>\n Type “exit” to log off of the Drobo and return to your computer’s command line.<\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section fb_built=”1″ admin_label=”Adding the Remote Repository to Your Xcode Project” _builder_version=”4.7.7″ _module_preset=”default” custom_padding=”12px||16px|||”][et_pb_row _builder_version=”4.7.7″ _module_preset=”default”][et_pb_column type=”4_4″ _builder_version=”4.7.7″ _module_preset=”default”][et_pb_text _builder_version=”4.7.7″ _module_preset=”default” text_orientation=”justified”]<\/p>\n If you open an Xcode project, at the top of the left-side navigator pane is a square icon with an “X” inside of it. This is the “Source Control Navigator”. Click it and you will see the Git artifacts for your project. The last folder in the list contains all of the defined remotes<\/em> for the project. If you expand that folder it will show any currently defined remotes. In the screen capture below for our “Udder” application I have highlighted the Source Control Navigator<\/em> icon and the Remotes<\/em> folder.<\/p>\n [\/et_pb_text][et_pb_image src=”https:\/\/richrijnders.com\/file\/2020\/12\/xcode-udder-no-remotes.png” title_text=”xcode-udder-no-remotes” show_in_lightbox=”on” _builder_version=”4.7.7″ _module_preset=”default”][\/et_pb_image][\/et_pb_column][\/et_pb_row][et_pb_row column_structure=”1_2,1_2″ _builder_version=”4.7.7″ _module_preset=”default” custom_padding=”||5px|||”][et_pb_column type=”1_2″ _builder_version=”4.7.7″ _module_preset=”default”][et_pb_text _builder_version=”4.7.7″ _module_preset=”default”]<\/p>\n Adding the new Git Remote Repository as a remote<\/em> location for this project is pretty straight-forward. The only thing to note here is that you will be using the option to add an existing remote<\/em> and NOT the option to add a “new” remote.<\/p>\n So right-click or CMD+Click on the “Remotes” folder. In the pop-up menu about half-way down is the option to “Add Existing Remote…” Go ahead and click on that option.<\/p>\n The “Add an existing remote” dialog box is displayed. In the first field you will give the remote repository a name. Keep in mind that this name is only a reference for this<\/em> project instance on this<\/em> computer. Each Xcode instance and users on other computers that clone<\/em> this project from the remote might give their remote reference a different name. The default name in Xcode is “origin” so we will use that name and type the word “origin” in the first input field.<\/p>\n [\/et_pb_text][\/et_pb_column][et_pb_column type=”1_2″ _builder_version=”4.7.7″ _module_preset=”default”][et_pb_image src=”https:\/\/richrijnders.com\/file\/2020\/12\/xcode-add-remote.png” title_text=”xcode-add-remote” show_in_lightbox=”on” _builder_version=”4.7.7″ _module_preset=”default”][\/et_pb_image][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.7.7″ _module_preset=”default” custom_padding=”8px|||||”][et_pb_column type=”4_4″ _builder_version=”4.7.7″ _module_preset=”default”][et_pb_text _builder_version=”4.7.7″ _module_preset=”default” text_orientation=”justified”]<\/p>\n The second input field is labeled “Location” and here is where we will enter the “url” for the Git Remote Repository that we created and initialized in the previous section. Enter:<\/p>\n <\/span><\/p>\n In the screenshot below you can see how I entered the url for the “Udder” project on my Drobo.<\/p>\n [\/et_pb_text][et_pb_image src=”https:\/\/richrijnders.com\/file\/2020\/12\/xcode-add-remote-modal.png” title_text=”xcode-add-remote-modal” show_in_lightbox=”on” _builder_version=”4.7.7″ _module_preset=”default”][\/et_pb_image][et_pb_text _builder_version=”4.7.7″ _module_preset=”default” text_orientation=”justified”]<\/p>\n After adding the remote Git location to your local Xcode project, your Source Code Control Navigator<\/em> will show the new location under the “Remotes” folder (you may need to expand that folder to see it). In the screen shot below you can see that the “origin” location has been added my “Udder” project. In the right-side panel is the Source Control Inspector<\/em>. If you select the “origin” remote, this panel will show you the details (url) of that remote repository. You will also note that the remote is still empty – the center pane of the IDE is still blank. This is because we have not yet pushed<\/em> our project up to the remote repository.<\/p>\n [\/et_pb_text][et_pb_image src=”https:\/\/richrijnders.com\/file\/2020\/12\/xcode-remote-added-1.png” title_text=”xcode-remote-added” show_in_lightbox=”on” _builder_version=”4.7.7″ _module_preset=”default”][\/et_pb_image][et_pb_text _builder_version=”4.7.7″ _module_preset=”default” text_orientation=”justified”]<\/p>\n Make sure that all of your current changes have been committed<\/em> to your local Git repository (Source Control –> Commit…). Now you are ready to push<\/em> your local Git to the new remote Git. Click the “Source Control” menu and then select “Push…”. You should see a pop-up like the following. <\/p>\n [\/et_pb_text][et_pb_image src=”https:\/\/richrijnders.com\/file\/2020\/12\/xcode-push-dialog.png” title_text=”xcode-push-dialog” show_in_lightbox=”on” _builder_version=”4.7.7″ _module_preset=”default”][\/et_pb_image][et_pb_text _builder_version=”4.9.0″ _module_preset=”default” text_orientation=”justified” hover_enabled=”0″ sticky_enabled=”0″]<\/p>\n The drop-down lets you select which remote<\/em> you want to push the project to, and also which branch<\/em> to push. We only have the single remote location configured (“origin”) and we also have only a single branch (“main”) so these are the only options in the drop-down. When you press the “Push” button, all of the Git artifacts will be pushed from your local Git repository to the new Git Remote on the Drobo. Once the push<\/em> completes, you will see the updated information in your Xcode Source Control Navigator<\/em>.<\/p>\n [\/et_pb_text][et_pb_image src=”https:\/\/richrijnders.com\/file\/2020\/12\/xcode-push-successful.png” title_text=”xcode-push-successful” show_in_lightbox=”on” _builder_version=”4.7.7″ _module_preset=”default”][\/et_pb_image][et_pb_text _builder_version=”4.9.0″ _module_preset=”default” text_orientation=”justified” hover_enabled=”0″ sticky_enabled=”0″]<\/p>\n You can see that now under the “origin” remote we now can see the “main” branch. If we select that branch, then our center pane shows all of the commits we had previously performed on our local Git are now also on our Remote Git. Our project is now successfully uploaded to our new Git server! Congratulations!<\/p>\n Now that the project is available on our Drobo Git Repository, it is available for any of our colleagues to clone<\/em> into their own Xcode. After you have added their SSH Public Key to the Drobo “git” user’s authorized_keys<\/em> file, all they need to do is open Xcode and select “Source Control –> Clone…” and enter the url<\/em> to the Drobo Git Remote.<\/p>\n [\/et_pb_text][et_pb_image src=”https:\/\/richrijnders.com\/file\/2020\/12\/xcode-clone.png” title_text=”xcode-clone” show_in_lightbox=”on” _builder_version=”4.7.7″ _module_preset=”default”][\/et_pb_image][et_pb_text _builder_version=”4.9.0″ _module_preset=”default” hover_enabled=”0″ sticky_enabled=”0″]<\/p>\n Woot! We now have a working Git Remote Repository running on our Drobo working with Xcode on our computers. The only ongoing administration functions we will need to perform are<\/p>\n The first one is a security function so you will always have to do that as you are the administrator of your Drobo. But I think I can help you automate the steps of the second one…[\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section fb_built=”1″ admin_label=”Bonus Code! Create and Prime Remote Repository Without Logging In To the Drobo Shell” _builder_version=”4.7.7″ _module_preset=”default” custom_padding=”18px|||||”][et_pb_row _builder_version=”4.7.7″ _module_preset=”default” custom_padding=”10px|||||”][et_pb_column type=”4_4″ _builder_version=”4.7.7″ _module_preset=”default”][et_pb_text _builder_version=”4.7.7″ _module_preset=”default” hover_enabled=”0″ sticky_enabled=”0″]<\/p>\n Each new remote repository you want to create on your Drobo will require you to:<\/p>\n Six steps just sounds like such a pain! \u00a0OK, stop rolling your eyes. I know it’s not really<\/em> all that hard and I know that I wouldn’t be creating new repositories every day. <\/p>\n Still, I am a lazy hacker. I would rather write a tool<\/em> to do those six steps than have to remember them and do them myself. Even better, a tool that other people<\/em> can use to do the task for themselves…<\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.9.0″ _module_preset=”default” hover_enabled=”0″ sticky_enabled=”0″]<\/p>\n So from the laziness of my La-Z-Boy desk chair, I present to you this bit of shell scripting:<\/p>\nWhy Not Just Use GitHub?<\/h3>\n
\n
The Pieces<\/h2>\n
\n
\n
Installing the Drobo Apps<\/h2>\n
Create a Drobo Share to House Your Git Repository<\/h2>\n
Create A “git” User On The Drobo<\/h2>\n
ssh yourdroboadmin@your.drobo.ip.address<\/span><\/pre>\n sudo adduser -h \/mnt\/DroboFS\/home\/git git<\/span><\/pre>\n sudo su git<\/span><\/pre>\n whoami<\/span><\/pre>\nAdd Your SSH Keys to Use the Git User Account<\/h2>\n
cd ~\/\n pwd<\/span><\/pre>\nDo You Already Have An SSH KeyPair?<\/h3>\n
ls -al .ssh<\/span><\/pre>\n id_rsa\n id_rsa.pub\n known_hosts<\/span><\/pre>\n ls: .ssh: No such file or directory<\/pre>\nCreate An SSH KeyPair<\/h3>\n
cd ~\/\n pwd<\/span><\/pre>\n \/Users\/yourname<\/span><\/pre>\n ssh-keygen -t rsa<\/span><\/pre>\n Generating public\/private rsa key pair.\n Enter file in which to save the key (\/Users\/yourname\/.ssh\/id_rsa):<\/span><\/pre>\n Created directory '\/Users\/yourname\/.ssh'.\n Enter passphrase (empty for no passphrase): \n Enter same passphrase again: \n Your identification has been saved in \/Users\/yourname\/.ssh\/id_rsa.\n Your public key has been saved in \/Users\/yourname\/.ssh\/id_rsa.pub.\n The key fingerprint is:\n SHA256:kf7WoKd6ZUkzS7UDnrOEk3SdaHE\/6IRHZsKWT5Zt25E yourname@YourComputer\n The key's randomart image is:\n +---[RSA 3072]----+\n | .o==+ .|\n | ..OBBooE |\n | .oB.B+ooo.|\n | .+.X++ ...|\n | S=.B.. |\n | o*o |\n | .o+ . |\n | .+ |\n | .o. |\n +----[SHA256]-----+<\/span><\/pre>\nCopy Your SSH Public Key Into the Drobo “git” User Authorized Keys File<\/h3>\n
cd ~\/\n pwd<\/span><\/pre>\n cat .ssh\/id_rsa.pub<\/span><\/pre>\nyouruser@yourcomputer ~ % cat .ssh\/id_rsa.pub\nssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDNgAcRKBp5ZJVpuvKWtG0Jgv59vwr0G5RSmhxU3VnIPrzf16b+JSyGSnap6ZDKiLTiok+t1v2f+mFzgeeqa9OrH3irhWKh+Vy+\/Rl8Z3uJMxLSOTB0rxMYD0MNTKTo+m32a8ITAE8ES8DvcGmGp5uT5pNhtAriaMM4hZusR6lbrOZUT1ffRPG2MMQOhfqQ9ZvJaqgO\/OpM20sNNJ++67vtDlIwW4I0sNynk743g1+KUQOzO3Bggr9x8Iq25fLU4cOg49kxhBeQGjP6ykA6sYYvpdXn50TcCt1b0PjkOtnM\/DAJKClBzPfF1BhJVyWhuB6wGWTIrjgfgCGcvIXbVI6w9kAiTwZvqsh8H8WNtxCp74DYYY5ONWezaLjATTI0h5Y5SJS6RdRbNSByXhuJnbIJx\/GfbrMLF2wlwFAUPl9c9IfhMUEvZY7uqm12Jvvj2oqltTL5q2g3+PJ5FOhMwXq4YDyUKIlzDMXubiBKxJD0vNEUWDpIAs\/49PKBDw5NeqU= youruser@yourcomputer<\/span><\/pre>\n ssh git@your.drobo.ip.address<\/span><\/pre>\n MyDrobo:~ $ whoami\n git\n MyDrobo:~ $ pwd\n \/mnt\/DroboFS\/home\/git<\/span><\/pre>\n ls -al .ssh<\/span><\/pre>\n ls: .ssh: No such file or directory<\/span><\/pre>\n mkdir .ssh && chmod 700 .ssh<\/span><\/pre>\n touch .ssh\/authorized_keys && chmod 600 .ssh\/authorized_keys<\/span><\/pre>\n\n
ssh git@your.drobo.ip.address<\/span><\/pre>\n ssh git@your.drobo.ip.address \"whoami\"<\/span><\/pre>\nAdd Symbolic Links (SYMLINKs) for Git Executables on the Drobo<\/h2>\n
\/mnt\/DroboFS\/Shares\/DroboApps\/git\/bin\/<\/pre>\n
Cobra5N:~ $ echo $PATH\n \/bin:\/sbin:\/usr\/local\/bin\n Cobra5N:~ $ \n Cobra5N:~ $ type -p git\n Cobra5N:~ $<\/span><\/pre>\nModifying PATH Does Not Work!<\/h3>\n
Cobra5N:~ $ echo $PATH\n \/bin:\/sbin:\/usr\/local\/bin:\/mnt\/DroboFS\/Shares\/DroboApps\/git\/bin\n Cobra5N:~ $ \n Cobra5N:~ $ type -p git\n \/mnt\/DroboFS\/Shares\/DroboApps\/bin\/git\n Cobra5N:~ $<\/span><\/pre>\n rrijnders@Richs-MBP ~ % \n rrijnders@Richs-MBP ~ % ssh git@192.168.1.65 \"echo \\$PATH\"\n \/usr\/bin:\/bin\n rrijnders@Richs-MBP ~ % \n rrijnders@Richs-MBP ~ % ssh git@192.168.1.65 \"type -p git\"\n rrijnders@Richs-MBP ~ %<\/span><\/pre>\nAdding “uploadpack” and “receivepack” to the Local Git Repository Config Does Not Work!<\/h3>\n
git config remote.origin.uploadpack \/mnt\/DroboFS\/Shares\/DroboApps\/git\/bin\/git-upload-pack\ngit config remote.origin.receivepack \/mnt\/DroboFS\/Shares\/DroboApps\/git\/bin\/git-receive-pack<\/pre>\n
[remote \"origin\"]\n uploadpack = \/mnt\/DroboFS\/Shares\/DroboApps\/git\/bin\/git-upload-pack\n receivepack = \/mnt\/DroboFS\/Shares\/DroboApps\/git\/bin\/git-receive-pack<\/pre>\n
Create the SYMLINKS!<\/h3>\n
ssh droboadmin@your.drobo.ip.address<\/span><\/pre>\n cd \/bin<\/span><\/pre>\n sudo ln -s \/mnt\/DroboFS\/Shares\/DroboApps\/git\/bin\/git git\n sudo ln -s \/mnt\/DroboFS\/Shares\/DroboApps\/git\/bin\/git-cvsserver git-cvsserver\n sudo ln -s \/mnt\/DroboFS\/Shares\/DroboApps\/git\/bin\/gitk gitk\n sudo ln -s \/mnt\/DroboFS\/Shares\/DroboApps\/git\/bin\/git-receive-pack git-receive-pack\n sudo ln -s \/mnt\/DroboFS\/Shares\/DroboApps\/git\/bin\/git-shell git-shell\n sudo ln -s \/mnt\/DroboFS\/Shares\/DroboApps\/git\/bin\/git-upload-archive git-upload-archive\n sudo ln -s \/mnt\/DroboFS\/Shares\/DroboApps\/git\/bin\/git-upload-pack git-upload-pack<\/span><\/pre>\n ls -al git*<\/span><\/pre>\n git -> \/mnt\/DroboFS\/Shares\/DroboApps\/git\/bin\/git*\n git-cvsserver -> \/mnt\/DroboFS\/Shares\/DroboApps\/git\/bin\/git-cvsserver*\n gitk -> \/mnt\/DroboFS\/Shares\/DroboApps\/git\/bin\/gitk*\n git-receive-pack -> \/mnt\/DroboFS\/Shares\/DroboApps\/git\/bin\/git-receive-pack*\n git-shell -> \/mnt\/DroboFS\/Shares\/DroboApps\/git\/bin\/git-shell*\n git-upload-archive -> \/mnt\/DroboFS\/Shares\/DroboApps\/git\/bin\/git-upload-archive*\n git-upload-pack -> \/mnt\/DroboFS\/Shares\/DroboApps\/git\/bin\/git-upload-pack*<\/span><\/pre>\n % ssh git@your.drobo.ip.address \"type -p git-receive-pack\"\n \/usr\/bin\/git-receive-pack\n %<\/span><\/pre>\nCreating and Initializing a New Git Remote Repository<\/h2>\n
ssh git@your.drobo.ip.address<\/span><\/pre>\n cd \/mnt\/DroboFS\/Shares\/GIT<\/span><\/pre>\n mkdir Udder.git<\/span><\/pre>\n\u00a0 cd Udder.git<\/span><\/pre>\n git --bare init<\/span><\/pre>\n\u00a0 Initialized empty Git repository in \/mnt\/DroboFS\/Shares\/GIT\/Udder\/<\/span><\/pre>\n\u00a0 git@your.drobo.ip.address:\/mnt\/DroboFS\/Shares\/GIT\/yourProject.git<\/span><\/pre>\nAdding the Remote Git Repository to Xcode<\/h2>\n
git@your.drobo.ip.address:\/mnt\/DroboFS\/Shares\/GIT\/yourproject.git<\/pre>\nPush the Project to the Git Remote Repository<\/h3>\n
git@your.drobo.ip.address:\/mnt\/DroboFS\/Shares\/GIT\/yourProject.git<\/span><\/pre>\nMission Accomplished!<\/h2>\n
\n
Bonus Code!<\/h2>\n
\n
The Create Git Repository Script<\/h3>\n