Deploy link
https://app.appaloft.com/?modal=quick-deploy&source=blueprint&sourceExtension=cloud-blueprint-marketplace&blueprintSlug=pocketbase&blueprintTitle=PocketBase&blueprintProfile=production&step=project&projectMode=new&projectName=PocketBase One-click deploy is not another YAML format. The button points to the Appaloft deploy entry; the deployable topology still lives in a Blueprint.
https://app.appaloft.com/?modal=quick-deploy&source=blueprint&sourceExtension=cloud-blueprint-marketplace&blueprintSlug=pocketbase&blueprintTitle=PocketBase&blueprintProfile=production&step=project&projectMode=new&projectName=PocketBase [](https://app.appaloft.com/?modal=quick-deploy&source=blueprint&sourceExtension=cloud-blueprint-marketplace&blueprintSlug=pocketbase&blueprintTitle=PocketBase&blueprintProfile=production&step=project&projectMode=new&projectName=PocketBase) https://www.appaloft.com/badge/deploy.svg The badge is shipped with the appaloft.com static site. It does not require static.appaloft.com.
The application or service topology definition, still appaloft.blueprint/v1.
URL parameters carry the user into the Appaloft Cloud /deploy page.
Appaloft provides the fixed brand badge; app READMEs reference the image and link.
Remote entries use the blueprintUrl parameter to point at a publicly readable appaloft.blueprint.yaml. Cloud reads the same appaloft.blueprint/v1 manifest; apps do not need a new yml format.
schemaVersion: appaloft.blueprint/v1
id: pocketbase
name: PocketBase
version: 1.0.0
summary: PocketBase service
components:
- id: app
name: PocketBase
kind: service
runtime:
strategy: container-image
image: ghcr.io/muchobien/pocketbase:latest
ports:
- name: http
containerPort: 8090
protocol: http
public: true
routes:
- port: http
pathPrefix: /
profiles:
production:
label: Production