Deploy Slink
Self-hosted image sharing service.
Just deployed
/app
Deploy and Host Slink on Railway
About Hosting Slink
Self-hosted image sharing with a small Railway volume-initialization adapter, pinned to Slink v1.14.6. The image and adapter source are pinned; the existing single-service topology and persistent data paths are retained.
Common Use Cases
Private image uploads and small-team image sharing using one persistent single-instance service.
Dependencies for Slink Hosting
Deployment Dependencies
One Slink service, public port 3000, /api/health, and a persistent volume mounted at /app. The bundled application uses SQLite read/event databases and local files; no separate database service is provisioned.
Implementation Details
Keep /app/var/data/slink.db, /app/var/data/slink_store.db, keys and /app/slink together. Configure ADMIN_EMAIL, ADMIN_USERNAME and a strong ADMIN_PASSWORD; log in as that administrator. Preserve IMAGE_MAX_SIZE=15M, ORIGIN=https://${{RAILWAY_PUBLIC_DOMAIN}}, PORT=3000, STORAGE_PROVIDER=local, TZ=UTC and USER_APPROVAL_REQUIRED=false unless deliberately changing policy. Secrets belong in Railway variables, not GitHub. Review public signup before exposing the service.
The root adapter rejects symlink/non-directory storage paths, creates only missing images/cache/chunks directories and delegates ownership and startup to upstream. It does not migrate paths or seed databases. The original published image's empty-volume upload fails HTTP 500; a separately disclosed legacy-initialized upgrade is not an original fresh-install success. For manual maintenance initialization and backup guidance see README.md. Never delete or reseed existing records to make an upgrade pass.
Why Deploy Slink on Railway?
Managed HTTPS and a persistent volume simplify a small single-instance installation. This topology is not HA, multi-replica, external object storage or zero-downtime. Keep consistent full-volume backups; image-internal paths outside /app remain ephemeral. Upgrades need original user/image/metadata persistence checks. AGPL-3.0, upstream Andrii Kryvoviaz and contributors: https://github.com/andrii-kryvoviaz/slink .
Template Content
ADMIN_EMAIL
Administrator email to use to login.
