CloudFoundryFun #8 - Local CAP development with Azure services
Marius Obert develops and debugs a CAP app locally while it targets Cloud Foundry backing services in production: a .cdsrc.json [production] block switches the database kind between SQLite for local runs and SAP HANASAP HANASAP’s relational database platform, which stores application data and executes SQL and SQLScript in the database, available on-premise and as the managed service SAP HANA Cloud.sap official, btp for the cloud HDI container, and a credentials.json file plus a cfenv.isLocal check stand in for the Azure Storage Account binding Cloud Foundry would otherwise inject. He sets up VS Code launch.json configurations that start the CDS server, the @sap/approuter@sap/approuterSAP's Node.js application router: the single entry point in front of a business application's microservices, which authenticates the user, forwards each request to a backend by route and serves static content.sap official, btp and an uploader microservice each in Node's --inspect debug mode on its own port, so the three can be stepped through together during local development.
Where it sits
Who is behind it
In the atlas: contributes to 3, wrote 1@IObertauthor
Properties
About this work
onedevatlas is open for browsing. Find tools for SAP development, compare their documented capabilities, ask your AI assistant, and join a flight during TechEd week.
Details
Graph
Source
History
- Entered the atlasDiscovered via SAP Community · cap-tag.
For your agent
- Ref
content:cloudfoundryfun-8-local-cap-development-with-azure-services- JSON
- /content/cloudfoundryfun-8-local-cap-development-with-azure-services.json
- MCP
- Connecting an agent