onedevatlasBeta
Browse the atlas
AllCAPBTPUI5ABAP
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-reuse-html5

A Fiori elements app uploaded to the HTML5 Application Repository together with a cdm.json, and a second repository instance on the app-runtime plan behind a subaccount destination pointing at /applications/cdm/cap-reuse-html5.

The app's build:cf script copies workzone/cdm.json into dist after the UI5 preload build, and the com.sap.application.content module uploads miyasutamanagebooks.zip and cdm.json together to the app-host instance of the SAP HTML5 Application Repository service for SAP BTP. A second instance of that service, on the app-runtime plan, backs a subaccount destination named cap_reuse_html5_cdm whose url is written out in full as https://html5-apps-repo-rt.cfapps.us10.hana.ondemand.com/applications/cdm/cap-reuse-html5; a comment in the descriptor records why, that ${default-domain} resolves to us10-001 on the trial while the repository runtime's domain is us10. The cdm.json holds a catalog and a workpage, each carrying one visualization with appId: miyasuta.managebooks and vizId: Books-manage. A second content module creates the instance destinations, one for the app host and one OAuth2UserTokenExchange against xsuaa, and the README is the CAP scaffold's own.

GitHub0 ★

Facts

Last push

Where it sits

Lives in
CAP
Demonstrates
Launchpad and site contentBTPLaunchpad and site contentcapabilityGetting apps, cards, pages and workspaces in front of users in an application launchpad or portal, including content providers, content packages and access roles. Serving the application’s files is [app hosting](capability:app-hosting); extending the surrounding shell is [launchpad plugins](capability:launchpad-plugins).App hostingCAPBTPApp 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.
Serves
BTP/BAIP
Flavors
Node.jsfrom its runtime
Runs
Cloud Foundry
Requires
SAP HTML5 Application Repository service for SAP BTPSAP HTML5 Application Repository service for SAP BTPartifactTwo instances of it: an app-host the app and its cdm.json are uploaded to, and an app-runtime instance the subaccount destination reads the content descriptor from.SAP Destination serviceSAP Destination serviceartifactThe destination service holds both the instance destinations the content module creates and the subaccount destination that points at the content descriptor.

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

The subaccount destination's url names the us10 trial's repository runtime, so another region or subaccount needs it rewritten before the descriptor deploys.

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

Connections4

Download
cap-reuse-html5 connectionscap-reuse-html5PROVIDES→ demonstrates2demonstrates authoredApp hostingdemonstrates authoredLaunchpad and site contentNEEDS→ needs2needs declared The destination service holds both the instance destinations the content module creates and the subaccount destination that points at the content descriptor. miyasuta/cap-reuse-html5 — mta.yaml, resources: https://raw.githubusercontent.com/miyasuta/cap-reuse-html5/main/mta.yamlSAP Destination serviceneeds declared Two instances of it: an app-host the app and its cdm.json are uploaded to, and an app-runtime instance the subaccount destination reads the content descriptor from. miyasuta/cap-reuse-html5 — mta.yaml, resources: https://raw.githubusercontent.com/miyasuta/cap-reuse-html5/main/mta.yamlSAP HTML5 Application Repositoryservice for SAP BTP

README

quoted from miyasuta/cap-reuse-html5, read
miyasuta/cap-reuse-html5/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-reuse-html5tree, 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, ui-and-frontend-bridge
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:miyasuta-cap-reuse-html5
JSON
/artifacts/miyasuta-cap-reuse-html5.json
MCP
Connecting an agent