Building OCI Images with Cloud Native Buildpacks (pack CLI)
Tutorials that teach this
- Tutorial Deploy in SAP BTP, Kyma Runtime
- Tutorial Deploy a CAP Application with PostgreSQL in SAP BTP, Kyma Runtime
- Tutorial Deploy and Run the Incident Management Application in the SAP BTP, Kyma Runtime with SAP S/4HANA Cloud Backend
- Tutorial Install Tools for Deployment
- Tutorial Fast Prototyping in SAP BTP, Kyma Runtime Using App Push
- Tutorial Prepare Multi-Tenant Applications for Deployment with CAP Operator
- Tutorial Deploy a Node.js Application in SAP BTP, Kyma runtime
- Tutorial Install a Mock Server in the SAP BTP, Kyma Runtime
- Tutorial Deploy a Multitenant Application to a Provider subaccount, Kyma Runtime
- Tutorial Deploy and Run the Incident Management Application in the SAP BTP, Kyma Runtime with a Mock Server
Docs explaining this concept
Prerequisites
- Concept Docker Image Build and Publish
- Concept Docker Installation and Setup
- Concept Node.js Development on SAP BTP
- Concept Node.js Buildpack Version Pinning Node.js Buildpack Version Pinning is a configuration practice in which a developer locks an application to a specific version of the Node.js buildpack on SAP Business Technology Platform, rather than relying on the default or latest version. Developers use it to avoid unexpected behavior or breaking changes that can occur when the platform automatically updates the buildpack. Guidance on this practice is covered in the [Node.js Buildpack: Troubleshooting](https://help.sap.com/docs/btp/sap-business-technology-platform/1462ff0fa7f04839a96c51d968d15b34?locale=en-US&state=PRODUCTION&version=Cloud) documentation as a known issue resolution strategy.
- Concept Building and Pushing a Custom Docker Image
- Concept Node.js Installation and Setup
- Concept Installing Node.js Dependencies with npm install
- Concept Docker Container Packaging