If you’ve been following along in the Git for the SalesLogix Developer series, you should now have Git installed and configured. Now it’s time to start putting it to use. In this post (and included video), I will outline the steps to take an existing SalesLogix project and put it under Git source control. Setting up the initial repository is not a hard task, but knowing all the steps is the only way to get it done.
Before we get too far ahead, be sure you’ve taken a look at the previous post in the series and have Git set up and installed so you can follow along and create a repository for your SalesLogix system. But first, what is all this for? Setting up the repository is done once, by one person. Once the initial repository is created, it can be hosted (such as on Github) so that multiple developers can all work on that same repository.
Video of Setting up your SalesLogix Repository
Watch the following video to walk through the entire process. From start to finish. You’ll see how to take your current SalesLogix system, put it under source control, and add it to Github so you can work on that system with multiple developers (or if you’re just working by yourself and want to take advantage of using a source control system and versioning).
Let’s outline all the steps covered in the video. Just to be clear, these steps are done just once, by one person on your team. Once the initial repository is created it can be hosted on Github and shared with the rest of the team. I’ll cover in a future post how the rest of the team grabs the hosted repository so they can work with it.
- Create a new repository on Github and add any developers on your team as collaborators
- In Application Architect export the SalesLogix model to the file system
- While still in Application Architect, click the “Browse Git Repository” button on the toolbar (this was added by installing “Git Extensions for SalesLogix”)
- You’ll be prompted to create a repository for the current workspace directory, click “Yes”. Note, this creates a local repository which you’ll later push to the Github repository
- Click the “Commit” button to bring up the commit dialog
- Stage all files, add a comment and click commit to add all files to local repository
- Go to the “Git Extensions” menu and select “Manage Remote Repositories” in Application Architect
- Fill out the following in the dialog to create a remote for the Github repository. Name = “origin”, Url = “url from github”, then click “Save”, when asked about default pull behavior for remote, click Yes
- When done, go to Default pull behavior tab. Make sure local branch name = “master”, Remote repository = “origin” and Default merge with = “master”, then Save and close Remote dialog.
- Click “Push” button on toolbar and push repository to github.
I mentioned on the video, that PuTTY will give you an error if this is the first time you’ve done any of this on your machine. The reason for this is that PuTTY wants the SSH key for Github to be cached in the registry. The easiest way to accomplish this is to use the registry file I have included below. This will add it to the registry quick and easy for you.
|Download registry fix: GithubSshHostKeys.zip|
Next up in the series we’ll look at how to use this repository so other developers on your team can make use of the repository you’ve set up and collaborate with you.