this post was submitted on 14 Jan 2026
31 points (86.0% liked)

Selfhosted

62325 readers
1051 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 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
[–] BroBot9000@lemmy.world 5 points 8 months ago

Got a version without the slop Ai?