clerk VS Sentry

Example view using htmx here

You can also pass it into a form, which seems like more work for little benefit (example).

I've just started experimenting with using HTMX with Django. It's been fucking rad so far, I've drunk the Kool-Aid perhaps, but I'm still fumbling around for the best way to achieve certain behaviors. If anyone has general advice or a link to a guide or some example code for a non-trivial app they can share that would be cool.

https://github.com/AnikaLegal/clerk/blob/develop/app/core/views.py#L14

unittest vs pytest is really a personal style decision, I like pytest better personally because it gives you quick access to useful fixtures like `client` or `monkeypatch`. Here's an example test using the client fixture to simulate a post request.

If you're running your apps in a Docker container and writing logs to a file then you might need to use a volume to ensure that the logfiles are persisted to the host server (ie the logs don't dissapear when the container dies). Alternatively you can use a log aggregation service like Papertrail (below)

building an image in github actions, testing it, and pushing it to Docker Hub (private repo) (yaml)

First, sign up for a free account at https://sentry.io. Create a new project and make note of your DSN (Data Source Name).

Using APM tools like NewRelic, Sentry, Datadog, etc to monitor the performance of your application and while you're on it, they can help you identify N+1 queries.

However, ensuring the reliability and performance of your Next.js app is equally crucial. That’s where Sentry comes into play. Combined with Sentry, an industry-leading error monitoring platform, Next.js empowers developers to proactively identify and resolve issues that may arise in their applications. In this article, we’ll explore how to integrate Sentry into your Next.js project for effective error monitoring and performance optimization.

Sentry: Error monitoring for applications, including APIs. Also offers application performance monitoring (APM).

Indeed, webapps are not immune to distribution problems. Wayward and invasive browser extensions are a clear threat, as are 3rd-party dependencies (and their dependencies) loaded at runtime. Which is why companies like https://sentry.io exist. I think the difference is that webapps are "distributable by default" and it takes real work to break this. Versus having local desktop apps which require work to distribute. A potent example of the power of defaults.

Sentry produces nothing of value? You don't value an open source error tracking and performance monitoring platform? https://github.com/getsentry/sentry

> You invent something, and then immediately turn it into a cheap commodity by releasing it for free.

Exactly. A 71-line python script https://github.com/getsentry/sentry/commit/3c2e87573d3bd16f6... was groundbreaking when it came out and the fact that it springboarded into a startup is commendable.

sentry.io: 5

Sentry - Open Source Alternative For Error Tracking

11. Sentry