Deploy and Host Bagisto on Railway

Bagisto is an open-source e-commerce platform built on Laravel and Vue: product catalogue, cart and checkout, orders, customers, CMS pages, multi-channel storefronts, and a REST API. This template deploys it with a working encryption key, a private administrator account, and store data that survives a redeploy.

About Hosting Bagisto

This template runs Bagisto 2.4.3 as two services: the application (nginx, PHP-FPM and the queue supervisor in one container, with storage/ on a persistent volume) and MySQL 9.4 on its own volume, sized from the container's memory limit rather than a fixed figure. The Laravel APP_KEY is generated once onto the volume as a real 32-byte key, so encrypted sessions and settings keep working across restarts. The administrator is seeded from your template variables before the store answers a request, and re-applied on every boot, so a redeploy is a working password reset. The installer's seeders run exactly once — they delete and re-insert store configuration every time they run, so anything after the first boot would wipe your channels, CMS pages and attribute options. The app honours Railway's injected port and is healthchecked.

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

The store actually loads — Laravel requires the application key to decode to 32 bytes. A key generated as 32 random characters decodes to 24, and every page then fails with "Unsupported cipher or incorrect key length" while the container still reports healthy. Here the key is generated correctly once and reused.
Your own administrator, not a published one — Bagisto's installer seeds a well-known default account. This template seeds yours from the generated password and removes the default.
Your store settings survive a redeploy — the installer seeders are recorded as done, so a later deploy does not delete your channels, locales, currencies, categories and CMS pages.
Password reset by redeploy — Bagisto's own reset is an emailed link, which a fresh deployment has no SMTP account for. Change the variable and redeploy instead.
Pinned and prebuilt — a fixed upstream version, pulled as an image rather than rebuilt on your build minutes.

Common Use Cases

A self-hosted online store — sell physical, digital, configurable or downloadable products with your own checkout and payment methods.
A headless commerce backend — drive a custom storefront through Bagisto's REST API while using the admin panel for catalogue and orders.
A B2B or multi-channel catalogue — separate channels, locales and currencies over one product set.

Dependencies for Bagisto Hosting

MySQL 9.4 (included in this template) for the catalogue, orders, customers and configuration.
A volume mounted at /var/www/bagisto/storage (included) for uploaded product images, generated caches and the application key.

Deployment Dependencies

Bagisto — the upstream project (MIT)
bon5co/bagisto-railway — the Railway wrapper image this template deploys

Implementation Details

Sign in at /admin with BAGISTO_ADMIN_EMAIL and the generated BAGISTO_ADMIN_PASSWORD from the service variables. To rotate the password, change that variable and redeploy; the new value is applied during boot and the old one stops working.

The first boot runs the database migrations and the full installer seed, so it takes a few minutes before the store answers. Later boots skip the seed.