Deploy Picsur

Deploy and Host Picsur on Railway

What is Picsur?

Picsur is an open-source image-sharing service for uploading, viewing, editing, converting, and expiring images. It supports anonymous uploads, user accounts, roles and permissions, common image formats, shareable previews, and a ShareX endpoint in a browser-based alternative to hosted image-sharing platforms.

About Hosting Picsur

This community template runs Picsur 0.5.6 with PostgreSQL 17.4. Picsur is the only public service: Railway terminates HTTPS and routes traffic to port 8080, while database traffic remains on Railway's private network. Railway checks / before marking the application healthy. PostgreSQL stores uploaded images and application metadata on a persistent volume mounted at /var/lib/postgresql. Required database settings use service references, and the database and administrator passwords use deployment-time generators, so no credential input or value is included in this overview. Upstream labels Picsur as beta and currently states that the project is not maintained; assess that status before using it for public or production workloads.

Common Use Cases

• Host images and generate links or previews for sharing.
• Upload screenshots from ShareX to infrastructure you control.
• Convert, resize, rotate, or otherwise edit supported image formats.
• Run a private image-sharing service with accounts, roles, and permissions.

Dependencies for Picsur Hosting

• Picsur 0.5.6, pinned to the official GHCR image digest.
• PostgreSQL 17.4 for images, users, settings, and other application data.
• One Railway persistent volume mounted at /var/lib/postgresql.

Deployment Dependencies

• Picsur 0.5.6 source
• Picsur self-hosting guide
• Picsur container package
• Official PostgreSQL container documentation
• Railway volume guidance

Implementation Details

The template pins ghcr.io/caramelfur/picsur:0.5.6@sha256:209ce21d338cd7d9a1adc838a67695e903149359bf192359819607df1b3c4417 and postgres:17.4@sha256:fe3f571d128e8efadcd8b2fde0e2b73ebab6dbec33f6bfe69d98c682c7d8f7bd. Picsur listens on public port 8080, and Railway probes GET /. The PostgreSQL service has no public domain.

Picsur's database host, name, username, and password settings reference the PostgreSQL service. Railway generates the PostgreSQL and Picsur administrator passwords for each deployment, while fixed non-secret application and database settings are prefilled. Every required variable therefore has a reference, generator, or non-secret default without copying credentials from the source project. Picsur runs its database migrations automatically at startup.

All durable Picsur content, including uploaded images, is stored in PostgreSQL. Back up the database volume before upgrading, review the upstream changes, and test a new immutable image digest against a restored copy in an isolated project. Because startup may apply database migrations, roll back the prior Picsur image and its matching PostgreSQL backup together if a migration is not backward compatible. A redeploy without a database backup is not a rollback plan.

This community template is maintained independently and does not imply affiliation with or endorsement by Picsur.

Why Deploy Picsur 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 Picsur 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.