• 0 posts
  • 4 comments
Joined 11 months ago
Cake day: August 21st, 2025
  • I custom-build the Caddy container since it is easy to do with xcaddy. It is automated to run every week via Forgejo Actions on a Forgejo repo, and one can pull the latest images from there using Portainer or whatever docker updater software there is.

    You can also use any other CI/CD solutions you like as long as it churn out a regularly updated image. Github Actions is another good one if you don’t wanna set up Forgejo.

    The caddy-cloudflare image is probably also enough for your use case, assuming they’re regularly updated. But if you like control, CI is one way to go.

  • If you are running a conduit fork, what is your reason for leaving conduit, and if you are running conduit, why didn’t you switch?

    Conduwuit (predecessor of Continuwuity and Tuwunel) hard-forked from Conduit and introduced breaking database changes. That is a significant people don’t easily “switch over”

    It may be slow in development, taking a bit longer to implement a new feature, but not too much longer.

    I would say its pace of development is very slow compared to the pace of Matrix in general. But if you only want the barebones features, you can use it.

    Or am I missing something the others have to offer?

    Feature-wise, Continuwuity offers email support, single-use registration token, policy server integration, user suspending, a ton more of admin commands, and some extra endpoints for Element Call. It is also actively working on OIDC-OAuth (so you can login with your IDP), and an ecosystem-wide Admin API. It also has an active community. I can’t speak for the other fork.

    Lastly, I don’t think anyone “hate” conduit, the project is alright. It’s just not the topmost option.