Demo & Seeding¶

Revel includes management commands to populate the database with realistic test data, useful for development, demos, and manual QA.

Commands¶

make bootstrap¶

Runs the bootstrap management command from common/management/commands/bootstrap.py, which orchestrates the full setup:

1. migrate: applies all pending database migrations
2. bootstrap_events: creates the main demo dataset (users, organizations, events, questionnaires, etc.)
3. bootstrap_test_events: creates a third organization with events designed to test every eligibility gate
4. generate_test_jwts: prints JWT access/refresh tokens for the superuser to stdout

make bootstrap

Safe to run multiple times; it checks for existing data.

make seed¶

Runs a separate, large-scale seeder (seed command) that generates a configurable amount of synthetic data for load testing and comprehensive QA. Defaults to --seed 999.

# Default: 1000 users, 20 organizations, 50 events per org
make seed

# Custom scale
uv run python src/manage.py seed --seed 42 --users 500 --organizations 10 --events 25

# Clear all existing data first (destructive!)
uv run python src/manage.py seed --seed 42 --clear

The seed command runs 12 phases: files, users, organizations, venues, events, questionnaires, tickets, interactions, notifications, social, preferences, and Telegram links. It also creates (or verifies) a superuser ([email protected] / password by default; note this differs from make bootstrap which uses [email protected]).

The seed command also supports a --yes flag to skip confirmation prompts, useful for automated scripts:

uv run python src/manage.py seed --seed 42 --yes

bootstrap_perf_tests¶

Creates test data specifically for Locust performance tests:

# Create performance test data
uv run python src/manage.py bootstrap_perf_tests

# Reset and recreate
uv run python src/manage.py bootstrap_perf_tests --reset

make reset-events¶

Runs the reset_events command, which deletes all organizations and all non-@letsrevel.io users, then re-runs bootstrap_events to recreate fresh demo data.

make reset-events

What Gets Created¶

Superuser¶

The bootstrap command creates a superuser if one does not already exist:

Tags (15)¶

A comprehensive tag taxonomy is created, split into two groups:

Category tags (10):

Vibe tags (5):

Users (13 + 4 test users)¶

All users share the password: password123

Main bootstrap users:

Users are assigned random pronouns from a seeded list (he/him, she/her, they/them, he/they, she/they, any pronouns, or none).

Additional test users (from bootstrap_test_events):

The referral rows back the J21 referral-program E2E journeys: bootstrap_test_events also switches SiteSettings.referral_applications_enabled on (so /version reports features.referral_applications: true). Admin decisions (approve / reject / block / invite) exist only in the Django admin, so the decided states are written directly with fixed ids the specs can reference.

The last three back the frontend revival / past-due E2E journeys: EXPIRED and PAST_DUE are only ever produced by Stripe webhooks and the daily events.expire_subscriptions_past_grace sweep, so no API can arrange them. They hang off Org Alpha (the Stripe-connected org) on a dedicated E2E Revival Tier / E2E Revival Plan (€10/month, ONLINE, sales open, uncapped).

10 dummy users ([email protected] through [email protected]) and 5 ticket holders ([email protected] through [email protected]) are also created for capacity testing.

Organizations (3)¶

Revel Events Collective (Alpha)¶

Tech Innovators Network (Beta)¶

Eligibility Test Organization¶

White-label tenant fixtures¶

bootstrap_test_events also seeds three dedicated organizations for the custom-domain E2E journeys (see White-Label architecture). They are separate on purpose: the frontend 301s the platform URL of any organization with an active custom domain, so a domain can never sit on the shared fixtures other journeys visit on the platform host. All are owned by [email protected].

• The two seated events (for anonymous seat-hold and guest-checkout E2E on a custom domain) are public and open to guests. Each has a venue named <Org Name> Hall with one seated sector MAIN ("Main Floor"), three rows A to C of six seats (A1 to C6), and a single tier where guests pick their seats. The free one needs no Stripe; the paid one does.
• *.localhost hostnames are valid only with DEBUG on. Without it the tenant fixtures are skipped with a warning. Run the frontend with PLATFORM_HOSTS=localhost and PUBLIC_CUSTOM_DOMAIN_URL_TEMPLATE=http://{hostname}:5173, and the backend with CUSTOM_DOMAIN_URL_TEMPLATE=http://{hostname}:5173, then open http://tenant.localhost:5173.
• Tenant Paid Org gets the platform's own STRIPE_ACCOUNT when it is a real acct_ id that no other organization holds, so test-mode checkouts work. Otherwise paid checkout on it fails and the seeder logs a warning.

Venues (1)¶

Revel Concert Hall¶

Event Series (2)¶

Events (13 main + 11 test)¶

Main Bootstrap Events¶

Eligibility Test Events¶

These events are all in the Eligibility Test Organization and are designed to test every possible eligibility gate:

Ticket Tiers¶

Sunset Music Festival¶

Exclusive Wine Tasting & Pairing Dinner¶

FutureStack¶

Weekend Wellness Retreat¶

Annual Charity Gala¶

Advanced Machine Learning Workshop¶

Classical Music Evening¶

Platform Billing (SiteSettings)¶

The bootstrap configures platform-level billing on the SiteSettings singleton:

Organization Billing Info¶

Both main organizations are configured with VAT/billing data for testing EU cross-border invoicing:

Revel Events Collective (Alpha)¶

Since the platform is in Italy (IT) and this org is in Austria (AT) with a validated VAT ID, platform fee invoices use reverse charge (B2B EU cross-border).

Tech Innovators Network (Beta)¶

Also reverse charge (DE → IT cross-border with valid VAT ID).

Payments & Invoice¶

The bootstrap creates 4 succeeded payments for the Revel Events Collective from the previous month, then generates a platform fee invoice with PDF:

• Payments are spread across the previous month (one per bootstrap user)
• Each payment includes full VAT breakdowns (ticket sale VAT + platform fee VAT)
• An invoice (RVL-{YEAR}-000001) is generated via generate_invoices_for_period()
• A PDF is rendered via WeasyPrint and attached to the invoice record

This verifies the full billing pipeline end-to-end: VAT calculation → payment recording → invoice aggregation → PDF rendering.

Questionnaires (4 main + 1 test)¶

Main Bootstrap Questionnaires¶

Code of Conduct Agreement. Simple yes/no agreement. Fatal question (wrong answer = automatic fail). Max 3 attempts, requires 100% score.

Wine Tasting Dinner Application. Multi-question application with a conditional question: if the user selects "Advanced" wine knowledge, they get an additional free-text question about their specialization. Max 1 attempt, requires 60% score.

Tech Innovators Network Membership Application. Multi-section questionnaire with conditional questions and conditional sections. Selecting "AI/Machine Learning" reveals a follow-up multi-select about AI areas. Selecting "Blockchain/Web3" reveals an entire section about Web3 experience. Max 2 attempts (can retake after 30 days), requires 70% score.

Event Feedback. Simple post-event feedback with a yes/no question and optional free-text comments. Linked as FEEDBACK type to the past event.

Eligibility Test Questionnaire¶

Simple automatic questionnaire with a fatal yes/no question and a free-text question.

Potluck Items (12)¶

For the Community Potluck & Garden Party:

Host-suggested items (unassigned):

User-contributed items (assigned):

Invitations¶

RSVPs¶

Tickets¶

• Sunset Festival: 4 Early Bird (active), 1 VIP (active), 1 General (pending payment), 1 Early Bird (cancelled/refunded)
• Annual Charity Gala: 2 checked-in tickets (George, Charlie) with succeeded payments
• Wellness Retreat: 1 Shared Room (active, Hannah)
• FutureStack: 1 Member Discount (active, Frank)
• Classical Music Evening: 3 Standing Room (active), 5 Standing Room (pending payment)

Waitlist Entries¶

Follow Relationships¶

Organization members automatically follow their organization via a signal. Additional non-member follows:

Dietary Data¶

Every bootstrap user has dietary preferences and/or food restrictions configured:

Testing Tips¶

Suggested Test Scenarios¶