public-roadmap VS Coral

We use Caddy for serving our free dashboards and status pages on your own domain at https://checklyhq.com

It was not super easy to set up. I think the whole config is 20 lines or so, but the docs, naming and functionality of how Caddy actually interfaces with LE was tricky to find out. Basically had to scrape together answers from various GitHub issues etc.

I should write a blog post…

Have you given checklyhq.com a look? Sounds like it could be a great fit. (Disclaimer: I work there).

Have a look at https://checklyhq.com. We do exactly that, API monitoring. You can set up a check that parses your API response and validates a specific field. We also have a free plan. Disclaimer: I’m the CTO.

We're looking forward to how Checkly will make their monitoring solution even more accessible for developers with e.g. versioned code, an integrated Monaco editor with better auto-completion, support for custom NPM modules, or a better debugging experience. We would recommend giving it a try and have not to worry about where to run your status checks or end-to-end tests and benefit from their simplicity. For a more detailed outlook, they provide an official public roadmap on GitHub.

The Coral Project [0] (commenting platform used on Washington Post, New York Times, The Verge) uses an Apache 2.0 license [1]. Which doesn't seem to have prevented it from raking in big SaaS customers.

A lot of people worry about copy-cat services, but it's kind of rare that someone will be able to compete with you as the original in hosting your own service as well as you can. Especially when you consider support and maintenance requirements of a new product you aren't personally developing.

I could see copy-cat services being more of an issue in the late stage of a product though? When everyone knows lots about how to stand it up and use it?

[0] https://coralproject.net/

The Coral Project was created inline with this initiative. They have lots of guides that provide some of the research that was conducted: https://coralproject.net/

For comment system, I choose Coral Project Talk because it could use Akismet and Google Perspective API for reducing spam and harassment. I also need to think about the remove comments when user delete their account (GDPR stuff). Coral Talk has the above functions in the UI.

Another great API that could be self-hosted is Coral. It’s a commenting platform where users can leave online comments. It’s received contributions from over 40 people on Github. It has a good-first-issue tag and also offers a contribution guide.

Yup! We do a Typescript/Node.js/GraphQL back-end with React/Relay/Typescript on the front end.

https://github.com/coralproject/talk

It's pretty nice having the whole code base share types, syntax, structure, etc.

Coral is poorly advertised outside it's ecosystem, but should be considered. https://github.com/coralproject/talk

See https://docs.coralproject.net/coral/v5/integrating/cms/ to get an idea of it's use.

Our highest tier comment system is quite powerful, and is based off Coral Talk by Vox. For beginners like yourself, if we allowed users to integrate Disqus on all tiers, would that alleviate your concerns with using Storipress?

If you need some inspiration, we added support for server caching of responses on Coral: https://github.com/coralproject/talk/blob/develop/src/core/server/app/middleware/graphql/apolloServer.ts#L85-L88

I've seen some examples in which people embed Discourse discussions.

There's also Coral (https://github.com/coralproject/talk) which used to be Mozilla + Vox project before Mozilla handed it over to Vox completely, but I have no experience with it.