MeetingBaas
Concepts

Environment Variables

Configuring Environment Variables for Transcript Seeker.

Let's learn how to configure environment variables for Transcript Seeker. Transcript Seeker uses dotenv-cli to load the environment variables, making it easy for development. Transcript Seeker follows this structure for different environments:

  • .env.development.local for development
  • .env.production.local for production

You can load a specific environment file by running the following command:

Terminal
export NODE_ENV="development"

Now, let's configure the environment variables.

Client

Create a .env.development.local file in the below directory of your project and add the following environment variables:

.env.development.local
package.json

Vite Port Configuration

These values are used by vite to configure the url the server listens on.

.env.development.local
VITE_CLIENT_PORT=5173
VITE_CLIENT_HOST=0.0.0.0

Proxy Configuration

This Proxy URL is used to forward requests from the client to the respective server, helping to avoid client-side CORS errors. An example proxy server is provided in the repository.

.env.development.local
VITE_PROXY_URL=http://localhost:3000

API Configuration

This API URL is used by the calendars functionality of Transcript Seeker. It allows the app to perform authentication and retrieve the user's calendar data.

.env.development.local
VITE_API_URL=http://localhost:3001

S3 Configuration

This environment variable is used to indicate to the client where the video recordings are stored.

.env.development.local
VITE_S3_PREFIX=https://s3.eu-west-3.amazonaws.com/meeting-baas-video

Proxy

Create a .env.development.local file in the below directory of your project and add the following environment variables:

...
.env.development.local
.env.development.local
package.json

MeetingBaas Proxy Configuration

These values are used by the api to figure out the api url for baas servers.

.env.development.local
MEETINGBAAS_API_URL="https://api.meetingbaas.com"
MEETINGBAAS_S3_URL="https://s3.eu-west-3.amazonaws.com/meeting-baas-video"

API

Create a .env.development.local file in the below directory of your project and add the following environment variables:

...
.env.development.local
.env.development.local
package.json

MeetingBaas Configuration

These values are used by the api to figure out the api url for baas servers.

.env.development.local
NITRO_MEETINGBAAS_API_URL="https://api.meetingbaas.com"
NITRO_MEETINGBAAS_S3_URL="https://s3.eu-west-3.amazonaws.com/meeting-baas-video"
NITRO_TRUSTED_ORIGINS="http://localhost:5173" # comma separated list of trusted origins

Google Authentication Configuration

These values are used by the api to perform google authentication. Please follow the guide for more details:

.env.development.local
GOOGLE_CLIENT_ID=""
GOOGLE_CLIENT_SECRET=""

Turso Database Configuration

These values are used by the api to store user autehtncation data. Please follow the guide for more details:

.env.development.local
TURSO_DATABASE_URL=""
TURSO_AUTH_TOKEN=""

Authentication Configuration

When deploying to Google Cloud Run with a custom domain, you should set the BETTER_AUTH_URL environment variable to the custom domain.

These values are used by the api to perform authentication. Please follow the guide for more details:

.env.development.local
BETTER_AUTH_SECRET=""
BETTER_AUTH_URL="http://localhost:3001"
API_TRUSTED_ORIGINS="http://localhost:5173"

The API_TRUSTED_ORIGINS is not only used for authentication but also for CORS configuration.

Edit on GitHub

Previous

Architecture

Next

Authentication

On this page