For today’s post we’re going to take a look at GitHub Connect … It’s the link between the On-Premises installation of GitHub Enterprise Server and the popular SaaS offering (as we all have come to love it) called GitHub. 😉
Installing GitHub Enterprise Server (on Azure)
So my journey for today started with registering for the GitHub Enterprise Trial, where I decided to install it on Azure… as my “On Premises” location.
Before pressing the “Deploy to Azure”-button, I did download the license file…
Followed by deploying the GitHub Enterprise Server to my Azure Subscription ;
Before that one actually started, we do need to foresee some parameters. Though it’s a very simple set of parameters.
After about 6,5 minutes the deployment finishes…
And you can access the portal on the DNS name linked to the NIC of the server you deployed ;
There we upload our license file and enter the admin password ;
You can then choose the installation type, where I went for the “New Install” ;
Here you are prompted with the option to add additional authorized SSH keys ;
And with the SSH access, we can even access the operating system level of the server (as you would expect) ;
Now let’s do some changes, and save. The instance will now finish up the installation process.
And once done, the button to “Visit your instance” will be enabled.
Configuring your GitHub Enterprise Server
Upon the first visit you’ll be prompted to create the admin account ;
And let’s create our first organization ;
Add members to it…
And … what about our first repository?
Where we have the same user experience as we would have with GitHub.com ;
Enabling GitHub Connect
Now let’s enable GitHub Connect. Browse to “Settings” and navigate to “Enterprise account settings” ;
Here you click on “GitHub Connect” ;
And then press the nice green button “Enable GitHub Connect” ;
If you see the following… Then your GitHub.com account is not linked to a GitHub Enterprise organization ;
So I quickly registered for a trial …
Boom, that’s done!
Giving me an additional organization…
And now that organization will become available in our private GitHub Enterprise ;
Press”Connect”, and you’ll be linked up, where you can enable/disable certain capabilities ;
Taking a look on GitHub.com, at the organization, you’ll see a “GitHub Connect”-option too. Which will show which GitHub Enterprise Servers are linked to that organization.
Let’s test the connect(ion)
So let’s search…
Though it did not give any results. It appears that I did not enable the search on GitHub.com. Let’s enable it…
And then try searching…
You’ll see that it will fail to show local results ;
But there is also the “GitHub.com results” pane, which will show the GitHub.com results ;
If we go to “Advanced”, we can also select “GitHub.com” as environment. ;
Which will take us immediately to that pane ;
Personally I was wondering what the “Hybrid integration” between GitHub.com and GitHub Enterprise Server would look like. Here I was pleasantly surprised! The user experience between both are almost identical, or at least as much as you would expect. In the quick test, I limited my test to the search aspect.
Though when looking at the documentation, the GitHub Connect will unlock the following ;
Where I can surely see the fit for several organizations.