Is there an alternative to .htaccess for GitHub Pages?

Question

I understand that .htaccess is not supported by GitHub Pages. Is there an alternative for password-protecting particular directories for websites hosted by GitH

Answer 1

I'm using a 404.html to redirect users from old S9Y index.php to my new blog on Github Pages. Check this commit: https://github.com/lionello/lionello.github.io/commit/c175f6524a53e29aea1890c8a758afd0e8944852

Answer 2

Although you can't use .htaccess or .conf, Github has instructions on how to use the Jekyll Redirect From plugin.

https://help.github.com/articles/redirects-on-github-pages/

Answer 3

"Unfortunately, GitHub pages only supports static pages. There is no way to make it execute server-side code and thus it's impossible to protect your pages with any kind of authentication scheme. If you expand further on why you need to password-protect your pages, maybe I can help you find a workaround."

Source: https://webapps.stackexchange.com/questions/35692/is-there-an-alternative-to-using-htaccess-to-password-protect-subdirectories-in

Answer 4

This post comes out at the top of web search when you look for .htaccess redirects in github pages. I am going to answer this question in that sense.

One option is to use a DNS redirect instead. You do this by putting a file named CNAME in the project's root directory (not sure if it works in a subdirectory). Just put the redirection URL in the file. However, there are a few limitations, e.g. you can only redirect to a website's root.