title | intro | weight | versions | layout | permissions | showMiniToc | miniTocMaxHeadingLevel | allowTitleToDifferFromFilename | mapTopic | hidden | redirect_from | gettingStartedLinks | popularLinks | guideLinks | introLinks | tags | |||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Custom URLs for Services |
rapyuta.io is a platform that enables robotics solution development by providing the necessary software infrastructure and facilitating the interaction between multiple stakeholders who contribute to the solution development. |
343 |
|
false |
rapyuta.io |
true |
4 |
false |
false |
false |
|
-
In the rapyuta.io console, on the left navigation bar, click Networking > Static Routes.
-
Click Add New Static Route.
-
Enter the Static Route URL. {{%notice info%}} 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. {{%/notice%}}
-
Click CONTINUE. The static route is created. {{%notice info%}}
- 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.
- You cannot edit the name of a static route. However, you can delete and recreate a new static route with a different name. {{%/notice%}}
To bind a static route to an externally exposed endpoint defined in a package, during deployment:
-
Click Add Static Route.
-
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.
Below is an example of the static route my-example-server which is bound to the network endpoint server_endpoint.
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]({{< ref "/5_deep-dives/58_account-management/582_billing-usage.md">}}) to understand the limits applied on static routes for different subscription plans.