Add HTTPS mirror of Drazzy.com served through cloudflare #184
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ladyada
approved these changes
May 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@ladyada / @caternuson I did this last time to unblock us, instead of removing the Drazzy link, but maybe it can be a long term fix.
This is a domain that I own, with multiple year validity and auto-renew (with account credit and calendar reminders).
It's DNS is hosted on Cloudflare, and I've created a subdomain using Cloudflare proxy that points at Drazzy.com but using Cloudflare's SSL certificate (zero cost).
https://drazzy.good-enough.cloud (all url paths will forward)
i.e. the new BSP path becomes
https://drazzy.good-enough.cloud/package_drazzy.com_index.json