All rapyuta.io docs are open source. See something that's wrong or unclear? Submit a pull request.Make a contribution
On the left navigation bar, click Networking>Static Route.
Click ADD NEW STATIC ROUTE.
Enter a name for Static Route URL.
The name of a static route has lowercase alphanumeric characters, or a hyphen, and must begin and end with an alphanumeric character, and must not be certain keywords, and it must be at least 4 characters and less than 64 characters long.
Click CONTINUE. The static route is created.
Observe that the name of the static route will be a subdomain belonging to .ep-r.io (essentially the provided name will be suffixed with .ep-r.io to form the FQDN). For instance, if the name of the static route is my-example-server, the static route URL will be my-example-server.ep-r.io
Once created, you cannot edit the name of a static route. You can however delete and recreate a new static route with a different name easily.
To bind a static route to an externally exposed endpoint, which is defined in a package, during the deployment process:
Select an external network endpoint from the drop-down list.
Select a static route from the drop-down list.
This creates a mapping between an external network endpoint and a static route.
You can unbind a static route from a network endpoint by clicking on the delete icon.
In this example, the static route my-example-server is bound to the network endpoint server_endpoint as shown below:
On deploying the package after binding a static route, the network endpoint URL address becomes deterministic and is a constant. It implies that even if the deployment is stopped and provisioned again with the same static route, the network endpoint URL address remains the same.
A package deployment can have multiple static routes. However, a single static route is used for a single deployment.
Refer to billing and usage to understand the limits applied on static routes for different subscription plans.