📈 Statty on Railway

A no-nonsense status page / statistics server.

🚄 All aboard!

Railway is a platform for quickly deploying services, akin to Heroku. The difference being it has a generous free tier with blazing fast response times. I decided it would be better to drop a status monitor here instead of a Raspberry Pi. To get your own deployment, click on this magical button!

👉 👈

Once copied, edit the config.json to your liking and commit the changes. Railway will automatically rebuild and update the deployment. You can follow my configuration as an example, which is live at https://status.dj.je.

❔ What is Statty?

Statty is an application server that powers a status page. It monitors your services and keeps track of response times and average uptime. It is designed to be lightweight and minimal, you only need to configure it once and it does the rest.

Statty can also be configured to send notifications if services are reported to be unreachable, and send all clear notifications when they come back online. Alerts are sent via Slack-compatible webhooks, and can be enabled or disabled for each service.

Statty is built with Next.js, which allows the dashboard to load fast and stay responsive.

🚀 Running in Production

This project uses GitHub Actions to run automated docker builds, you can find them in this repo's Package Registry. A sample Docker Compose file has been provided for you to use as a reference.

📝 Configuration

Statty services are configured using YAML or JSON. A JSON schema has been provided for use in IDEs. By default, Statty looks for config.yaml, config.yml, or config.json in the application's root directory. You can override this behaviour using environment variables. Refer to .env.example for documentation.

Statty also requires a Redis database for persistence between restarts. This is configured using environment variables. Refer to .env.example for documentation.

💖 Special Thanks