[push-app-to-main]

Name of the Script

CertMate

Script Type

CT (LXC Container)

Script path

No response

Where does it run?

Proxmox VE host

Does this script support arm64?

arm64 supported

📋 Script Details

community-scripts/DevScripts#2338

New script: CertMate, a self-hosted TLS certificate lifecycle manager with ACME issuance/renewal (Let's Encrypt and other CAs), DNS-01 on 20+ providers, inventory, deployment hooks and a REST API. It is a Python/Flask app served by gunicorn.

---

Automated migration from DevScripts (community-scripts/DevScripts#2344).

[github-actions]

Try this branch

The engine and the scripts resolve independently, so this runs the changed
ct/ and install/ scripts against the production engine:

export COMMUNITY_SCRIPTS_URL=https://raw.githubusercontent.com/community-scripts/ProxmoxVE/add-script-certmate-1791526610
bash -c "$(curl -fsSL "$COMMUNITY_SCRIPTS_URL/ct/certmate.sh")"

Both lines are needed. Without COMMUNITY_SCRIPTS_URL the engine falls back to
main, so curling the branch URL on its own gives you the ct/ script from
this PR and the install/ script from main. Frequently the one you meant to test.

The same command works on an Incus host: the engine detects the platform and
loads the matching backend, while the scripts still come from this branch.

Useful while testing

dev_mode=net logs every fetch with status and URL, which is the quickest way
to confirm the branch is really being used. dev_mode=keep stops a failed
build from deleting the container along with the evidence.

export COMMUNITY_SCRIPTS_URL=https://raw.githubusercontent.com/community-scripts/ProxmoxVE/add-script-certmate-1791526610
dev_mode=net,keep bash -c "$(curl -fsSL "$COMMUNITY_SCRIPTS_URL/ct/certmate.sh")"