perf(orchestrator): add POSTIZ_ACTIVE_PROVIDERS to limit idle Temporal workers

[onyedikachi-david]

Problem

On a standard Postiz deployment, getTemporalModule starts 32 Temporal workers (one per supported social provider + main), regardless of which integrations are actually configured. Each worker long-polls Temporal continuously, causing significant idle CPU/RAM overhead on every self-hosted instance.

From issue #1570, a deployment with only 8 configured integrations reports:

• postiz container: ~27% CPU, 672 MiB RAM at idle
• temporal container: ~31% CPU
• temporal-elasticsearch: ~330 MiB
• ~24 idle Postgres connections looping COMMIT

Root cause in temporal.module.ts:

workers: [
  { identifier: 'main', maxConcurrentJob: undefined },
  ...socialIntegrationList,          // all 31 providers
]
  .filter((f) => f.identifier.indexOf('-') === -1)
  .map((integration) => ({ autoStart: true, ... }))  // all start, always

Solution

Introduce an optional POSTIZ_ACTIVE_PROVIDERS environment variable — a comma-separated list of provider identifiers. When set, only those workers (plus the always-required main worker) are started.

# Only start workers for the 8 providers you actually use
POSTIZ_ACTIVE_PROVIDERS=twitter,instagram,linkedin,bluesky,telegram,facebook,threads,youtube

This reduces 32 idle workers to 9, eliminating ~23 long-pollers and their CPU/RAM/connection overhead.

Backwards compatibility

When POSTIZ_ACTIVE_PROVIDERS is unset (the default), all 32 workers start exactly as before. Existing deployments are completely unaffected — no action required on upgrade.

Changes

• libraries/nestjs-libraries/src/temporal/temporal.module.ts — adds parseActiveProviders() helper and a second .filter() step in the worker list builder
• .env.example — documents the new variable with all available provider identifiers

Testing

• Unset POSTIZ_ACTIVE_PROVIDERS → all 32 workers start (existing behaviour )
• POSTIZ_ACTIVE_PROVIDERS=twitter,instagram → 3 workers start: main + twitter + instagram
• POSTIZ_ACTIVE_PROVIDERS=TWITTER, Instagram → case-insensitive + whitespace-trimmed → same 3 workers
• POSTIZ_ACTIVE_PROVIDERS= (empty string) → treated as unset, all workers start

Closes #1570

[postiz-contribution]

Contribution-checker quality warning
Heuristic score: 0/100 (low). This is a non-blocking warning surfaced by the project's quality settings.

Heuristics that flagged:

• Excessive emojis in body: 4 emojis (>2)
• Excessive inline code references: 17 inline refs (>3)
• PR doesn't use the repo's PR template: 5 required checkbox items missing (max 1, match ≥80%)
• Body adds too many extra headers beyond the template: 6 extra headers (>1)
• Commit message too long: Longest: 1136 chars
• Excessive added comments: 21 added comment lines (ratio 1.24)
• No public email

If this is a genuine contribution, please add detail to your PR description and tighten the diff scope before reviewers look at it.

[postiz-agent]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[postiz-contribution]

Contribution-checker quality warning
Heuristic score: 16/100 (low). This is a non-blocking warning surfaced by the project's quality settings.

Heuristics that flagged:

• Excessive inline code references: 17 inline refs (>3)
• PR doesn't use the repo's PR template: 5 required checkbox items missing (max 1, match ≥80%)
• Body adds too many extra headers beyond the template: 6 extra headers (>1)
• Commit message too long: Longest: 1136 chars
• No public email

If this is a genuine contribution, please add detail to your PR description and tighten the diff scope before reviewers look at it.

[postiz-contribution]

Contribution-checker quality warning
Heuristic score: 16/100 (low). This is a non-blocking warning surfaced by the project's quality settings.

Heuristics that flagged:

• Excessive inline code references: 17 inline refs (>3)
• PR doesn't use the repo's PR template: 5 required checkbox items missing (max 1, match ≥80%)
• Body adds too many extra headers beyond the template: 6 extra headers (>1)
• Commit message too long: Longest: 1136 chars
• No public email

If this is a genuine contribution, please add detail to your PR description and tighten the diff scope before reviewers look at it.