onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →Reference

cap-redis

A sample that holds the approuter's session, CSRF token included, in a bound instance of Redis on SAP BTP, hyperscaler option instead of the approuter's own memory, around a CAP and Fiori elements app.

The approuter.nodejs module sets EXT_SESSION_MGT to an object naming instanceName: cap-redis-redis and storageType: redis, with a defaultRetryTimeout of 10000 and a backOffMultiplier of 10, adds SVC2AR_STORE_CSRF_IN_EXTERNAL_SESSION: true, and requires the cap-redis-redis resource: an instance of Redis on SAP BTP, hyperscaler option on the trial plan with engine_version: "6.0" and eviction_policy: noeviction. Around that session sits the ordinary shape it belongs to, a CAP service on a HANA HDI container, a Fiori elements app deployed to the SAP HTML5 Application Repository service for SAP BTP and served through the same approuter, xsuaa, and a destination to https://ui5.sap.com. decode_redis_data.sh in the repository root base64-decodes, gunzips and pretty-prints a value pasted into the script, which is how to read what landed in the cache. The README is the CAP scaffold's own, and the repository description, "Approuter + Redis", is what names the subject.

GitHub0 ★

Facts

Last push

Where it sits

Lives in
CAP
Demonstrates
DeploymentCAPDeploymentcapabilityGetting an application onto a runtime and keeping it there: build descriptors, deployment topology, service bindings and lifecycle operations. The target runtime determines how the application is packaged and configured.App hostingCAPApp hostingcapabilityWhere a built frontend lives and what serves it — the static files of a frontend application after the build, reachable behind a login and beside the API it talks to, without a web server of your own.
Flavors
Node.jsfrom its runtime
Runs
Cloud Foundry
Requires
Redis on SAP BTP, hyperscaler optionRedis on SAP BTP, hyperscaler optionartifactThe approuter's external session store: the descriptor binds a redis-cache instance and names it as the store in the router's own configuration.@sap/approuter@sap/approuterartifactThe session being stored is the approuter's own, and the deployment includes the router module that holds the configuration.SAP HTML5 Application Repository service for SAP BTPSAP HTML5 Application Repository service for SAP BTPartifactThe Fiori elements app is uploaded to an app-host instance and served from the app-runtime plan through the same approuter.

Who is behind it

Mio YasutakeMio YasutakePersonMaintains this
In the atlas: maintains 47, contributes to 47, wrote 10@miyasutamaintainer

Before choosing this

Signals

LicenceNo licenseNeither the package manifest nor the repository tree declares a licence

Without a licence the default is all rights reserved. Ask the maintainer, or check for terms stated elsewhere, before depending on it.

Conditions

PracticalFunctional boundary

Not a descriptor to deploy as it stands: the approuter's sessionSecret is written out in mta.yaml.

What it declares

Every artifact

Type
Sample
Origin
Independently maintained
Use as
A reference
Runtime
Node.js
Runs on
Cloud Foundry

As a sample

Form
does not say

Connections5

Download
cap-redis connectionscap-redisPROVIDES→ demonstrates2demonstrates authoredApp hostingdemonstrates authoredDeploymentNEEDS→ needs3needs declared The session being stored is the approuter's own, and the deployment includes the router module that holds the configuration. miyasuta/cap-redis — mta.yaml: https://raw.githubusercontent.com/miyasuta/cap-redis/main/mta.yaml@sap/approuterneeds declared The approuter's external session store: the descriptor binds a redis-cache instance and names it as the store in the router's own configuration. miyasuta/cap-redis — mta.yaml: https://raw.githubusercontent.com/miyasuta/cap-redis/main/mta.yaml miyasuta/cap-redis — mta.yaml, resources: https://raw.githubusercontent.com/miyasuta/cap-redis/main/mta.yamlRedis on SAP BTP, hyperscaler optionneeds declared The Fiori elements app is uploaded to an app-host instance and served from the app-runtime plan through the same approuter. miyasuta/cap-redis — mta.yaml, resources: https://raw.githubusercontent.com/miyasuta/cap-redis/main/mta.yamlSAP HTML5 Application Repositoryservice for SAP BTP

README

quoted from miyasuta/cap-redis, read
miyasuta/cap-redis/README.mdOn GitHub

Getting Started

Welcome to your new project.

It contains these folders and files, following our recommended project layout:

File or FolderPurpose
app/content for UI frontends goes here
db/your domain models and data go here
srv/your service models and code go here
package.jsonproject metadata and configuration
readme.mdthis getting started guide
excerpt, no licence read, read the rest, on GitHub

Details

Sources3
GitHub APIdiscovered here, miyasutachecked
github.com/miyasuta/cap-redistree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
runtimesnode
deploymentCloud Foundry
discovered viaGitHub API · miyasuta
first seen in the atlas
ecosystem and domaincap, operations-and-runtime
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:miyasuta-cap-redis
JSON
/artifacts/miyasuta-cap-redis.json
MCP
Connecting an agent