Deploy Gianki Server
Run Gianki Team Chat on railway.
gianki-server
Just deployed
/data
Deploy and Host Gianki Server on Railway
Gianki is private team chat on a server of your own: channels, direct messages, threads, reactions, file sharing and search, with native apps for Mac, iPhone, iPad and Android and a web app. One deployment serves one team, and its messages stay in that deployment's volume and nowhere else.
About Hosting Gianki Server
Gianki Server is a single container with a single volume. The server holds accounts and settings in SQLite and messages in files beside it, all in the volume
at /data, so there is no separate database or cache to run. Railway provides the HTTPS address the apps connect to. The first start creates your team and
its first administrator; after that you invite people from the browser-based admin console. Hosting it means keeping the volume large enough for your team's
uploads, using the volume's backups, and deploying a newer image when one is published. A redeployment is a short interruption, and the apps reconnect on
their own.
Common Use Cases
- A company or team that wants its chat on infrastructure it controls
- A community, club or project that wants its own chat space, with sign-up by invitation or registration code
- Trying Gianki with a few people before running it on a machine of your own
Dependencies for Gianki Server Hosting
- A Railway volume mounted at
/data(included in this template) - The Gianki apps, or the web app at
/web/on your domain, for the people who will use it
Implementation Details
- Gianki apps and server documentation: https://gianki.com
- Running the server in a container: https://gianki.com/server.html#docker
- Container image:
ghcr.io/agentbillo/gianki-serverAfter deploying:
- Open the service's public domain and sign in as
admin. The password was generated for you: it is theGIANKI_ADMIN_PASSWORDvariable on the service's Variables tab. - Open the admin console at
/adminto invite people or create a registration code. - In the apps, enter your domain as the server address.
Variables:
gianki-server.GIANKI_ADMIN_PASSWORD the first administrator's password. It is used once, when the team is created; changing it afterwards changes nothing. gianki-server.GIANKI_TEAM_NAME optional. Your team's name, which can be changed later in the console. gianki-server.RAILWAY_DEPLOYMENT_DRAINING_SECONDS leave at 45. It gives the server time to write its last messages to disk before a redeployment stops it. gianki-server.PORT leave at 8080. With a custom domain, add GIANKI_PUBLIC_ORIGIN=https://chat.example.com so that invitation and password-reset links use it.
Why Deploy Gianki Server 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 Gianki Server 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.
Template Content
gianki-server
ghcr.io/agentbillo/gianki-server:latestGIANKI_TEAM_NAME
Team name displayed to your users
GIANKI_ADMIN_PASSWORD
The password for your admin user. Username is 'admin'
