Using a custom domain

By default, pullpreview instances will use a domain name such as pr15-my-beautiful-code-1-2-3-4.my.preview.run.

Built-in DNS alternatives

In addition to the default my.preview.run, PullPreview provides these built-in DNS suffixes:

rev1.click, rev2.click, rev3.click, rev4.click, rev5.click, rev6.click, rev7.click, rev8.click, rev9.click

These are useful when you need to spread across multiple domains to avoid Let's Encrypt rate limits (50 certificates per registered domain per week).

with:
  dns: rev1.click

Using your own custom domain

If you wish to use a custom domain instead (e.g. pr15-my-beautiful-code-1-2-3-4.preview.domain.com), you can do so by:

• assuming you own domain.com and want previews to be under <ENV-NAME>.preview.domain.com, add a record in your DNS zone so that preview.domain.com is a NS record for xip.preview.run.
• add the dns [input] parameter in your workflow file to indicate the domain you want to use:

with:
  dns: preview.domain.com

That's it! Using a custom domain also gives you an independent Let's Encrypt rate-limit quota.