Follow

Pugpig Domains

CMS DOMAINS

The domains you'll get for access to your CMS are:

<publication>.prod.<account>.pro.pugpig.com
<publication>.stage.<account>.pro.pugpig.com

For example:

weekly.prod.acme.pro.pugpig.com
weekly.stage.acme.pro.pugpig.com

PUBLIC FACING DOMAIN:

The public facing domain for your content and web reader will be:

<account>-<publication>-<endpoint>.content.pugpig.com

For example, in multi-lingual app:

acme-weekly-en.content.pugpig.com
acme-weekly-fr.content.pugpig.com

The public facing content domain should always be HTTPS and used for:

  • everything in the admin
  • everything in the apps
  • for web reader auth endpoints

VANITY DOMAIN

Vanity domain should only be used for:

  • the link to the web reader (including sharing links)
  • the CORS header on the authentication endpoints
  • one of the domains to Fastly

If you wish to use a vanity domain, you'll need to point this domain to our Fastly CDN (prod.pugpig.map.fastly.net) using your DNS provider. An example entry would be:

Single feed:
reader.acme.com 300 IN CNAME prod.pugpig.map.fastly.net

Multiple feeds:
en.reader.acme.com 300 IN CNAME prod.pugpig.map.fastly.net
fr.reader.acme.com 300 IN CNAME prod.pugpig.map.fastly.net

Wildcard:
*.mydomain.com 300 IN CNAME prod.pugpig.map.fastly.net

Whilst we support vanity domains it can't be a deep url / vanity url. It has to be the root of a subdomain. 

Note: If you had done this in the past before we supporting HTTPS, you would have CNAME'd to global.prod.fastly.net - please update your CNAME if you need HTTPS. 

DISTRIBUTION SERVICE DOMAIN

When these are available you will log into the distribution service using:
<account>.admin.pugpig.com

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk