ByteBite Docs
Deployment

Deployment Overview

Deployment targets and runtime strategy for ByteBite.

Deployment Overview

ByteBite services are containerized and deployed via Dokploy on BYTEBITE-APP-01. Traefik handles edge routing and TLS; Cloudflare is the DNS provider.

GitHub (main) -> Dokploy -> compose.deploy.yml -> containers -> Traefik -> Internet

Full infrastructure documentation: Infrastructure overview.

Environments

EnvironmentStatusGuideCompose
Local devActiveLocal deploymentcompose.yml + compose.dev.yml
StagingActiveStaging deploymentcompose.deploy.yml
ProductionNot deployedProduction deploymentcompose.deploy.yml (planned)

See Environments for a full comparison.

Production-style runtimes

Staging and production use the same deployment compose pattern:

AppBuildRuntimePort
APItsup bundlenode server.js3001
Storefrontnext buildNext.js standalone3000
Dashboardvite buildnginx static8080
Docsnext buildNext.js standalone3002

Local development uses dev servers via compose.dev.yml.

What the repository provides

  • Multi-stage Dockerfiles under infrastructure/docker/ (dev and prod targets)
  • compose.deploy.yml for Dokploy (api, storefront, dashboard, docs only)
  • Bundled DB tooling in the API image (node db/dist/migrate.js, node db/dist/seed-staging.js)
  • Local Traefik routing: infrastructure/traefik/dev/dynamic.yml
  • infrastructure/dokploy/README.md quick reference

What is managed outside the repository

ComponentManaged by
PostgreSQL (staging)Dokploy
Traefik (dokploy-traefik)Dokploy + host-level config
TLS / ACMETraefik (HTTP-01 + DNS-01)
Explicit domain routingDokploy UI
Wildcard tenant routingcompose.deploy.yml Traefik labels
SecretsDokploy env + host filesystem
DNSCloudflare

Dependency Policy

How ByteBite manages dependency versions at bootstrap stage.

Local Deployment

Docker-based local development infrastructure and setup.

On this page

Deployment OverviewEnvironmentsProduction-style runtimesWhat the repository providesWhat is managed outside the repositoryRelated