this post was submitted on 14 Jan 2026
30 points (87.5% liked)

Selfhosted

54613 readers
691 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Hi everyone, it's been a while since my last update.

Just a recap: Postiz is an open-source social media scheduling tool supporting 25 social media channels/platforms.

You can craft different posts, schedule them in advance, and cross-post them to multiple platforms, and use various tools to make them better.

https://github.com/gitroomhq/postiz-app

Any star would be amazing ❤️

---

Until today, we have used BullMQ to schedule all posts in advance.
Simple Redis queue system.

But what happened is that it was really hard to maintain it because we:

  • Queue for webhooks
  • Queue for comments
  • Queue for plugs
  • Queue for internal plug

They were all self-replenishing queues, meaning that when one queue finishes, it creates another.

Don't take my word for it; something was also wrong in BullMQ (I might be wrong), but some things would vanish.

It was a large, chaotic salad with many bugs.
I investigated further and determined that workflow execution is the best approach.
I reviewed Temporal/DBOS and Inngest and decided to go with Temporal.

I think it's the most open-source-friendly and better for scaling (I might be wrong)

With a big blitz, I consolidated all my huge salad code into a single workflow.

You can also now check your workflow states at http://localhost:8080/ (temporal workflow viewer)

I usually wouldn't post an update on the channel for something like this, but this one was important: if you use Postiz and upgrade from an older version, it will crash.

We have updated our docker-compose docs to the new one.

If you manage to test it, let me know how it goes.

Once you run the new Postiz architecture, any old posts will be moved to Temporal using the Temporal Cron we have configured.

We barely had any new features lately. Postiz's goal today is to be the best social media scheduler possible. That means FIXING DAMN BUGS, and solving technical debt.

If you want to stay with the legacy BullMQ version, don't upgrade after v2.11.3.

I know that many websites, such as Coolify, Cloudron / Elastio, are currently offering Postiz. They are not updated to the new infrastructure; they will fail if you try to deploy. So until they fix it, use v2.11.3.

I am sorry for the significant change, and I know it's a challenge.

you are viewing a single comment's thread
view the rest of the comments
[–] corsicanguppy@lemmy.ca 1 points 2 days ago

Got a version without docker?