Skip to main content

Marquees

A Marquee is a Docker host registered with Fibe. It runs Playgrounds and Tricks within its capacity and handles TLS, routing, registry credentials, and SSH.

Runtime actions and Genie messages require a funded Marquee. An unpaid Marquee returns MARQUEE_NOT_FUNDED, while Billing remains available so you can restore service.

What a Marquee gives you​

CapabilityDetail
Docker executionCompose files run as containers on the host. Fibe drives Docker; you don't.
Public routing (HTTPS)external services get a URL under your root domain. TLS terminates at the Marquee.
Internal routinginternal services share the URL shape but sit behind Basic Auth.
DNS at the root domainPoint a wildcard at the Marquee. Every service gets a subdomain.
Docker Hub credentialsAdd once. Every Playground pulling private Docker Hub images can use them. Other registries (GHCR, Amazon ECR) are configured per Template.
SSH terminalOpen from the Marquee page. Inspect disk, containers, the Docker daemon.
CapacityMany environments side-by-side. Limit is host CPU/memory.

Add a Marquee​

Connect any Docker-capable host reachable over SSH, or use a managed tutorial Marquee to start without infrastructure.

You supply:

  • SSH details: address, user, and key. Port 22 is the default. The host needs running Docker and a public address; private, loopback, and duplicate host-port pairs are rejected.
  • Root domain: every service becomes <subdomain>.<root-domain>. Requires a wildcard DNS record.
  • TLS: automatic Let's Encrypt or your own certificate and private key. Automatic wildcard certificates support Cloudflare, AWS Route53, DigitalOcean, Hetzner, OVH, Google Cloud DNS, and manual acme-dns CNAME verification.
  • Optional Docker Hub credentials: for pulling private Docker Hub images. Credentials for other registries (GHCR, Amazon ECR) are added on the Template that uses them, not on the Marquee.
Tutorial Marquees

A Tutorial bundle provisions a managed host without requiring your own infrastructure.

Marquee types​

Marquees are self-hosted or platform-managed tutorial hosts. Billing bundles differ by funded Marquee count and duration, not features.

Tutorial hosts show each provisioning stage from Queued through Ready. SSH works after Ssh Configured; a 30-minute stall fails provisioning. Fibe manages immutable connection details and HTTPS certificates. Two rate-limited recovery actions are available:

ActionAvailableLimit
Fix-redeployOnce provisioning has finished or failed; not while a Genie chat is live10 attempts per 4-hour window
RebootOnce provisioned: including from error status3 reboots per 1-hour window

Both counters reset when their window expires.

Routing & URLs​

Two URL kinds per service:

  • Public (fibe.gg/visibility: external with fibe.gg/port: PORT): https://<subdomain>.<root-domain>. Anyone with the URL reaches it.
  • Internal (fibe.gg/visibility: internal with fibe.gg/port: PORT): same shape, Basic Auth in front.

Routing is opted in per service with fibe.gg/port; pick public vs. internal per service with fibe.gg/visibility (defaults to external). Container ports are not published manually. Fibe handles binding, certificates, the proxy.

services:
  web:
    image: nginx:alpine
    labels:
      fibe.gg/port: 80
      fibe.gg/visibility: external
  admin:
    image: my-org/admin:1.0
    labels:
      fibe.gg/port: 8080
      fibe.gg/visibility: internal

The subdomain defaults to the service name. Override it with lowercase letters, digits, hyphens, or @ for the root domain. See Service labels → Routing & exposure.

Health & capacity​

The Marquee page shows:

  • Live status: reachability, Docker daemon, service health.
  • Capacity: running Playgrounds, CPU/memory usage.
  • Schedule: Playgrounds and Tricks running here.
  • SSH terminal.
  • Connection test: re-runs the check. Surfaces firewall, key, disk problems.

Connection tests and live diagnostics also require a funded Marquee because they contact the remote host.

A Marquee is active, disabled, or in error. Launches require an active, funded Marquee with SSH details, a root domain, and completed tutorial provisioning. Other runtime actions have the same active and funded requirements.

Disable a Marquee for maintenance. Existing Playgrounds continue, new launches stop, and live Genie chats pause without losing data. Nonpayment blocks every runtime action; managed Playgrounds become unfunded and live chats stop. See Billing → When your balance runs low.

Removing a Marquee​

Stop or move attached Playgrounds and Tricks first. The product lists what's attached.

Decommission flow:

  1. Disable the Marquee.
  2. Stop or destroy obsolete Playgrounds.
  3. Relaunch long-running Playgrounds from the same Template on another Marquee. Existing Playgrounds cannot move between hosts.
  4. Delete the Marquee. The host machine is untouched.

Example: connect a DigitalOcean droplet​

  1. Ubuntu droplet, 2 vCPU / 4 GB RAM minimum, with Docker installed and the needed ports open (SSH, 80/443).
  2. Wildcard DNS *.dev.example.com → <droplet IP>.
  3. Add Marquee in Fibe with:
    • Host: dev.example.com
    • SSH user, SSH key.
    • Root domain: dev.example.com.
    • TLS: automatic, with DigitalOcean as the DNS provider (an API token).
  4. Test connection. Fibe verifies SSH access, that Docker is installed and running, and that its working directories are writable.
  5. Marquee ready. Launch a Playground.

FAQ​

How many Marquees can I have?

Standard and tutorial Marquees have separate account quotas. Wallet credit funds existing Marquees but does not raise those quotas.

Move a running Playground to a different Marquee?

No. A Playground stays on the Marquee it was created on. To change hosts, launch a fresh Playground from the same Template on the other Marquee and retire the old one.

Can two people share a Marquee?

Yes, through a team. An owner can grant accepted members manage access from the team page. Members can select the Marquee for Playgrounds, templates, CI, and schedules, and can manage its Playgrounds.

Ownership and billing stay with the owner. An unfunded Marquee blocks everyone. Other resources remain private, access is manage-only, and team management is available only in the web UI.

When sharing ends, your Playgrounds on that Marquee are destroyed and its Genie chats stop. Move needed work first.

Host goes down?

Connection check flips the Marquee to error. Playgrounds become unreachable until the host returns, and live Genie chats stop automatically with a message that the Marquee became unavailable (their data is kept). No automatic failover.

Does the Marquee see my source?

Source-mounted templates clone the repository with Prop credentials. Image-only templates expose the image, not raw source. Mounted source remains for the Playground's lifetime.

Last updated on