1

I currently have a blog set-up through Github using Jekyll. At first, it started out to be a public blog, but recently it has become more private for me(i.e., blogging for therapeutic's sake and mental health). I wanted to make this blog site private.

I understand that you can make a repository private, but I want to continue using my published blog's website interface which is currently public. Is there a way around this? If not, what alternative options are there? (I tried using Blogger, and though I like its privacy settings, the published website interface is pretty weak.)

ayjay
  • 1,272
  • 2
  • 16
  • 25
  • 1
    Does this answer your question? [Private pages for a private Github repo](https://stackoverflow.com/questions/10748082/private-pages-for-a-private-github-repo) – Ente Dec 10 '19 at 19:55

2 Answers2

0

You can have password protected pages on CloudCannon. You can also add a htaccess file on your custom hosting environment.

Mr. Hugo
  • 11,887
  • 3
  • 42
  • 60
-1

You can try the encryption route. Here, the name staticrypt really says everything (I have a demo here). It allows you to create a password for each page for your website. It used AES-256 encryption, so as far as I am concerned, a long password should suffice. You will be the only one to view the webpage. You can also have js on the webpage etc., so I believe you can maintain whatever you have on your website, (the address, format, etc.) while restricting access.

In the readme.md of staticrypt:

Disclaimer if you have extra sensitive banking data you should probably use something else!

StatiCrypt generates a static, password protected page that can be decrypted in-browser: just send or upload the generated page to a place serving static content (github pages, for example) and you're done: the javascript will prompt users for password, decrypt the page and load your HTML.

It basically encrypts your page and puts everything with a user-friendly way to use a password in the new file.

AES-256 is state of the art but brute-force/dictionary attacks would be trivial to do at a really fast pace: use a long, unusual passphrase.

To do that, first, generate your webpage as an HTML file and use this link (or locally) to encrypt your HTML file. Download the HTML file and upload it to your server.

I don't think GitHub allows you to make a "private" Github-pages.

wooohooo
  • 576
  • 1
  • 4
  • 15
  • What is "the encryption route"? How does it work together with Jekyll? – Nico Haase Dec 12 '19 at 14:46
  • updated the answer. It does not work with Jekyll directly. You have to generate the HTML file from markdown first, but that could be done locally. The `staticrypt` takes over from there. – wooohooo Dec 12 '19 at 14:51