Gateways
Gateways allow you to expose your Hop deployments to your project or the internet.
There are 2 types of gateways: Internal or External. External gateways expose your deployment to the internet under a protocol of your choice, e.g. HTTP. Internal gateways expose your deployment to your project by giving you an IP address and customizable internal domain to use.
Currently, both gateway types round-robin requests between containers. In the future, there will be more fine grained controls for load balancing requests.
Creating a Gateway
It's easiest to create a gateway through our console, however keep in mind that all of Hop is built around a REST API, so you can automate this if you need to.
Navigate to the Gateways tab in an Ignite deployment:
Click on the "Create Gateway" button in the top right:
You will be presented with a modal:
Here, you can select the gateway type and target port.
Gateway type can be either:
- External, or
- Internal
At the moment, external gateways only support HTTP(S), so there's no option to select the protocol yet.
The target port should be the port your app listens on. The gateway will load balance requests between containers on the target port. HTTP gateways will automatically handle external HTTP and HTTPS termination on the correct ports (80 & 443), so you don't need to run your application on these ports.
Click Create Gateway.
Adding Custom Domains
By default, every external gateway gets assigned it's own .hop.sh domain, generated using the deployment name. You have the choice to update this subdomain to something not taken already, or you can add your own custom domains.
Head over to the "Domains" page inside your gateway.
Here, you can manage the .hop.sh domain as well as add your own custom ones. To add a custom domain, click on the Attach Domain button in the top right of the page.
You will be presented with this modal, where you should enter your desired domain.
Click Next.