Use cdn.privacytools.io for static resources #1936
No reviewers
Labels
No Label
🔍🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#1936
Loading…
Reference in New Issue
No description provided.
Delete Branch "cdn"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
You'd have to build locally with
JEKYLL_ENV=production bundle exec jekyll serve
orJEKYLL_ENV=production bundle exec jekyll build
to see the changes yourself, since the CDN URL should not be used in a development environment like NetlifyNice, could we also update the Readme build instructions to include this PR’s description? Helpful for future reference.
Why would we need a CDN though?
We could, although it doesn't make sense to load from the CDN in development. Because if you add a new image or whatever to your local fork, the CDN won't display it obviously, it will only load assets on the webserver. So really you'd only set
JEKYLL_ENV=production
when building the live website, or if you just wanted to see the CDN in action for some reason (like you might with this specific PR). But otherwise I'm not sure it's particularly helpful information.Ah that makes sense, okay, I was mistaken; we can leave the Readme as-is.