Next Steps: Development and Build Pipelines
After exploring the installed Precomposer components, you can begin developing your own features and services.
Step 1: Copy and Clone Service Repositories
To start development, create a copy one or more of the following Precomposer service repositories by using "Use this template"
- E-Commerce Hub: Repository epc-aggregator-api (opens in a new tab)
- Storefront: Repository epc-storefront (opens in a new tab)
- Pricing Service: Repository epc-pricing-service (opens in a new tab)
Step 2: Configure GitHub Secrets and Variables
- Create the
EPC_PAT
Secret:
Settings -> Secrets and variables -> Actions -> Secrets -> New repository secret
.
- Add a new secret named
EPC_PAT
in each of your newly created Precomposer service repositories. - Use the same credentials as you used for the
PERSONAL_ACCESS_TOKEN
that you used during the installation process.
- Set the
DEPLOYMENT_REPO_NAME
Variable (if applicable):
This is only necessary if you renamed the
epc-deployment-configurations
repository during the installation step:
Settings -> Secrets and variables -> Actions -> Variables -> New repository variable
.- Create a variable named
DEPLOYMENT_REPO_NAME
and set its value to the name of the renamed deployment-configuration repository.
Step 3: Commit and Deploy
Once the above configurations are complete, you can start committing changes to your service repositories. The corresponding pipelines will automatically:
- Build the changes.
- Deploy the updates to your environment.
For more details on how the pipelines work, refer to the Build and Deployment Pipelines Documentation.
Notes
- The automated pipelines ensure that your changes are tested, built, and deployed seamlessly.
- If you're new to deployment pipelines, you can explore resources like What is a Deployment Pipeline? (opens in a new tab) or How to Build a DevOps Pipeline (opens in a new tab) for additional insights.
- Ensure that all secrets and variables are securely configured to avoid deployment issues.