Couchbase Migrator

Getting Started

Once the container is built, you need to switch to Node 18 in your terminal using nvm:

nvm use 18

Environment Setup

Before running the script, you need to set up the database URLs in your environment variables. The following environment variables are required:

• PRISMA_API_USERS_URL - Database connection URL for API Users
• PRISMA_API_MEDIA_URL - Database connection URL for API Media
• PRISMA_USERS_URL - Database connection URL for Users (optional), this is a SQLite Database used to temporarily store user data needed for other objects.
• GOOGLE_APPLICATION_JSON - Firebase database to save users
• OKTA_TOKEN - needed to validate user's SSO GUID against.

These should be set in your .env file in the project root.

Schema Setup

Important: Before pulling the schema, the environment variables (PRISMA_API_USERS_URL and PRISMA_API_MEDIA_URL) must point to the production database to pull the schema.

Once the database URLs are configured to point to production, pull the schema using the pull command:

pnpm prisma:pull

After pulling the schema:

• If you want to run the script locally, change the environment variables to point to your container database
• If you want to run scripts against stage or prod, keep the environment variables pointing to the respective production databases

Running the Script

After setting up the environment variables and pulling the schema, you can run the script. The script supports the following commands:

• build-cache - Build document cache by migrating documents from Couchbase
• ingest - Ingest documents from cache into Core

Example usage :

1. Pull the database schema (from production)

First, ensure your .env file has the production database URLs:

• PRISMA_API_USERS_URL → production database
• PRISMA_API_MEDIA_URL → production database

pnpm prisma:pull

2. Configure environment for local development (optional)

If you want to run the script locally, update your .env file to point to your container database:

• PRISMA_API_USERS_URL → local container database
• PRISMA_API_MEDIA_URL → local container database

3. Build the cache

pnpm dev build-cache

4. Ingest into core from cache

pnpm dev ingest --pipeline users
pnpm dev ingest --pipeline playlists
pnpm dev ingest --pipeline all

Note: If you want to run scripts against stage or prod, ensure your environment variables point to the respective production databases in your .env file.

Additional Info.

reset:firebase is used to batch delete firebase users. be warned this is dangerous - only do this in dev environment.

This is becuase the email could be used to login to other Jesus Film Apps, ergo, this should only be used to test scripting in dev environments.