CDN
Optional CloudFront URL rewriting — and S3 only if WordPress will not stay online.
CDN support is optional. Open Settings → Tivlo Static Site → CDN & Media Sync. The tab can rewrite media (and CSS/JS) URLs to a CloudFront domain and, if you need files off WordPress, copy them to S3.
If you only wanted faster HTML on the host you already pay for, you can ignore this whole section. Tivlo is already serving files from disk. A CDN here is for images and assets, not a second static generator.
Tivlo SSG does not provision AWS resources. You create the CloudFront distribution (and S3 bucket, if you use Scenario 2) in AWS, then paste the CDN domain here. After you click Save CDN Settings, run Build Console → Full Rebuild so exported HTML picks up the new URLs.
CDN & Media Sync
Fields on the CDN tab: rewrite, domain, invalidation, and S3 sync.
Live site origin
CloudFront origin is your public WordPress site. No S3 required.
Static + S3
Edit locally, publish HTML elsewhere, media and CSS/JS from S3.
Which scenario
| Live site origin | Static + S3 | |
|---|---|---|
| WordPress | Public, always online | Can run locally for editing |
| S3 Media Sync | Off | On |
| CloudFront origin | Your live website | Your S3 bucket |
| Static HTML export | Optional | Required for publishing |
| Best for | Faster media on a live WP site | WordPress does not need to stay online for visitors |
CloudFront cannot use localhost as an origin. AWS will not fetch your
laptop, no matter how nicely you ask. If WordPress is only on your
computer, use Static + S3 (or leave CDN off and serve media from
whatever host receives the HTML).
Same-origin sites
If Tivlo already serves HTML from this WordPress install and you do not need a CDN, leave the CDN tab off. See Serving & output.
How is this guide?