[PR #12097] [CLOSED] Submit/postiz #9964

Closed
opened 2026-02-26 17:32:28 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE/pull/12097
Author: @jelicanin
Created: 2/19/2026
Status: Closed

Base: mainHead: submit/postiz


📝 Commits (3)

  • 50869af feat: add Postiz installation and configuration scripts
  • e7a183a fix(postiz): make first-start readiness check resilient
  • 6a7bb4d chore(postiz): point script URLs to upstream for PR

📊 Changes

3 files changed (+227 additions, -0 deletions)

View changed files

ct/postiz.sh (+56 -0)
frontend/public/json/postiz.json (+52 -0)
install/postiz-install.sh (+119 -0)

📄 Description

✍️ Description

Adds new Postiz LXC script set:

  • ct/postiz.sh
  • install/postiz-install.sh
  • frontend/public/json/postiz.json

Implementation details:

  • Docker-based Postiz deployment using upstream compose files.
  • Auto-generates DB password and JWT secret.
  • Creates /opt/postiz/docker-compose.override.yaml.
  • Adds startup resilience for slow first boot (does not fail unnecessarily while containers initialize).
  • Includes update flow (docker compose pull && up -d --remove-orphans).

Tested on local Proxmox:

  • PVE 8.4.16, Debian 13, unprivileged CT
  • 2 CPU / 4096 MB RAM / 50 GB disk
  • Post-install access verified on http://<CT_IP>:4007
  • Container stack status verified with docker compose ps

Related discussion: https://github.com/community-scripts/ProxmoxVE/discussions/1693

Prerequisites (X in brackets)

  • Self-review completed – Code follows project standards.
  • Tested thoroughly – Changes work as expected.
  • No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

🛠️ Type of Change (X in brackets)

  • 🐞 Bug fix
  • New feature
  • 💥 Breaking change
  • 🆕 New script
  • 🌍 Website update
  • 🔧 Refactoring / Code Cleanup
  • 📝 Documentation update

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/community-scripts/ProxmoxVE/pull/12097 **Author:** [@jelicanin](https://github.com/jelicanin) **Created:** 2/19/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `submit/postiz` --- ### 📝 Commits (3) - [`50869af`](https://github.com/community-scripts/ProxmoxVE/commit/50869af8bb48824a19ae52e01e4023e3a5e1e022) feat: add Postiz installation and configuration scripts - [`e7a183a`](https://github.com/community-scripts/ProxmoxVE/commit/e7a183ae95d572d4a90880fbe757e57f597d3c62) fix(postiz): make first-start readiness check resilient - [`6a7bb4d`](https://github.com/community-scripts/ProxmoxVE/commit/6a7bb4debaabd032fccc662d9d84d1b41c7210c7) chore(postiz): point script URLs to upstream for PR ### 📊 Changes **3 files changed** (+227 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `ct/postiz.sh` (+56 -0) ➕ `frontend/public/json/postiz.json` (+52 -0) ➕ `install/postiz-install.sh` (+119 -0) </details> ### 📄 Description ## ✍️ Description Adds new Postiz LXC script set: - `ct/postiz.sh` - `install/postiz-install.sh` - `frontend/public/json/postiz.json` Implementation details: - Docker-based Postiz deployment using upstream compose files. - Auto-generates DB password and JWT secret. - Creates `/opt/postiz/docker-compose.override.yaml`. - Adds startup resilience for slow first boot (does not fail unnecessarily while containers initialize). - Includes update flow (`docker compose pull && up -d --remove-orphans`). Tested on local Proxmox: - PVE 8.4.16, Debian 13, unprivileged CT - 2 CPU / 4096 MB RAM / 50 GB disk - Post-install access verified on `http://<CT_IP>:4007` - Container stack status verified with `docker compose ps` ## 🔗 Related Issue Related discussion: https://github.com/community-scripts/ProxmoxVE/discussions/1693 ## ✅ Prerequisites (**X** in brackets) - [x] **Self-review completed** – Code follows project standards. - [x] **Tested thoroughly** – Changes work as expected. - [x] **No security risks** – No hardcoded secrets, unnecessary privilege escalations, or permission issues. --- ## 🛠️ Type of Change (**X** in brackets) - [ ] 🐞 **Bug fix** - [ ] ✨ **New feature** - [ ] 💥 **Breaking change** - [x] 🆕 **New script** - [x] 🌍 **Website update** - [ ] 🔧 **Refactoring / Code Cleanup** - [ ] 📝 **Documentation update** --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-02-26 17:32:28 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ProxmoxVE#9964
No description provided.