6 ms·
I recently switched to gitlab because they have a much more straightforward pages publishing system. It works by setting up a (free) pipeline which can run arb
by aeharding 10y ago
I recently switched to gitlab because they have a much more straightforward pages publishing system.
It works by setting up a (free) pipeline which can run arbitrary code (docker-ized) that you set up in a .gitlab-ci.yml file that outputs build artifacts (static assets). These assets are then copied to gitlab's pages system.
Keeps your git repo clear of compiled stuff.
Works the same for public/private repos, too. Also has option for a custom domain SSL cert and 404 pages.
- ktta 10y agoYou can use SSL with GitHub pages if you're using CloudFlare. https://blog.cloudflare.com/secure-and-fast-github-pages-with-cloudflare/ https://blog.cloudflare.com/secure-and-fast-github-pages-wit... And I think it works only if you're using CloudFlare. I've always heard that you can't use custom domains and SSL but this works perfectly for me. But can anyone say why? Since my website is now hosted by github, I'm not so paranoid about my website going down or DoS attacks, and would like to not depend on CF anymore.
- daenney 10y agoIt doesn't only work with Cloudflare but if you want to use a custom domain + SSL you need to use a provider that can proxy the request for you. GitHub and their Fastly setup won't serve custom certificates for you and the *.github.io certificate wouldn't be valid for your custom domain.
- ktta 10y agoThe last sentence didn't really make sense to me. I assume Fastly is some kind of backend tool? So why is it only working with CF? when I visit my custom domain, I get a cert from sni75146.cloudflaressl.com but no cert related to github to be seen anywhere. I'm assuming the cert I'm seeing is valid because I'm viewing the page on CF's CDN, or am I wrong? Well, I think I'm better off asking objective questions, so: 1. Can I change by DNS provider to something else and have SSL work? 2. Can I keep using CF and use my own cert, say from LetsEncrypt? 3. Do GitHub and CF have something in common/mutual agreement so this works?
- angry-hacker 10y agoNo no and no. Custom certs are for Cloudflares paying customers. You can use Cloudflares with any host. It's basically a reverse dns proxy.
- ktta 10y agoPlease see your sibling comment
- daenney 10y agoFastly is not "some backend tool". Two seconds of Google'ing would reveal to you that they're a Content Distribution Network, aka CDN. They're the ones actually serving the content hosted on *.github.io: host user.github.io user.github.io is an alias for github.map.fastly.net. github.map.fastly.net is an alias for prod.github.map.fastlylb.net. prod.github.map.fastlylb.net has address 151.101.12.133 Cloudflare doesn't act as a CDN in this case. What Cloudflare does is proxy the request for you, and by virtue of them terminating the request they can serve an SSL certificate for your domain (either handed out by them or custom if you pay them).
- ktta 10y agoPlease see your sibling comment
- syshum 10y ago>>So why is it only working with CF? Because CloudFlare is basically a MITM Attack.... that is authorized by the website owner. http://blog.ricardomacas.com/index.php?controller=post&action=view&id_post=4 http://blog.ricardomacas.com/index.php?controller=post&actio... https://stirling.co/blog/cloudflare-mitm/ https://stirling.co/blog/cloudflare-mitm/
- ktta 10y agoPlease see your sibling comment
- 10y ago
- echelon 10y agoI'm not going to switch to Gitlab, because someone took my Github/Gmail/Twitter/HN handle. :(
- harperlee 10y agoWhy not just sign in with Gmail? The only reason that I see to not do it would be that someone could think that the other person is you - but that can happen nonetheless.
- sytse 10y agoDid you know GitLab has pages too? https://pages.gitlab.io/ https://pages.gitlab.io/ It supports many generators https://gitlab.com/groups/pages https://gitlab.com/groups/pages and custom domains work even on free accounts.
- nicky0 10y agoIt works by setting up a (free) pipeline which can run arbitrary code (docker-ized) that you set up in a .gitlab-ci.yml file that outputs build artifacts (static assets). These assets are then copied to gitlab's pages system. Doesn't sound very straightforward to me.