Introducing hugoArticleEncryptor - Encrypt Your Hugo Articles

New theme/module
1

I’m excited to share with you a humble tool I’ve developed called hugoArticleEncryptor. The motivation behind creating this tool was to provide a simple solution for those who wish to write personal diaries on their own websites while ensuring their privacy. With hugoArticleEncryptor, you can now protect your diary entries and keep them strictly for your eyes only.

The idea behind hugoArticleEncryptor draws inspiration from the renowned project called Hugo Encryptor. However, I took it upon myself to reimplement it in Go, creating a tool that generates a convenient binary file for direct usage. I wanted to make the process of encrypting your diary articles as effortless as possible, requiring minimal configuration and offering a straightforward user experience.

To learn more about hugoArticleEncryptor, I invite you to check out the project’s README. It provides detailed information on installation, usage, and configuration.

image
image1934×1377 66.2 KB

image
image1969×1329 77.2 KB

2 Likes
2

Hi there, and thanks for sharing,

Here is a quick feedback:

  1. I would prefer not to use binaries to handle sensitive data, especially executed through curl | bash (I didn’t review the source code you published along with the binaries, but I guess such install method could refrain others too)

  2. I’ve been working on a different – but closely related – project and I think your Readme should warn users about public repos.
    Here is the way I use Gitlab public pages while keeping the repo private: Gitlab: use public Pages while keeping the Git repo private | Roneo.org

  3. Staticrypt covers a similar usecase. I didn’t look in depth so far, did you? See GitHub - robinmoisson/staticrypt: Password protect a static HTML page, decrypted in-browser – maybe some interesting bits are out there.

Thanks a lot for sharing,
cheers

3

I’ve seen this mentioned a couple of times while reading Hugo stuff. I have my website in a public GitHub repo so beyond the obvious precaution of not putting sensitive stuff on a publicly accessible web page, I’m curious what the group wisdom is on this topic.

4

Hi there,

Thank you for your feedback and suggestions. I appreciate your insights and would like to address your points:

  1. The binary files I provided are automatically generated by GitHub Actions based on my code. They are primarily meant for convenience, especially when deploying on platforms like Vercel and Netlify. In my README, I also provide instructions on using the tool from the source code directly. I understand your concern, and I will make sure to clarify this in the README to provide users with both options.
  2. I want to express my gratitude for bringing up the importance of keeping the blog code in a private repository. It’s an essential consideration, and I will definitely include a reminder in the README to emphasize this aspect.
  3. Thank you for mentioning Staticrypt. It seems like an interesting project, and I will take a closer look at it.

Once again, I appreciate your feedback and the time you took to provide these suggestions. If you have any further thoughts or questions, please feel free to share them.

Best regards,

1 Like
5

@RoninTech

This advice is only relevant in specific cases. Here, the password is put plaintext in the Markdown file, with the shortcode {{< secret "password" >}}.
That’s why – in this case – it’s important to use a private repo.

1 Like
6

Really cool, thanks! :slight_smile:

What I liked about hugo_encryptor was the ability to protect only sections of a post instead of the whole page/post. Is this feature also planned in your version?