I really wanted Coolify to work, as I like the idea behind it. I gave it a go some time ago, and I ended up spending the entire evening battling issues like the proxy not running, with no helpful UI feedback whatsoever.
So I came to the conclusion that if I have to dig through abstractions built by someone else, only to find out that in the end I have to manually restart the underlying containers anyway, I might as well stick to using Docker directly.
And truth be told, it’s not even that difficult to handle it all yourself. And it’s definitely very educational. It gives me a nice feeling of being in control and knowing my server. And on top of that it’s fun too.
I think there is an issue with the implementation of search and filtering.
When I open https://mpa.nuejs.org/ and type "kind of rate limit" in the search box, I get 383 search results, and the URL updates to include the query: /app/search/?query=kind+of+rate+limit.
However, when I paste that URL directly into a new tab, I only see one result instead of 383.
> You can’t schedule replies, because Threads wants the platform’s conversations to feel real-time and alive.
However, nothing feels less authentic than optimizing for audience growth by scheduling posts in the first place.
Maybe it’s just me—not a content creator or public figure in any way—but I’ve always felt that the best aspect of Twitter, Threads, or Bluesky is the spontaneity in expressing your thoughts.
> Prisma’s architecture has historically limited community contributions. Core functionality—such as query parsing, validation, and execution—has been managed by our Rust engine, which has been opaque to our TypeScript-focused community. Expanding capabilities or fixing core issues often fell solely to our team.
> We’re addressing this by migrating Prisma’s core logic from Rust to TypeScript and redesigning the ORM to make customization and extension easier.