- All development is done from the IBM i - single repository over the Profound.js modules folder (non-bare) where developers make individual commits from the same folder.
- All development is done locally and changes are pulled into the IBM i - remote repository hosted on cloud/local-network server where developers develop on their local machines and make commits to the remote repository. Some cloud services provide private repositories.
Option 1 - Develop on the IBM i
This option is the easiest to setup. Via pase:
When people are creating, deleting or modifying files, each individual should make commits to the files they change.
<div align="center" style="position:relative;height:360;width:640"><iframe width="640" height="360" src="https://www.youtube.com/embed/jInntFxTwrA" frameborder="0" gesture="media" allow="encrypted-media" allowfullscreen></iframe></div>
Option 2 - Develop Locally with a Cloud Repository
This option is best for distributed development. First, you will want to setup either a local-network repository or use a cloud hosting service such as GitHub or BitBucket.
This wlll create the git repository in a sub-folder within modules.
Pulling the changes onto your IBM i
- Clone your repo within your Profound.js installed on your IBM i, with a final parameter of 'modules - which tells the clone to 'clone' into the modules folder:
git clone https://github.com/user/myproductmodules.git modules
git pullevery time you'd like to pull new commits down to your IBM i.