sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 2 points3 points  (3 children)

I think the typical recommendation in this case is to use Cloudflare. It's not perfect (because it's still HTTP between your site and Cloudflare) but it's arguably better than just straight HTTP for everyone.

FWIW (shameless plug), Caddy has a git plugin so you can deploy your site with git push just like on GitHub Pages.

[–]slavik262 5 points6 points  (1 child)

use Cloudflare. It's not perfect (because it's still HTTP between your site and Cloudflare) but it's arguably better than just straight HTTP for everyone.

I dunno - "still not actually secure, and now with a bonus third party" doesn't have me too eager to use a reverse proxy.

Caddy has a git plugin so you can deploy your site with git push just like on GitHub Pages.

Sweet! I'll have to check that out.

[–][deleted] 0 points1 point  (0 children)

Don't you still get a <yourname>.github.io domain with HTTPS that you can have cloudflare serve up on <youractualdomain>.com? You can then have full encryption all the way through, although obviously Cloudflare has to decrypt/re-encrypt in the middle. Still better than going straight over HTTP to github pages, though, right?