Is Postiz Ready for Primetime?

[crazybrad]

Decided to implement Postiz and after working through the config and options, I realized that the app is of marginal use on Cloudron. Here are the details:

(1) You can enable OIDC which is great. But if you disable registration, you are unable to invite any other users to your "workspace".

(2) If using OIDC, potentially each Cloudron user could have their own workspace, but you would have to enable registration, add the user, and then disable the user.

(3) Assuming you follow the path in #2, there is no admin interface to see the users in your instance, leaving you with the potential that someone unknown has signed up and is using your Postiz instance.

(3) If you use the app's own authentication (not OIDC), you can invite other users, but can only have a single workspace per domain. (see #4)

(4) #3 would not be a problem as you can define a workspace for each Cloudron domain you wish, except that the Docker container is massive (4GB) due to an unoptimized node_modules. So the cost of an instance per domain is 4GB of disk and 1GB of RAM. A lot of resources wasted.

If you are social media team of 1 person and need only one workspace on your server, I can see where Postiz would work. But with Cloudron's strength being a multi-domain architecture, Postiz seems to be lacking in many areas.

Any other opinions?

[joseph]

To add to this, the latest release requires temporal which requires its own portgresql database. So postiz app needs two databases. It's not clear where the app is headed, but it's really difficult to selfhost (and use).

[crazybrad]

@joseph Thanks for this update. I see no point (for me) in going further with Postiz. I would support looking for a better alternative.