Postiz

community-scripts/ProxmoxVE#1693
https://docs.postiz.com/installation/development

Application Name
Postiz

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

Description
Postiz helps you to manage all your social media accounts.

Schedule all your social media posts (many AI features)
Measure your work with analytics.
Collaborate with other team members to exchange or buy posts.
Invite your team members to collaborate, comment, and schedule posts.

Hi! I see the task as done and closed, does this mean it's not going to be implemented?

Same question, why not planned?

@michelroegl-brunner

@michelroegl-brunner

Hi! Any news on this one?

ive finalized the Script for Testing State, but i dont have any idea how to use this tool. The Agent Chat doesnt respond, but i dont know if i need to setup an local agent or something else. Maybe an user / requester can answer this. This tool need an full test of requested user, if not, we remove it in May.

when i install it first installs correctly. postiz itself relies heavy on environment variables (see here for eg instagram: https://docs.postiz.com/providers/instagram ) these variables need to be set up for each instance individually and then the information must be given to postiz by these env variables. (mastodon and bluesky can be configured directly in the web ui, the rest not)

FACEBOOK_APP_ID="app id"
FACEBOOK_APP_SECRET="app secret"

For each provider, this has to be done, then postiz needs to be rebuilt again.

when i run
pnpm run build

i get errors and it doesn't compile correctly

maybe we need to upgrade the script so that it shows the .env in the home dir and then a command that starts to rebuild it correctly?

Update 21-04:
One of the most upvoted tools, but NO ONE FROM THIS REQUEST RESPOND;
community-scripts/ProxmoxVE#1693

So i deferr the migration for now.

The postiz script is ready for testing:
bash -c "$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/ct/postiz.sh)"
The build process requires significant RAM (4GB+). Do not reduce container RAM below 4GB.
NEXT_PUBLIC_* variables are baked at build time. If you change the IP/URL or add social provider keys, rebuild with: postiz-rebuild

Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.

I am testing this now and it is nice that it runs bare-metal. I have it working with a Cloudflared tunnel. It looks good. Indeed, the API for OpenAI is not working properly yet, so I will continue testing.

tested looks good to me.

check my spec:

   ____             __  _    
   / __ \____  _____/ /_(_)___
  / /_/ / __ \/ ___/ __/ /_  /
 / ____/ /_/ (__  ) /_/ / / /_
/_/    \____/____/\__/_/ /___/
                              
  ⚙️  Using Default Settings on node pve01
  💡  PVE Version 9.1.1 (Kernel: 6.17.2-1-pve)
  🆔  Container ID: 108
  🖥️  Operating System: debian (13)
  📦  Container Type: Unprivileged
  💾  Disk Size: 20 GB
  🧠  CPU Cores: 4
  🛠️  RAM Size: 8192 MiB
  🚀  Creating a Postiz LXC using the above default settings

A PR has been created for postiz: community-scripts/ProxmoxVE#15048

Files deleted with PR #1946

Navigation Menu

Repository navigation

Postiz #96

16 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Postiz #96

Description

Activity

ocr99 commented on Apr 6, 2025

duntik commented on Apr 11, 2025

duntik commented on Apr 23, 2025

ocr99 commented on May 7, 2025

16 remaining items

p-blaublue commented on Apr 2, 2026

MickLesk commented on Apr 21, 2026

github-actions commented on Apr 21, 2026

monomo71 commented on May 10, 2026

kimwwk commented on Jun 10, 2026

github-actions commented on Jun 11, 2026

github-actions commented on Jun 24, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions