Deployment Environments

The Liana Banyan Platform uses three distinct deployment environments, each serving a specific purpose.

Overview

EnvironmentPurposeAudience
TemplateReference implementation for copyingDevelopers, aspiring Dukes
StagingTesting before productionInternal team
ProductionLive platformMembers, public

Template Environment

What it is: A clean, forkable codebase hosted on Lovable.dev.

Purpose:

  • Reference implementation for new MimicTrunks
  • Developer playground for experimentation
  • Training ground for learning the architecture

Who uses it:

  • Aspiring Dukes launching their own MimicTrunk
  • Developers building new features
  • Anyone wanting to understand how the platform works

Key point: This is a template, not the live platform. Fork it, modify it, make it your own.


Staging Environment

What it is: A pre-production testing environment.

Purpose:

  • Test changes before they go live
  • QA verification
  • Preview new features for stakeholders

Who uses it:

  • Internal development team
  • QA testers
  • Leadership reviewing new features

Key point: What works in staging gets promoted to production.


Production Environment

What it is: The live platform serving real users.

URLs:

  • Main platform: lianabanyan-main.web.app
  • Business module: lianabanyan-biz-trunk.web.app
  • Nonprofit module: lianabanyan-org-trunk.web.app
  • Network module: lianabanyan-net-trunk.web.app
  • HexIsle: hexisle.web.app
  • Documentation: the2ndsecond.com
  • Rally Group: therallygroup.web.app

Who uses it:

  • Members (Ghost through Crown)
  • The 300 Harbor Masters
  • Initiative Crowns
  • General public

Key point: Real users, real data, real consequences. Changes are tested thoroughly before deployment.


The Flow

Development → Template (Lovable) → Staging → Production
  1. Develop locally or in the template environment
  2. Validate using the template’s preview
  3. Test in staging with real-ish scenarios
  4. Deploy to production after approval

For Aspiring Dukes

If you’re launching a MimicTrunk, start with the Template:

  1. Fork the template repository
  2. Customize for your business
  3. Follow the DNA Rules
  4. Deploy your own instance

The template gives you a working foundation that follows all platform standards.


Questions about deployment? The template repository includes detailed setup instructions.