tribe/tribe

Tribe is a project management framework by Wildfire.

v3.1.9 2025-06-30 13:02 UTC

Requires

• php: ^8.0
• agence104/livekit-server-sdk: 1.1
• alsvanzelf/jsonapi: ^2.4
• guzzlehttp/guzzle: ^7.7
• phpmailer/phpmailer: ^6.7
• pusher/pusher-php-server: ^7.2
• tribe/core: ^4.0
• vlucas/phpdotenv: ^5.2

GPL-3.0-or-later

README

A web project management framework for building platforms, products and web interfaces using a modular approach.

Visit https://tribe-framework.org

Quick Start

# 1. Configure
cp .env.sample .env
# Edit .env — set passwords, PROJECT_NAME, BARE_URL

# 2. Start
docker compose up -d

That's it. Tribe is running at http://localhost:12000.

Default Ports

Service	Port
Tribe	12000
phpMyAdmin	12001
Junction	12002
Dist (static)	12003
Dist (PHP)	12004
FileBrowser	12005

All ports are configurable in .env.

CLI

docker compose up -d       # start
docker compose down        # stop
docker compose logs -f     # tail logs

Tribe — Advanced Reference

Glossary

Term	Definition
Tribe	PHP content/app framework — core backend and UI engine
Junction	CMS layer connecting to Tribe via API
Docker	Containerisation platform; docker-compose.yml defines all services
.env	Environment file holding secrets and config
MySQL	Relational database storing all Tribe content and data
phpMyAdmin	Web UI for browsing and managing MySQL databases
Caddy	Web server / reverse proxy — handles HTTP, routes to PHP-FPM
FileBrowser	Web UI for browsing and managing uploaded files
Loom	Multi-tenant mode — one shared infrastructure hosting many Threads
Thread	A single Tribe + Junction instance inside a Loom setup
Tor	Overlay mode routing all traffic through .onion hidden services

Full Folder Structure

applications/          # App code
  tribe/               # Tribe PHP application
  junction/            # Junction frontend (dist/)

config/                # Service configuration
  mysql/               # my.cnf, install.sql
  tribe/               # Caddyfile, supervisord.conf, watcher.sh, indexer scripts
  junction/            # Caddyfile
  dist/                # Caddyfile (static site)
  dist-php/            # Caddyfile (PHP site)
  tor/                 # Tor daemon config and helpers
    README.tor.md      # ← Tor setup guide
    docker-compose.tor.yml
    .env.tor.sample
    torrc
    tor-addresses.sh

uploads/               # All runtime data (gitignored)
  sites/
    dist/              # Static site files
    dist-php/          # PHP site files
  threads/             # Per-thread uploads (Loom mode)
  filebrowser/         # FileBrowser database
  tor/                 # .onion keys and hostnames

logs/                  # Runtime logs (gitignored)
  threads/             # Per-thread logs (Loom mode)

threads/               # Generated thread configs (Loom mode)
  .registry.json
  <name>/
    docker-compose.yml
    .env
    config/

docker-compose.yml     # Standard single-project setup
.env.sample            # Standard env template

Advanced Modes

Loom — Multi-tenant hosting

Loom lets you run hundreds of isolated Tribe + Junction instances (Threads) on one shared set of services (MySQL, Caddy, phpMyAdmin, FileBrowser).

To use Loom:

# Manage Threads with loom.sh
node loom create <name>    # provision and start a new Thread
node loom list             # list all Threads with ports and status
node loom destroy <name>   # stop containers and drop DB

Tor — Anonymous hidden services

Tor mode layers docker-compose.tor.yml on top of the standard setup. All ports are removed from the host; services are reachable only via .onion addresses.

To use Tor:

# 1. Copy files to project root
mv config/tor/docker-compose.tor.yml .
mv config/tor/.env.tor.sample .

# 2. Follow the guide
# config/tor/README.tor.md

→ Full instructions: config/tor/README.tor.md

License

GNU General Public License — free, copyleft.