Just a geek, finding my way in the fediverse.

  • 0 posts
  • 39 comments
Joined 3 years ago
Cake day: June 11th, 2023
  • You’re correct.

    The only time I can think of that this approach wouldn’t work is if the quadlet config file specified a tag/version on the image setting besides latest. That is, if the quadlet file specified something like Image=docker.io/jellyfin/jellyfin:a_old_version. I usually stick with latest on mine.

    EG: Image=docker.io/jellyfin/jellyfin:latest

  • My company is pushing LLM code assistants REALLY hard (like, you WILL use it but we’re supposedly not flagging you for termination if you don’t… yet). My experience is the same as yours - unit tests are one of the places where it actually seems to do pretty good. It’s definitely not 100%, but in general it’s not bad and does seem to save some time in this particular area.

    That said, I did just remove a test that it created that verified that IMPORTED_CONSTANT is equal to localUnitTestConstantWithSameHardcodedValueAsImportedConstant. It passed ; )

  • Does borg need an entire python venv?

    I was looking at “modern” backup tools while back and when I saw borg was python I decided not to bother.

    Instead I focused on restic for a little while and then rsync was already there and I already knew the commands so… Rsync. Though I still have restic on my list.

  • Looks like you called it. Seems the container image(s) default to a subscription plan (“Starter”, free for <50 users) but apparently you can revert to the “Community Edition” which gets rid of it.

    Found this post over at the place we no longer speak of :

    Hello, I’m Gabriel Engel, the founder of Rocket.Chat. I want to clarify that there is no new limitation for community use. We’ve recently introduced a plan offering all enterprise features for free to groups with fewer than 25 users. For those with more users, you have the opportunity to try the enterprise features. After the trial period, the system will automatically revert to the community version. However, you have the option to bypass the trial in the admin settings. I emphasize that we are not imposing any restrictions; instead, we’re providing the enterprise version free to small teams and inviting larger teams to experience it. Let’s view this as the positive initiative it is. For more details, please visit our forum: https://forums.rocket.chat/t/introducing-the-starter-plan-free-access-to-premium-features-for-limited-scale-use/18736

    In the admin settings for your instance you can go to the “Subscription” panel and down at the veeeery bottom is a “Cancel Subscription” button (I’m on the free “starter” subscription, apparently). I’m assuming that’s how you back out of it.

    Once I have a chance to warn users that I’m about to do something potentially dramatic, I’ll test it out and see what happens.

    EDIT: Also found this in the RC forums (from 2 years ago) :

    Note, if you upgrade or install new version of RC, it will automatically put you at a Starter or Pro plan, to go to the community, go to Admin settings, remove the key and it will put you back to the Community version… It took me a while to figure this out :slight_smile:

    O, and the immediate next post is what I described above :

    I believe community is still available within v6.6.0, but new instllation will put you automatically to the Starter Plan. You need to cancel subscription going to Setting → Subscription → Cancel Subscription

  • RocketChat is pretty easy to setup with docker. I couldn’t get it to work in podman after many, many hours of trying despite the documentation saying it does. They have a dedicated podman doc page but I just hit problem after problem after problem. I was trying to do it with the containerized mongo as a PoC though - a lot of problems came from that (mongo connection). Maybe I’ll try again with a “real” db server. Root cause seemed to be networking differences between docker and podman.

    I found it really odd that your server has to get a registration key from their server… That part weirds me out.

  • I started a blog specifically to make me document these things in a digestable manner. I doubt anyone will ever see it, but it’s for me. It’s a historical record of my projects and the steps and problems experienced when setting them up.

    I’m using 11ty so I can just write markdown notes and publish static HTML using a very simple 11ty template. That takes all the hassle out of wrangling a website and all I have to do is markdown.

    If someone stumbles across it in the slop ridden searchscape, I hope it helps them, but I know it will help me and that’s the goal.