Good-to-know
Using @cap-js/sqlite in CF for your CAP services
I published a couple of short posts recently: Running non-production CAP services in CF Easily add an explicit cds.requires.db to your CAP project's package.json Both of them are related to going...
read postRunning non-production CAP services in CF
Sometimes I want to run test CAP services not only locally, but in the cloud. I don't want the trappings of production (which are of course important ... in production settings) such as a production...
read postEasily add an explicit cds.requires.db to your CAP project's package.json
In an experimental CAP project serving data in an in-memory SQLite persistence mechanism, seeded from CSV files (as per the classic starting point in CAP's Grow As You Go approach), I wanted to have...
read postImprove your CAP dev container shell prompt
In the current back to basics series on CAP Node.js we're using VS Code with a dev container, based on the definition in the repo for the series. The container image is based on this one: FROM...
read postAvoid design time CAP server restarts when maintaining local data files
Starting the CAP server with cds watch is great for tight development loops at design time, especially with the built-in in-memory SQLite persistence layer, seeded by data in CSV files. When the...
read post