OnlineOrNot VS firestarter

Personally, I built OnlineOrNot (https://onlineornot.com/) - it's a set of uptime monitoring tools, with a hosted status page.

There's an open source CLI (https://github.com/onlineornot/onlineornot), and a public API under active development.

There's an open source CLI, and a public API under active development.

I've been working on OnlineOrNot for two years (as of last week), and started building an open source CLI in TypeScript for it:

https://github.com/onlineornot/onlineornot

I'm finding building a CLI fun because it's still a "frontend", but you have to think harder about how the UX should work - since you can't just make it pretty.

(it's also a cheap way to grow the roadmap for my public API since I need to build all these endpoints to make what I want to do possible)

As of (today, actually), it also has an open source CLI, and a public API.

I've been working on the same uptime monitoring/status page web app for two years (as of next week!), and decided to start building a CLI and API for it: https://github.com/onlineornot/onlineornot

It doesn't really do anything yet, but I'm stoked I managed to get automated releases and CI setup (with preview releases for PRs).

Building a SaaS and web app starter kit https://github.com/mcapodici/firestarter using NextJS, Firebase and Tailwind

Working on a ChatGPT tutorial now for it:

I agree. I accidentally ended up using the very basic todolist in my starter kit https://github.com/mcapodici/firestarter for all my todos! And noticed the ui and ux issues as a result.

My open source project is mostly aimed at this. Happy to help out early adopters (find me on twitter @mcapodici)

https://github.com/mcapodici/firestarter

1. Check

2. Check: I started using github spaces developing this

3. Check

4. Uses Firebase, trading off open sourceness for convenience

Firestarter https://github.com/mcapodici/firestarter, is perhaps a more humble project than most.

It is an attempt to build what is (in my opinion!) a great stack for quickly iterating on a web app idea. Probably about a month off from first release, which will be a simple TODO app you can sign up for, with full instructions on getting it set up and deployed that would be about an hour's work. From that point you have a semi-professional setup with devops and CI taken care of so you can move faster on your idea or startup.

Uses Firebase/NextJs/Vercel/React/Tailwind/Github Actions/Jest/Testing Library

This is something I have been considering as I work on firestarter [0] which is a going to be an open source starting point for building a SaaS.

I decided tests are a good thing to have, and especially when already set up and you can easily add more by following the pattern.

I prefer unit tests that are narrow in scope and avoid IO interactions (for example databases)

Of course anyone using my framework can ignore the tests if they desire. But my gut feeling is tests save you time in the short run as well as long run.

[0] https://github.com/mcapodici/firestarter