Deploy and Host LubeLogger on Railway

LubeLogger is an open-source, self-hosted vehicle maintenance and fuel mileage tracker. It records service, repairs, upgrades, fuel, odometer readings, taxes, reminders, supplies, inspections, equipment, notes, documents, and recurring plans, giving individuals and households a durable history of vehicle condition, costs, and upcoming work.

About Hosting LubeLogger

This community template runs LubeLogger 1.7.0 from the official digest-pinned container image. Railway provides a public HTTPS endpoint on port 8080, checks the built-in /health endpoint, and mounts one persistent volume at /App/data for LiteDB, settings, uploads, themes, translations, and ASP.NET data-protection keys. The public URL is derived from Railway automatically, so deployment has no credential prompts. LubeLogger starts without authentication by default: open the Settings page immediately after deployment, enable authentication, and create the root account before storing private vehicle data. This template is independently maintained and is not affiliated with or endorsed by Hargata Softworks.

Common Use Cases

Track maintenance, repairs, inspections, and recurring service reminders.
Measure fuel economy, mileage, and total vehicle operating costs.
Keep receipts, documents, notes, and history for multiple vehicles.

Dependencies for LubeLogger Hosting

Official ghcr.io/hargata/lubelogger:v1.7.0 image pinned by immutable digest.
One Railway persistent volume mounted at /App/data.

Deployment Dependencies

Implementation Details

The official image declares and listens on port 8080, which Railway uses for routing and health checks. LUBELOGGER_DOMAIN=https://${{RAILWAY_PUBLIC_DOMAIN}} aligns generated links with Railway HTTPS.

Upstream normally persists application state at /App/data and ASP.NET data-protection keys at /root/.aspnet/DataProtection-Keys. Railway supports one volume per service, so the template sets HOME=${{RAILWAY_VOLUME_MOUNT_PATH}}. .NET then stores its key ring at /App/data/.aspnet/DataProtection-Keys, keeping database, files, configuration, authentication cookies, and key material together on the single volume. Losing or rotating the key ring signs users out and can invalidate protected data.

Back up the complete /App/data volume before updating. Review upstream release notes, test the new immutable image digest against a restored copy, and verify /health, sign-in, one representative record, one attachment, and persistence after restart. Roll back by restoring the prior image digest together with its matching /App/data backup if an update or migration is incompatible.

Why Deploy LubeLogger 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 LubeLogger on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, and more on Railway.