You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
communityCollaborate with and develop consensus with the Postgres communitydesignDesigning the architecture, protocols, tools, and interfaces for PGXN v2opsDeployment and operations automation
Work with Postgres infra team to select an OCI registry and host name. Prefer to have it part of the community infrastructure. If not, find another option (might be able to use ghcr.io). Ideally it can be hosted as one of:
oci.postgresql.org
trunk.postgresql.org
oci.pg
trunk.pg
trunk.pgxn.org
Ideally we use a host name controlled by the community so that, if we migrate from one OCI provider to another in the future, things should still work.
The text was updated successfully, but these errors were encountered:
theory
added
design
Designing the architecture, protocols, tools, and interfaces for PGXN v2
community
Collaborate with and develop consensus with the Postgres community
labels
Sep 4, 2024
communityCollaborate with and develop consensus with the Postgres communitydesignDesigning the architecture, protocols, tools, and interfaces for PGXN v2opsDeployment and operations automation
Work with Postgres infra team to select an OCI registry and host name. Prefer to have it part of the community infrastructure. If not, find another option (might be able to use ghcr.io). Ideally it can be hosted as one of:
Ideally we use a host name controlled by the community so that, if we migrate from one OCI provider to another in the future, things should still work.
The text was updated successfully, but these errors were encountered: