Private Networking

Services in the same project reach each other by name:

<service>.zenavo.internal

For example, an API connects to postgresql.zenavo.internal:5432. The host is shown on the service's Networking tab under Private. Traffic stays inside the server; projects cannot reach each other's services.

Ports

Expose Port under Private adds a port the service listens on. Each port has:

• a name, such as web, used in built-in variables like WEB_PORT;
• a number, the port inside the container;
• a type: HTTP (can get a domain), TCP or UDP (can be published).

Changes to ports and domains apply right away: Zenavo saves them and redeploys the project.