Skip to content

Render

Deploy to Render

The button reads the source repository’s render.yaml: a web service running ghcr.io/pwnera/artbucket:1 and a Render Postgres, both in Frankfurt. BETTER_AUTH_SECRET and SETUP_TOKEN are generated and DATABASE_URL wired in.

Render has no object storage, so bring an S3-compatible bucket: Cloudflare R2, AWS S3, Backblaze B2. Render asks for it when the Blueprint is created:

Variable Example
APP_URL https://artbucket.onrender.com, or your own domain
S3_ENDPOINT https://<account>.r2.cloudflarestorage.com
S3_REGION auto for R2, the bucket’s region elsewhere
S3_BUCKET acme-assets
S3_ACCESS_KEY_ID …
S3_SECRET_ACCESS_KEY …

APP_URL is the service’s address, https://<service name>.onrender.com (Render shows it once the service exists: change the variable if it differs), or your own domain once it is added under Settings, Custom Domains.

Browsers upload to the bucket directly. The server sets the bucket’s CORS rule and lifecycle on start; with a key that can’t (R2’s object tokens), set them in the provider’s console, as Storage says.

The service migrates its database on start and answers once it has. Make the first account at APP_URL, right away: the address is public, and that account is the admin of everything. The form asks for the setup token, SETUP_TOKEN under the service’s Environment, so nobody who finds the address first can. Every other variable is in Environment: add it under the service’s Environment.

The Blueprint picks the standard instance (2 GB: uploads are buffered while previews are made) and a basic-256mb Postgres, in Frankfurt. For another region or size, fork the repository, edit render.yaml, and deploy the fork: https://render.com/deploy?repo=<your fork>.

The image follows the major line (:1). Manual Deploy, then Deploy latest reference, pulls the newest 1.x; to pin one, set the image to ghcr.io/pwnera/artbucket:<version> under Settings, a tag the registry lists, such as 1.8.1.