Not an ad, I’m not involved with Bento (or Stirling, for that matter). I’ve been unhappy with Stirling for a while (why do documents need to be uploaded to the server? That makes it really hard to safely host publicly. Why is it so slow? Plus, too many things are put behind a fucking paywall).

Learned about Bento this morning, tried it out, really liked it, spent an hour today packaging it for nixpkgs. It doesn’t quite have feature parity with Stirling yet, but at least for me, everything I need is there, it’s fast, and it keeps processing in the browser. Like, not even joking: the output of the build process/nixpkg are just a couple of static HTML files and some WASM. No server-side components at all. Really refreshing to see.

  • seang96@spgrn.com
    link
    fedilink
    English
    arrow-up
    10
    ·
    edit-2
    2 days ago

    I want to swap to this but also want to do a few PRs but haven’t had the time.

    • Dockerfile exposes port 80 and runs as root
    • Less concerning, but dislike it, the scripts and CSS use remote cdns rather than being bundled locally

    Otherwise I am excited for this. Stirling doesn’t really support replicating even with license and its fat image takes up a bit of my disk space for images.

    • smiletolerantly@awful.systemsOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      2 days ago

      Yeah those are good points. Also noticed the CDN thing, it’s a bit annoying for a privacy-first project… But should be an easy fix 😄

      Stirling’s backend is Java. So, yeah, heavy and slow sounds about right.

      • seang96@spgrn.com
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 day ago

        Yeah very exciting project and to be honest a lot of popular services run as root by default. That said this ones harder to change from port 80 without changing the image. Could mount a nginx.conf to override probably though.