3 ms·

I came here to ask why these instructions didn’t just use GitHub pages. Especially since it seems it is targeted toward a person that this is a stretch for, and

I came here to ask why these instructions didn’t just use GitHub pages. Especially since it seems it is targeted toward a person that this is a stretch for, and GH pages would be easier. So anyway, downtime is one reason I suppose. Are there others?

whimsicalism 5y ago
I seem to recall from my experience that if you want to have a custom domain and subdomain, they can't both be on gh-pages but they can be on Cloudflare. Don't really remember what the hurdle with gh-pages was though.
the_arun 5y ago
I wish github supported comments on any file in the repository with a preference to turn it off. That alone is sufficient in most cases. OR There is a way to make GitHub pages to support commenting by default. Currently, it is a pain to run after third party tools for commenting. Is it so difficult to make already existing commenting feature to work on pages or regular files?
codazoda 5y ago
I use GitHub pages with no build step (GitHub handles that). I use my repos root folder for my page content, starting with index.md. I have a custom domain and just point the a record or cname at my GitHub address or IP. Works great for me and I haven’t noticed a lot of downtime, but I don’t really monitor either. Edit: It is a little slow to build when you make changes. My changes take a minute or two to appear on the site.
Brajeshwar 5y ago
Another thing I remembered, was the support for newer Jekyll version and plugins. I had everything running locally and it failed on GitHub Pages without any error anywhere. It turned out to be that I need to step back few versions with Jekyll (and I think some Github approved plugins). I’m fine with that but the lack of error why that is happening was hard for me to assume. Last year, I moved my site[1] (a pretty heavy content with lots of text files from two decades), and I really like Hugo. It was fast and can compile my site quick enough. Jekyll still crawls but I was ready to live with it as I can just write in MarkDown and don’t worry about compiling every time. However, the downtime was the reason I stopped using GitHub Pages. 1. https://brajeshwar.com/2021/brajeshwar.com-2021/ https://brajeshwar.com/2021/brajeshwar.com-2021/
nunez 5y ago
I host my Hugo blogs on S3 at the moment because I wrote a deployment engine that targeted S3 initially. I refactored it recently so that it can deploy pages anywhere, so theoretically I could deploy to GH Pages or anywhere, but S3 works well enough for me.

whimsicalism 5y ago

I seem to recall from my experience that if you want to have a custom domain and subdomain, they can't both be on gh-pages but they can be on Cloudflare. Don't really remember what the hurdle with gh-pages was though.

the_arun 5y ago

I wish github supported comments on any file in the repository with a preference to turn it off. That alone is sufficient in most cases. OR There is a way to make GitHub pages to support commenting by default. Currently, it is a pain to run after third party tools for commenting. Is it so difficult to make already existing commenting feature to work on pages or regular files?

codazoda 5y ago

I use GitHub pages with no build step (GitHub handles that). I use my repos root folder for my page content, starting with index.md. I have a custom domain and just point the a record or cname at my GitHub address or IP. Works great for me and I haven’t noticed a lot of downtime, but I don’t really monitor either. Edit: It is a little slow to build when you make changes. My changes take a minute or two to appear on the site.

Brajeshwar 5y ago

Another thing I remembered, was the support for newer Jekyll version and plugins. I had everything running locally and it failed on GitHub Pages without any error anywhere. It turned out to be that I need to step back few versions with Jekyll (and I think some Github approved plugins). I’m fine with that but the lack of error why that is happening was hard for me to assume. Last year, I moved my site[1] (a pretty heavy content with lots of text files from two decades), and I really like Hugo. It was fast and can compile my site quick enough. Jekyll still crawls but I was ready to live with it as I can just write in MarkDown and don’t worry about compiling every time. However, the downtime was the reason I stopped using GitHub Pages. 1. https://brajeshwar.com/2021/brajeshwar.com-2021/ https://brajeshwar.com/2021/brajeshwar.com-2021/

nunez 5y ago

I host my Hugo blogs on S3 at the moment because I wrote a deployment engine that targeted S3 initially. I refactored it recently so that it can deploy pages anywhere, so theoretically I could deploy to GH Pages or anywhere, but S3 works well enough for me.