origin
points to your new branded edition and upstream
points to your institutional fork. consortium
that points to the ElentraProject API so that you can keep in sync with the latest updates to your Elentra release branch.ssh-keygen
command to initialize a new SSH key and press the enter key through each question. "elentrapackages/elentra-1x-api"
in your Elentra ME composer.json
file. You can also review the Compatibility Matrix documentation to find the appropriate version.repositories
section in the composer.json
file in your Elentra installation above the packagist entry. The repository type should be set to "git" and the "url" set to the SSH URL from your branded repository.composer.lock
file before each deployment. enable_branded_api
setting in your deployment/deploy.php
file to true
.composer.lock
is a file that keeps track of exactly which versions of a project's dependencies were used when it was generated. This speeds up the dependency resolution process during deployment and ensures a consistent state each time composer install is run. What this means for us is that because the Elentra API is currently included as a composer dependency, we must regenerate this file each time we tag a new release of the Elentra API. composer.json
and composer.lock
file and push the commits to your Branded Edition Elentra repository remote. composer.lock
file when tagging releases in the future.master
branch.master
will point to the most recent tag.develop
branch because it may have breaking changes introduced during the development cycle.