-
Notifications
You must be signed in to change notification settings - Fork 0
Quick Start
First of all, log in and proceed to FlexBalancers
page:
Select name for your Balancer, Custom code
button and press Next step
:
Then, fill in your fallback
address. You may also select desired TTL
. Then, press Create New FlexBalancer
button:
Now, you have text editor open, so you can write or post there your custom code.
Supported language: TypeScript
.
Editor: Monaco Editor, see Monaco Editor Accessibility Guide for detailed info.
Notice, that you also are able to edit FlexBalancer description, Fallback and TTL:
The text editor checks your code syntax for errors:
And shows error details on mouse hover:
And provides helpful hints (use Ctrl+Space
) and auto-completion (use Tab
):
After all changes are done and no errors remain, press Test and Publish
button:
Confirm the deployment:
The next page has important information, do not forget to copy/save CNAME
record for further placement into domain settings for your domain, then press Done
:
Now you can see your newly created FlexBalancer at FlexBalancers
page:
Let's check if your Custom Answer works. After some time, when you already have made all nessessary CNAME
changes - check CDN RUM Uptime at CDNPerf.
You can see that RUM Uptime is higher than 98,5
.
So, according to rules that you have defined at Custom Answer, it should return google.com
as response address.
And it does! That means your FlexBalancer works perfectly!
To change your custom answer, proceed to FlexBalancers
page and press square button with pen at your Balancer:
You can edit your code, FlexBalancer description, Fallback and TTL:
You are also able to turn your FlexBalancer off and even to Delete it:
After editing, press Test and Publish
button, then Deploy now
:
Do not forget to copy/save FlexBalancer name for placement into CNAME
record of domain settings for your domain, then press Done
:
Proceed to FlexBalancers
page and press red square button with trashcan picture on it:
Confirm the deletion. Keep in mind that it may break your service:
Create your first FlexBalancer
- Case 1.1: Provider Availability with Weights.
- Case 1.2: Availability based on Monitor Uptime.
- Case 2.1: Balancing based on the CDN with the better Performance.
- Case 3.1: Geolocation with excluded country.
- Case 3.2: The specific answer for the specific region.
- Case 3.3: The provider with the best performance for visitor's country.
- Case 4.1: Using country-based answers from remote sources.