How to begin collaborating with Far Beyond Code on a repository

  Follow me: Follow Bruce Kirkpatrick by email subscription Bruce Kirkpatrick on Twitter Bruce Kirkpatrick on Facebook
Tue, Feb 25, 2014 at 6:05PM

Working with Far Beyond Code, LLC on the source code for client projects requires working through Git version control using the integration manager workflow.  While most of our work is open source, client projects are not fully open source, and this requires sharing code through privately hosted git version control.  Be sure not to make the project available.

Before setting up a project repository on your computer, you need to have a working copy of Jetendo Virtual Machine with Jetendo CMS installed which can be downloaded from  

Follow the Jetendo Server Virtual Machine Readme to personalize it to your development environment.  This process should only take up to an hour for a new user.  If you get stuck, let me know so we can improve the documentation.

Step 1:

Your project's git repository will be a URL like shown below, where is the project's primary domain.   (note this example is not a real project.)

Ask Bruce Kirkpatrick for the correct URL and to assign your bitbucket account to it.

Step 2:

After you have access to the repo URL, click on "Fork".  Screenshot below:

On the next page, you can leave everything as the default setting and click "Fork Repository" at the bottom.

Step 3:

Now the repository exists on your bitbucket account with full access to push and pull changes to it.

You should be able to access it like shown below, where username is your username and is your project's primary domain:

Step 4:

We recommend downloading and installing the Github desktop client software for Windows or Mac to help you visualize your git project, so you don't have to learn as much about git commands right away.  Even though we're using, Github's software is designed to work with any git remote server because it uses the standard git commands for everything.

Step 5:

After the git client software is installed, you should clone the repository to your computer in the /path/to/jetendo/sites/ directory.

To find the git clone path to use, go to your forked repository on your bitbucket account, and copy the HTTPS URL to your clipboard. Screenshot below:

Step 6:

Now that you have the source code, you'll just need to setup the project in Jetendo CMS Server Administrator browser interface by making the site's configuration to match the configuration of the site on the live server.   Bruce Kirkpatrick will provide the configuration information or give direct access to the production Jetendo CMS Server Administrator to help with this step.   Sometimes, you may need a backup of the user upload files and other database information, which can also be obtained through the Jetendo Server Administrator.

Step 7:

After your development environment is fully setup, you will be able to access your project's domain on your own computer as shown below:

Site Manager:

Step 8:

Make changes on your local copy of the project and commit them to your local git repository.  Usually, it is a best practice to create a new branch before making changes, so it is easier to create a small pull request later that has a descriptive name of the changes.

Step 9:

Push the changes to your bitbucket fork.  In GitHub client, this is the "sync" icon or via command line, type: git push origin

Step 10:

On, create a pull request from your fork to the main repository.
Wait for me to review your work and merge or comment on the changes you made.
Then I merge your pull request, test/integrate it further, and then I publish the work to the production server.

You're done.

Nearly all software is built like this around the world, especially open source projects.   It will feel very productive and fix many common development problems once you get used to it.  

If you have trouble understanding Git, Bitbucket or Jetendo CMS documentation, let me know.

Bookmark & Share

Popular tags on this blog

Performance |