Migration Guide: Environment Variables in v0.1.62

Release v0.1.62 is a breaking configuration change. The application no longer reads any of the original VUE_APP_* Amplify variables or the Lambda-level API_KEY. If you are upgrading from an earlier version you must update your deployment environment before the new build will start correctly.

Why This Changed

Area	Old approach	New approach
LettMC API key	Hardcoded in getEnvironmentConfig.js / API_KEY Lambda var	LETMC_API_KEY env var read from src/lib/letmc/config.ts
Authentication	AWS Cognito Amplify (Vue SDK)	NextAuth.js with Cognito OIDC provider
Session storage	Amplify-managed	Drizzle ORM on Postgres (DATABASE_URL)

Variables You Must Remove

These are no longer read and should be cleaned out of your environment to avoid confusion:

API_KEY
VUE_APP_AWS_USER_POOLS_ID
VUE_APP_AWS_USER_POOLS_WEB_CLIENT_ID
VUE_APP_AWS_COGNITO_IDENTITY_POOL_ID

Variables You Must Add

LettMC API

Variable	Required	Notes
LETMC_API_KEY	Yes	Your LettMC API key. Replaces the hardcoded values and the old API_KEY Lambda variable.
LETMC_API_BASE_URL	No	Defaults to https://live-api.letmc.com if omitted.

Cognito OIDC (NextAuth)

Variable	Required	Value
COGNITO_USER_POOL_ID	Yes	eu-west-2_NOGEI9Qdo
COGNITO_CLIENT_ID	Yes	j2nunff7hd0p2tbcc42p8eurt (web) · 4tns2b4j7n6lsasd9gj2ean8fs (native)
COGNITO_CLIENT_SECRET	Yes	Obtain from the AWS Cognito console for your app client.
COGNITO_REGION	Yes	eu-west-2

NextAuth Core

Variable	Required	Notes
NEXTAUTH_SECRET	Yes	A random string used to sign session tokens. Generate with openssl rand -base64 32.
NEXTAUTH_URL	Yes	The canonical URL of the deployed portal, e.g. https://portal.youragency.com.

Database

Variable	Required	Notes
DATABASE_URL	Yes	Postgres connection string used by the NextAuth Drizzle adapter for session storage. Example: postgresql://user:password@host:5432/dbname

Step-by-Step Checklist

• Remove API_KEY, VUE_APP_AWS_USER_POOLS_ID, VUE_APP_AWS_USER_POOLS_WEB_CLIENT_ID, and VUE_APP_AWS_COGNITO_IDENTITY_POOL_ID from your environment.
• Add LETMC_API_KEY with your LettMC API key.
• Add COGNITO_USER_POOL_ID, COGNITO_CLIENT_ID, COGNITO_CLIENT_SECRET, and COGNITO_REGION.
• Provision a Postgres database and add DATABASE_URL.
• Generate and add NEXTAUTH_SECRET.
• Set NEXTAUTH_URL to your portal's public URL.
• (Optional) Set LETMC_API_BASE_URL if you target a non-production LettMC endpoint.
• Deploy the v0.1.62 build.

Obtaining the Cognito Client Secret

1. Open the AWS Console and navigate to User Pools.
2. Select the pool eu-west-2_NOGEI9Qdo.
3. Go to App clients and click on the relevant client.
4. Reveal or rotate the App client secret and copy the value into COGNITO_CLIENT_SECRET.

Generating a Postgres Connection String

If you are using a managed Postgres provider (e.g. AWS RDS, Supabase, Neon), copy the connection string from the provider dashboard. It follows the format:

postgresql://<user>:<password>@<host>:<port>/<database>

Ensure the database is reachable from your deployment environment and that the user has permission to create tables (Drizzle will run migrations on startup).