No description
  • JavaScript 52.5%
  • HTML 24%
  • Dockerfile 23.5%
Find a file
hamoudi 162426be05 deploy-app: no Dockerfile in the app's repo, the platform picks the recipe
The pipeline now builds an app from the platform's recipe for its kind
(logfab.cloud, cluster/manifests-hostup/platform/recipes/), chosen from its
package.json, so the repo holds only the app, deploy/ and catalog-info.yaml.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 17:16:47 +02:00
templates deploy-app: no Dockerfile in the app's repo, the platform picks the recipe 2026-10-16 17:16:47 +02:00
all.yaml "Deploy my app" template, for apps that already exist 2026-10-14 16:01:19 +02:00
README.md deploy-app: "Node.js app with its own server" as a second kind of app 2026-10-14 16:59:55 +02:00

software-templates

Templates for Red Hat Developer Hub's "Create" page on the OpenShift cluster on HostUp. Developer Hub reads all.yaml from this repo (set in logfab.cloud, cluster/manifests-hostup/devhub/02-app-config.yaml) and rereads it every few minutes, so a pushed change shows up by itself.

Template Makes
nodejs-app "New Node.js app": a small Node.js web app in its own Forgejo repo, listed in Developer Hub and live on OpenShift
deploy-app "Deploy my app": a home for an app that already exists (a React / Vite website, or a Node.js app with its own server), with a placeholder page until the app is pushed into it

A template is a template.yaml (the form and the steps) and the folders it copies into the new repo. In those files, ${{ values.name }} and the like are filled in from the form.

  • shared/: what every app gets, whatever the template: deploy/ (how it runs on OpenShift) and catalog-info.yaml (how it is listed in Developer Hub).
  • nodejs-app/skeleton/: the starter app.
  • deploy-app/types/<type>/: how one kind of app is built and served. Another kind of app is another folder here and another entry in the template's type field.