Tickets Setup Guide

Tickets is a simple event ticketing system. This guide will help you get it running on your own domain.

Which applies to you?

Your Configuration

No configuration found. If you're a Chobble customer, you should have received a link with your configuration included. Please check the link you were given.

Step 1: Generate Your Encryption Key

Click the button below to generate a secure encryption key. This key encrypts sensitive data in your database.

Step 2: Fork the Repository

1 Go to github.com/chobbledotcom/tickets/fork

2 Click "Create fork"

(You'll need a GitHub account - it's free to create one)

Step 3: Add Your Secrets

In your forked repository:

1 Go to Settings (tab at the top)

2 Click Secrets and variables in the left sidebar

3 Click Actions

4 For each secret below, click "New repository secret"

Step 4: Deploy

1 Go to the Actions tab

2 Click "I understand my workflows, go ahead and enable them"

3 Click Deploy in the left sidebar

4 Click "Run workflow" button on the right

5 Click the green "Run workflow" button

That's it! Once the workflow completes (usually under a minute), your ticketing system will be live at your domain. Visit it to complete the initial setup.

Self-Hosting Requirements

You'll need to set up these services yourself:

Step 1: Create Your Database

1 Sign up at turso.tech

2 Create a new database

3 Copy your database URL (looks like libsql://your-db.turso.io)

4 Create an auth token and copy it

Step 2: Set Up Bunny Edge Scripting

1 In your Bunny dashboard, go to Edge Scripting

2 Create a new script

3 Note your Script ID (from the URL)

4 Create an API key with deploy permissions

5 Set up your domain to point to this script

Step 3: Generate Your Encryption Key

Step 4: Fork and Configure

1 Fork github.com/chobbledotcom/tickets

2 Go to Settings → Secrets and variables → Actions

3 Add these secrets:

ALLOWED_DOMAIN

Your domain (e.g., tickets.example.com)

DB_URL

Your Turso database URL

DB_TOKEN

Your Turso auth token

DB_ENCRYPTION_KEY

The key you generated above

BUNNY_SCRIPT_ID

Your Bunny Edge Script ID

BUNNY_SCRIPT_KEY

Your Bunny API key

Step 5: Deploy

1 Go to Actions tab → Enable workflows

2 Click Deploy → Run workflow

Once deployed, visit your domain to complete the initial setup (admin password, optional Stripe configuration, etc).

Generate Customer Setup Link

Fill in the customer's configuration, then share the generated link.

What happens: The customer opens this link, generates their own encryption key (which you'll never see), adds all the secrets to their GitHub fork, and deploys. You can then use the DB credentials to access their data - but anything encrypted will be unreadable without their key.