Working On Multiple Projects

You may need to be able to quickly switch between stacks and projects as the complexity of your Caliper SDK effort grows. To develop for different projects, you need a shared dev location and a local IDE directory for each project.

Shared Dev

To facilitate your shared dev location, you will need to run switch_project in order to create the necessary git repository and directory for each project. As a Certified Partner, all customer projects will be saved to ~/<customer-directory>/<customer-project>. Otherwise, you will see the project directory in shared dev alongside ~/sdk, which is the default project created for your institution when you began using the SDK.

IDE

Each additional project will also require a new IDE project directory on your local machine. In your IDE, you can create a copy of your existing SDK project, changing the remote server location where appropriate for your project.

Once you have completed setting up shared dev and your local IDE, you will be able to SSH into the shared dev machine where you were last working by default. This default location will only change when you run switch_project again to work on another project.

Preparing for UUX Upgrades

You can also use switch_project to switch stacks. This may be helpful when taking a major upgrade at Q2 to prepare your existing project for a new stack. In this case, ~/sdk remains your project directory in shared dev, and you should be able to use your existing IDE project without making any changes.

Requesting a New Project

Typically, you only need a single project for your institution to build extensions over time, and inherit from ancillary extensions when building more complex workflows. If you need a new standalone project, please contact https://q2developer.com/support/create?ticketType=General. The SDK support team will create a new Gitlab repository and will make any changes necessary to support using switch_project in shared dev.