Deplo

Networking

How traffic reaches an app, your own hostnames over HTTPS, and a URL per pull request.

Everything about the addresses an app answers on, from a permanent production hostname to a throwaway one for a single pull request.


How it works

Every hostname Deplo serves, permanent or temporary, goes through the same router: a rule bound to a container, a certificate resolver when HTTPS is asked for, and a DNS check that decides whether the hostname is actually routed yet.

  • Domains and HTTPS covers the permanent case: your own hostnames, certificates, path-based routing and redirects.
  • Pull request previews covers the temporary case: a deterministic URL per open pull request, torn down when it closes.

A preview's hostname follows the same HTTPS rule as a manual domain, Let's Encrypt when a real domain is behind it, plain HTTP on nip.io when there is none.


See also

Did this page help you?

On this page