arch1e

Good point! We use a database (SQLite or Postgres) to enable more advanced features like versioning, collaboration, and access control, which aren't easily managed with static files alone. The database also allows us to scale better for teams with frequent updates.

While it does limit deployment to platforms like GitHub Pages, Kalmia is designed for teams that need more than just static documentation—think of it as a middle ground between static site generators and fully dynamic CMS solutions. For purely static sites, there are other great options out there, but Kalmia focuses on more interactive, collaborative documentation.

That said, we’re actually interested in providing an option for users to export and deploy it to platforms like GitHub Pages or similar, so stay tuned for future updates on that!

We saw nearly the same reduction in build times (~80-90%) as quoted in the official RsPress documentation. Keep in mind, we're using MDX, not just plain Markdown.

Source: https://rspress.dev/guide/start/introduction#build-performan...

Thank you so much! Great question. Kalmia actually borrows elements from all three, but in different ways:

* On the GUI side, it leans heavily towards TinaCMS. We even considered using TinaCMS directly (Tinasaurus (https://github.com/tinacms/tinasaurus)) but ultimately built our own for better integration with our backend.

* For the backend (MDX -> HTML) generation, it's very similar to Docusaurus. We use a tool called RsPress, which is part of the RsBuild/RsPack tool suite. It's relatively new, but because it's written in Rust, it's much faster than Docusaurus. (Fun fact, if you look at the commit history you will see that we initially used Docusaurus but then migrated away from it!)

* Wiki.js is extremely extensive, but it’s dropping support for SQLite, which was a big factor for us. Also, its frontend for documentation doesn’t feel as fast as RsPress (you can try ours out on kalmia.difuse.io it's hosted on single core azure server). The biggest reason we didn’t go with Wiki.js was the versioning system—it felt clunky (or non existent for entire docs?). In Kalmia, versioning the entire documentation is just a one-click process.

So, in short, Kalmia combines a TinaCMS-like editing experience with Docusaurus-like static site generation, but with speed advantages from the latest Rust based tooling for SSG.

Is there a write up or something I can use to make this work on my VF2?

Linux compatibility is a great feature, but as a heavy user of Firefox and KVM, I find some alternatives in FreeBSD like Bhyve a bit lacking, especially in areas like PCI passthrough. For example, it can be unreliable, even stopping to work after the system wakes up from sleep.

Also, while FreeBSD's flexibility is impressive, allowing the use of Linux binaries, it's worth noting that there aren't many scenarios where using FreeBSD on Linux without a VM is necessary. What unique capabilities does FreeBSD offer that Linux doesn't?

Additionally, the BSD license is indeed powerful, allowing companies like Sony, Nintendo, NASA, and Apple to use and modify FreeBSD without the obligation to contribute back. While this has broadened FreeBSD's usage, the license can also be seen as a double-edged sword because it diminishes the incentive for these companies to contribute back to the community, which could potentially slow down the development and improvement of FreeBSD in certain areas.

FreeBSD has its merits, but comparing its jails to Docker isn't entirely fair. Many applications well-suited for systems like TrueNAS often lack documentation for running within a FreeBSD jail, or on FreeBSD in general—Jellyfin is a case in point.

Additionally, I recently attempted to install FreeBSD on my ThinkPad, which has an Intel Wi-Fi chip, and found that software support remains lacking. This extends to other features like Widevine, making it impossible to use streaming services such as Netflix, Prime Video, or Spotify.

For FreeBSD to approach even a fraction of Linux' mainstream adoption, significant development and support improvements are necessary.

Or the market already priced it in?

Weird how they didn't mention openwrt at all

My country is cracking down on civil liberties (I'm not talking the ability to not take certain vaccines), I'm talking about religious freedom among other things and crypto like XMR gives me a way to make sure I am able to buy stuff like Mullvad VPN (again for privacy) without going through a centralized payment processor. This is just one instance though, I even get domains from njall.la now with XMR/crypto and enjoy a lot of privacy benefits (coming from godaddy)