WBSP
ProvidersDocsSign in
All pages

The WBSP platform provides multiple ways to deploy your application on your development machine:

  1. dev - the database, REDIS and any other services you require get deployed in Docker using the docker compose ... command. You develop your application in your IDE, with live reloading.

  2. compose - similar to dev mode, except your application also runs within Docker. This allows you to confirm that the Docker build is running correctly.

  3. standalone - we build a single Docker image that contains your application, and a database and REDIS (if required). This self-contained image can be used to allow users to 'demo' your software.

Authentication

By default, the three deployment options above all use the website auth server.

App configuration - wbsp.yaml


...
destination:
  standalone:
    type: standalone
    tenant: wbsp

  dev:
    type: dev
    tenant: wbsp
    env:
      HAP_AUTH_ENABLED: "true"
      HAP_BASE_URL: https://wbsp-auth.wbsp-demo.com
      HAP_TENANT: wbsp
      HAP_TENANT_ID: 6d8e672b-d5ab-494f-a53a-120681b1ce16
      HAP_WEBSITE_REDIRECT_URI: http://localhost:3000/api/auth/callback
      HAP_WEBSITE_POST_LOGOUT_REDIRECT_URI: http://localhost:3000/
      APP_BASE_URL: http://localhost:3000

  compose:
    type: compose
    tenant: wbsp

  ...

Deploying

wbsp-app deploy --destination dev|compose|standalone