pusher-js VS django-htmx

another tool is pusher but have a high cost https://pusher.com/

Pusher specializes in realtime WebSockets and offers a straightforward way to integrate realtime features into your React app. It's a reliable choice for apps that need to send notifications based on realtime events.

why are you considering building your own websocket service instead of using something like https://pusher.com/ ?

IVS offers chat rooms, but Kick doesn't seem to use them. All chat messages are sent over a websocket connection to Pusher. Pusher seems pretty cheap for the purpose.

Serveless Websocket service

Is it possible to use Supabase as a Pusher alternative?

if you are on time, since it is a coursework, and it is allowed to use some libraries, you can check how to use pusher it should be fairly easy for you too integrate to your application.

I've built a flutter web chat using flutter_chat_ui and dart_pusher_channels, for the backend I used soketi which is an open source node.js pusher replacement but you could just use pusher.com if you can squeeze into their free tier.

What? No. Takes 5-10 minutes to set up a websocket server manually or is just requires a few configuration variables to be set if using a hosted service like Pusher.

ah - a good callout. No. You can setup a `subscription` model and use something like https://pusher.com/ to accomplish this, but it's more manual.

If you don't already, you should use django-htmx. This will allow you to check if the request was made with HTMX. You can then do something like this:

To make things easier, install the django-htmx package. Then, in your Page model's serve(), you can do things like if request.htmx: and return an HTML snippet instead of the full page in that case.

The great thing about HTMX is it fits really nicely with templated server-rendered frameworks like Django.

You can have a page with a list of items. The page is one template, and it includes a sub-template which is just the

items. Then you have a separate view for "get list fragment" which just returns the updated/sorted/filtered

. If you toggle the ordering, or filter the list, HTMX will automatically call the fragment renderer and replace just the

items, without reloading the page.

See this example: https://github.com/adamchainz/django-htmx/blob/8054f049f53f0...

This approach solves the common interactivity use-cases requiring JS in a server-rendered app, without having to write any JS, and without having to build a REST API. Instead you just render HTML, which your framework is excellent at.

If you use django-htmx, it's pretty simple to get the "this HTTP request came from HTMX" flag and branch accordingly in your view. The docs give a simple example of the logic here:

https://django-htmx.readthedocs.io/en/latest/middleware.html...

The examples give a fleshed-out version: https://github.com/adamchainz/django-htmx/blob/main/example/...

Though that's very slightly different than how I described it above, but it's basically the same idea; in this case you commonize the `main` block between the two contexts.

HTMX has a HX-Trigger response header that enables you to trigger events in the browser that Javascript code can listen for. Assuming you already have Django-HTMX library set up, you could write a middleware like this:

Nice. I've written some less complete, less consistent variant of this a couple times now. That alone may be worth taking the dependency.

Full URL for django-htmx: https://github.com/adamchainz/django-htmx (creator here)

I think it's fair to clarify that Adam Johnson (aka adamchainz on Reddit and GitHub) didn't create HTMX but did write the django-htmx app to make it easier to use HTMX in Django.

django-htmx also comes with it's own version of HttpResponseHtmxRedirect (called HttpResponseClientRedirect).