doks VS juicefs

He just recommended that I use HUGO to set up a simple, static website for a non-profit that could be hosted for free on Github and would be fairly simple for me to update using markdown. It sounded like a wonderful idea. He downloaded HUGO & set up WSL for my Windows Terminal for me & I was pretty much on my own to find tutorials for Git & Github, VSCode, Hugo & the Hugo Doks Theme.

Recently I started to configure my digital garden. Foam is a good option, Hugo Doks, No Style Please, Git-Wiki, Researcher, Thinkspace, and other themes are good for zetteltasken pages.

Take a look at this theme for documentation. https://getdoks.org/

Thanks, yes of course — https://getdoks.org/.

Download Doks theme for Hugo

Download Doks Doks demo site Minimum Hugo version: 0.80 GitHub stars: 952 License: MIT

I am trying to create a second docs page, e.g. called `docs`, that should have the same layout as the `docs` page. I managed to do this by following [this](https://github.com/h-enk/doks/discussions/173) discussion topic. I managed to add the second page, all with correct menu entries and the sidebar showing correctly.

Feel free to download and try JuiceFS 1.2-beta1 here. If you have any questions, join JuiceFS discussions on GitHub and our community on Slack.

Support for Kerberos keytab files

JuiceFS under the Apache License 2.0, is a high-performance POSIX file system optimized for cloud-native environments. It stores data in Object Storage (e.g., Amazon S3) and metadata in databases like Redis, MySQL, or TiKV. JuiceFS integrates massive cloud storage with big data, machine learning, and AI applications efficiently, akin to local storage. It features full POSIX and Hadoop compatibility, S3 interface, Kubernetes support, and shared file storage for numerous clients. Some cool features are - strong consistency, scalable performance, data encryption, global file locks, and compression with LZ4 or Zstandard.

To improve the handling process of capacity overrun, the JuiceFS client supports deletion operations in the case of Ceph cluster fullness (see related code changes in JuiceFS Community Edition). Therefore, for newer client versions, there is no need to use set-full-ratio for temporary adjustments.

If you have any questions or would like to learn more, feel free to join discussions about JuiceFS on GitHub and the JuiceFS community on Slack.

The architecture image shows GCS and others, so I suspect it does.

https://github.com/juicedata/juicefs#architecture

See also: JuiceFS: https://juicefs.com/

Adds a DBMS or key-value store for metadata, making the filesystem much faster (POSIX, small overwrites don't have to replace a full object in the GCS/S3 backend).

Almost certainly a better solution if you want to turn your object storage into a mountable filesystem, with the (big) caveat that you can't access the files directly in the bucket (they are not stored transparently).

JuiceFS can do the same thing as s3fs-fuse, but better. Because it supports robust data consistency and caching policies to improve performance.