awesome-status-pages VS flyctl

awesome-status-page > Open Source: https://github.com/ivbeg/awesome-status-pages?tab=readme-ov-...

Logging cert hashes and checking them against a configurable list and CT Certificate Transparency logs would be useful

It's worth coming up with a stronger public-facing answer

We went through this last year, I think we have a public one, a private one, + our actual more 'serious' telemetry (opentelemetry, ...). For the status pages, I think one we don't pay for, and the other is like $20/yr.

It's a crowded space, so clearer differentiation seems useful for your users and for your own journey: https://github.com/ivbeg/awesome-status-pages

When you have that endpoint working take a look at https://github.com/ivbeg/awesome-status-pages and do your own research on which solution fit better for your use case

Here's a list of a bunch of open source status page services: https://github.com/ivbeg/awesome-status-pages

It's called a status page and they are common (here is reddits) and there are many options. Check this list for some starting ideas: https://github.com/ivbeg/awesome-status-pages

I found this when I searched "self hosted service status page" with something like this as an example. How detailed that is or how to point it to the services, I can't say but I think that would be a start.

To begin visit fly.io to create an account. Next install flyctl a command line tool for creating and deploying fly apps. macOS

For frontend deployment, I used Netlify (for the generous free package) and the recommended fly.io for server + database (also cheap package).

Create an account on Fly.io.

You can learn more about fly.io and tigris, we will need to create an account on both platforms for this project regardless. Anyway with the theory out of the way let's get started in the next section as we create our accounts and start building the app.

Fly.io is a platform that helps you run your apps and databases closer to your users all around the world. It takes your app code, packages it up neatly, and puts it on virtual machines that can be quickly started or stopped. This makes your app faster for users and more reliable. Fly.io is easy to use, works well for small projects or personal apps. It's a great way to make sure your app runs smoothly for people no matter where they are.

In this post, we'll start from scratch, running FerretDB locally via Docker, trying out the connection with mongosh and the MongoDB Node.js client, and finally deploy FerretDB to Fly.io for a production ready set up.

2- fly.io

Fly is a cloud platform that focuses on global edge computing. Fly specializes in high-performance hosting and provides a global network of edge locations. Fly is known for its scalability and performance optimizations.

But videototextai.com is built using NextJS + Firebase auth + Firestore and a backend deployed at fly.io . Fly makes it really easy to deploy docker containers and that is IMO the fastest way to develop, you can setup a local setup

Alternatives explored: * northflank: While running the wrk test, requests were taking 3-7 seconds. Couldn't repeat Heroku's phenomenon of "400ms-800ms" during such a load test. * fly.io: Reliability: It’s Not Great * render.com: I remember the time when indiehackers.com was down because of an outage on Render, not sure if it's worth trusting.