---
title: "Deploy Chibisafe"
description: "File and image sharing with a web dashboard and persistent upload storage."
category: "Storage"
url: https://railway.com/deploy/chibisafe
---

# Deploy Chibisafe

File and image sharing with a web dashboard and persistent upload storage.

**[Deploy Chibisafe on Railway](https://railway.com/template/chibisafe)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/chibisafe/manifest.json

- **Creator:** orenaksakal
- **Category:** Storage

## Template content

### web

- **Image:** chibisafe/chibisafe:v6.5.5@sha256:836467a50792b08c29d90e32447a1480208723751e8a0f7ecd7ede17fe393ea3

### chibisafe

- **Source:** orenaksakal/railway-templates
- **Health check:** /healthz
- **Public domain:** Yes

## Documentation

# Deploy and Host Chibisafe

File and image sharing with a web dashboard and persistent upload storage.

## About Hosting

| Service | Access | Persistent storage |
| --- | --- | --- |
| web | Private | None |
| chibisafe | Public HTTPS | /data |

Railway provides the public HTTPS endpoint. Dependencies stay on private networking. Keep each volume-backed service at one replica.

## Why Deploy Chibisafe on Railway

This definition includes pinned container sources, documented storage paths and generated credentials where required. It restores the missing repository adapters from the previous draft and keeps the application setup steps explicit.

## Common Use Cases

File and image sharing with a web dashboard and persistent upload storage.

## First use

No mandatory operator-supplied variables. Retrieve generated credentials from the service variables.

No mandatory operator-supplied variables. Generated credentials are available in service variables after deployment.

Open the chibisafe public domain. Log in as admin with ADMIN_PASSWORD from its variables. Configure the public service URL and registration policy in the dashboard, then create your uploader API key. The web frontend uses the private backend on port 8000.

Where an owner gateway is included, the username is admin. API clients can use `X-Template-Key: YOUR_ACCESS_PASSWORD`. The gateway consumes Basic Authorization, preserves Bearer authorization and WebSocket upgrades, and caps requests at 32 MiB; check compatibility with native clients. Generated credentials must remain private.

## Scope and limitations

The adapter supervises the backend and Caddy together with a single /data volume for database, uploads and logs. Sharing URLs intentionally serve files publicly, following the upstream topology; restrict uploads through native application accounts and review registration settings. S3 and CDN integrations are not configured. /healthz measures Caddy readiness only.

Source and static configuration checks are recorded in the repository's release report. Container builds, fresh Railway startup, native-client compatibility, full application workflows, backup restoration and costs have not been verified. A proxy healthcheck is not application readiness.

## Acceptance checks

Log in with the generated password, upload an image through the UI and API, retrieve its sharing URL, delete it, restart, and verify both database records and remaining file bytes.

Verify first use, unauthorized rejection where applicable, and a volume-preserving redeploy. Back up every persistent volume, generated application key and consistent database export. Restore into a separate instance and verify accounts, records and uploaded bytes before using important data. Container rollback does not revert database migrations.

## Dependencies for Chibisafe

### Deployment Dependencies

A Railway account with capacity for 2 services, access to the selected registries and repository source, and the inputs listed above. External provider accounts and optional integrations are operator-supplied.

### Source and maintenance

- [Upstream project](https://github.com/chibisafe/chibisafe)
- [Reviewed application source](https://github.com/chibisafe/chibisafe/tree/3e050cb581512665ec912b038ed24388625f9994)
- [Deployment adapter](https://github.com/orenaksakal/railway-templates/tree/codex/unique-template-drafts/templates/round9/chibisafe)
- Repository services build from `orenaksakal/railway-templates`, branch `codex/unique-template-drafts`, with repository-root build context. Keep the branch available.
- Image digests and source references are tracked separately. A source revision is not asserted to match a rolling image unless the image metadata establishes it.

Upstream software retains its own license and trademarks. This community integration does not imply endorsement.


## Similar templates

- [Garage S3 Storage](https://railway.com/deploy/garage-s3-storage) — Ultra-light S3 server: fast, open-source, plug-and-play.
- [Redis](https://railway.com/deploy/redis-1) — Self Host Latest Redis with Railway
- [Plik File Sharing](https://railway.com/deploy/plik-file-sharing) — Expiring file sharing with authenticated uploads and persistent metadata.

Open this page in a browser: https://railway.com/deploy/chibisafe