Deploy and Host Clipline Cloud on Railway

Clipline Cloud is a self-hosted video clip library for the Clipline Windows desktop app. It lets users upload, browse, share, comment on, and embed gameplay clips through a web UI, while keeping storage, accounts, and deployment under the server owner’s control.

About Hosting Clipline Cloud

Hosting Clipline Cloud on Railway runs the web server from the published Docker image, stores metadata in Railway Postgres, and stores uploaded media in an S3-compatible object storage bucket. Cloudflare R2 is the recommended storage backend because it is S3-compatible and has no egress bandwidth charges. Backblaze B2 can also work, but review its download bandwidth and egress model before using it for public video playback. Once deployed, Clipline Cloud exposes a web UI, public clip pages, Discord-friendly embeds, admin controls, user accounts, comments, avatars, and upload support for the Clipline desktop client.

Common Use Cases

Host a private or invite-only clip library for friends, teams, or communities.
Publish a public clip library with share pages, comments, views, and Discord embeds.
Give Clipline desktop users a self-hosted cloud upload target without managing a VPS.

Dependencies for Clipline Cloud Hosting

A Railway account.
A Railway Postgres database.
An S3-compatible object storage bucket, preferably Cloudflare R2.
S3 API credentials with read, write, and list access to the media bucket.
The Clipline Windows desktop app for recording and uploading clips.
Optional: a custom domain for public share links and embeds.

Deployment Dependencies

Clipline Cloud Docker image: ghcr.io/dain98/clipline-cloud:latest
Clipline Cloud repository: https://github.com/dain98/clipline-cloud
Clipline desktop app: https://github.com/dain98/clipline
Cloudflare R2: https://developers.cloudflare.com/r2/
Backblaze B2 S3-compatible API: https://www.backblaze.com/docs/cloud-storage-s3-compatible-api

Implementation Details

Recommended service settings:

Docker image: ghcr.io/dain98/clipline-cloud:latest
Healthcheck path: /readyz
Database: Railway Postgres
Storage backend: S3-compatible object storage

Required user-provided variables:

CLIPLINE_S3_ENDPOINT
CLIPLINE_S3_BUCKET
CLIPLINE_S3_ACCESS_KEY_ID
CLIPLINE_S3_SECRET_ACCESS_KEY

Recommended preconfigured variables:

CLIPLINE_PUBLIC_URL=https://${{RAILWAY_PUBLIC_DOMAIN}}
CLIPLINE_DATABASE_URL=${{Postgres.DATABASE_URL}}
CLIPLINE_STORAGE_BACKEND=s3
CLIPLINE_S3_REGION=auto
CLIPLINE_S3_FORCE_PATH_STYLE=true
CLIPLINE_DIRECT_S3_UPLOADS=false
CLIPLINE_PUBLIC_MEDIA_MODE=presigned
CLIPLINE_BOOTSTRAP_ADMIN_USERNAME=admin
CLIPLINE_SESSION_SECRET=${{secret(64)}}
CLIPLINE_LOG_LEVEL=info

Do not set CLIPLINE_BIND_ADDR on Railway. Clipline Cloud will bind to Railway’s injected PORT.

Why Deploy Clipline Cloud on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Clipline Cloud on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.