Multiple portals per Org support in the Developer Portal

[NethmiRanasinghe]

1. What is the problem

The Developer Portal currently assumes a one-to-one mapping between a portal instance and an organization. A single organization row is pinned at startup, and every database query is scoped only by org_uuid.

This means it is not possible to run multiple portal instances against the same organization with isolated data per portal which is a requirement for cloud (SaaS) deployments where organizations need separate developer portals.

2. Why we are solving it

• Cloud/SaaS onboarding requires one organization to host multiple developer portals, each serving a distinct product group or audience, from a single shared database.
  • Without this, the only isolation option is a separate database per portal, which is operationally expensive.

3. Proposed solution

• A devportal_id column is added to all org-scoped tables, and every affected query is filtered by both org_uuid and devportal_id.
• The portal id is read from config.toml (or overridden via an environment variable for cloud deployments), so each portal instance is pinned to its own identifier at startup.