AppBuilder Portal

Description

The appbuilder-portal is the portal frontend/backend for the Scriptoria project. This project provides software to automate the building and publishing of Scripture App Builder apps (and other related content) to App Stores and websites. It runs as a single docker container, requiring a database and redis (valkey) server.

This process requires the coordination of user activites, project data, automated services, and administrative activities (e.g. managing App Store listings). The portal provides organization, group, user, project, and product management and provides access to users and organizational admins to interact with the workflow activities.

This process also requires management of resources to store project data (AWS S3), generate product files from project data (AWS CodeBuild), and store product files for distribution (AWS S3). These resources are managed by AppBuilder BuildEngine, which can be setup on a per-organization basis.

Development

Prerequisites

• Docker CE (Docker Desktop on Mac)
• Volta - controls which version of node is used per directory

Common scripts are in the run file, so be sure to check that for reference.

First-time setup

1. Clone the repository.

git clone https://github.com/sillsdev/appbuilder-portal
cd appbuilder-portal

1. Create environment file Create a .env file in the root directory with the following variables:

DATABASE_URL="postgresql://db-user:1234@localhost:5432/development?schema=public"
MAIL_SENDER=LogEmail
AUTH0_CLIENT_ID=n8IAE2O17FBrlQ667x5mydhpqelCBUWG
AUTH0_DOMAIN=sil-appbuilder.auth0.com
AUTH0_CONNECTION=Username-Password-Authentication
DEFAULT_BUILDENGINE_URL=https://dev-buildengine.scriptoria.io:8443
APP_ENV=dev

AUTH0_SECRET=
AUTH0_CLIENT_SECRET=
DEFAULT_BUILDENGINE_API_ACCESS_TOKEN=
ADMIN_EMAIL=

USER_DATA_TURNSTILE_SECRET_KEY=
PUBLIC_USER_DATA_TURNSTILE_SITEKEY=

Note: Contact @sillsdev/scriptoria-developers for help obtaining the secret values.

1. Install and bootstrap

# Install dependencies
npm i
# Bootstrap database and initalize docker support images (db adminer valkey)
./run bootstrap

1. Start development server

# Start the local dev server and create a user invite link
ADD_USER=true npm run dev

Visit http://localhost:6173 to see the homepage of the site, then click the invite link in the console to setup your admin account.

Running in Docker

./run up

Visit http://localhost:6173 to access the web application frontend.

Visit http://localhost:18080 to access the development database using Adminer.

• System: PostgreSQL, Server: db, Username: db-user, Password: 1234, Database: development

Visit http://localhost:6173/admin/jobs to access the BullMQ tasks queues.

Running in the Host OS

This is important for local development. You still need the db and valkey docker images running.

Start database and adminer

./run local

Start SvelteKit project

npm run dev
# or
npm run build; NODE_ENV=development npm run preview

Connecting to BuildEngine

Set DEFAULT_BUILDENGINE_URL in your .env file to the URL of the AppBuilder BuildEngine instance you want to use.

Testing and linting

CI_EMAIL= CI_PASSWORD= PW_TEST_CONNECT_WS_ENDPOINT=ws://127.0.0.1:3000 npm run test
npm run lint

Currently tests check that the page comes online and that a user is able to login. The CI_EMAIL and CI_PASSWORD environment variables are required to test login functionality. They should be set to the Auth0 credentials the test runner should login with.

Deployment

Building The Docker Images

./run build

Production

Database configuration

Before starting the docker container in production, make sure to deploy Prisma migrations using npx prisma migrate deploy.

Special Thanks

For authentication and authorization services:

For localization management: