A production-ready monorepo template for building applications with MemberJunction.
When you create an environment through MJ Central, provisioning happens automatically:
- GitHub Repository
- Git Branches - One per environment (dev, stage, prod, or custom names)
- Azure Resources - App Service, Static Web App, SQL Database
- GitHub Secrets & Variables - Configured per environment
- Workflows - Triggered automatically to deploy your environment
- mj-setup - Initializes database schema and generates code
- explorer - Deploys the Angular admin UI (runs after mj-setup succeeds)
- api - Deploys the GraphQL API server (runs after mj-setup succeeds)
If all workflows succeed:
- Environment status shows Running in MJ Central
- You'll receive a confirmation email
- Your apps are live and accessible
If any workflow fails:
- Go to GitHub Actions in your repository
- Check the failed workflow logs for details
- Try clicking Re-run jobs to retry
- Still failing? Contact help@memberjunction.com
- MJ API (
apps/MJAPI) - GraphQL API server - MJ Explorer (
apps/MJExplorer) - Angular admin UI - Generated Entities (
packages/GeneratedEntities) - Auto-generated TypeScript entities - Generated Actions (
packages/GeneratedActions) - Auto-generated business logic - SQL Migrations (
SQL Scripts/migrations/) - Database migration structure
See the Local Development Guide for running this project locally.
- Issues: help@memberjunction.com
- Documentation: docs.memberjunction.org