v1

Public Northflank domain names, available online and used to associate with your own domain names, take the format:

[port-name]--[service-name]--[project-name]--[entity-dns-id].northflank.app

Public ports can only use HTTP.

Public ports can be linked to your own subdomain.

Private Northflank domain names, to be used internally by other Northflank services, take the format:

[service-name]:[port-number]

Private ports allow services in the same project to communicate with each other. You can access the port within the project by using the internal domain name.

Private ports can use HTTP, TCP, or UDP.

When you create a new deployment Northflank will scan the image manifest and attempt to identify and add the ports exposed by the image. You can also detect ports from the ports & DNS page on a service. You should always verify that the ports are correct for your deployment.

You can expose ports in your Dockerfile in the following ways:

# HTTP port (public by default)
EXPOSE 3000
# TCP port (private)
EXPOSE 2121/tcp
# UDP port (private)
EXPOSE 7171/udp

You can edit ports on your deployment's ports & dns page. Saving a new port configuration will rollout a restart of your running deployments.

You must give each port in your service a unique name. Your port name will be used to create your Northflank generated domain.

© 2021 Northflank Ltd. All rights reserved.