Works fine for me. It’s you.

Its features are much more than mimicking your browser bookmark functionality.

The most important feature to me is the offline archiving of the target link/page. Link rot is real and content can change. Capturing the site as it is when I link it means the info I wanted is now safely stored.

There’s also the multi-user features. A family can centralize and collaborate on links.

Here’s the Features list from the projects GitHub page.

Features

• 📸 Auto capture a screenshot, PDF, and single html file of each webpage
• 📖 Reader view of the webpage, with the ability to highlight and annotate text
• 🏛️ Send your webpage to Wayback Machine (archive.org) for a snapshot (optional)
• ✨ Local AI Tagging to automatically tag your links based on their content (optional)
• 📂 Organize links by collection, sub-collection, name, description and multiple tags
• 👥 Collaborate on gathering links in a collection
• 🎛️ Customize the permissions of each member
• 🌐 Share your collected links and preserved formats with the world
• 📱 Native iOS and android mobile apps
• 🔍 Full text search, filter and sort for easy retrieval
• 🌓 Dark/Light mode support
• 🧩 Browser extension (star it here!)
• 🔄 Browser Synchronization (using Floccus!)
• ⬆️ Upload from SingleFile (check out the guide)
• 🔐 SSO integration (Enterprise and Self-hosted users only)
• 🍎 iOS Shortcut to save links to Linkwarden
• 🔑 API keys
• ✅ Bulk actions
• 👥 User administration
• 🌐 Support for other languages (i18n)
• 📁 Image and PDF uploads
• 🎨 Custom icons for links and collections
• 🔔 RSS feed subscription
• ✨ And many more features (literally!)

+1 for PocketID

+1 for Renovate. It’s not a drop-in replacement for Watchtower, but it allowed me to create a robust CI/CD pipeline. And, it can be centrally run, instead of having Watchtower running on every Docker host I have.

The biggest concern here would be 1) have you installed the Nvidia container toolkit, and 2) how are you passing the GPU into the Jellyfin docker container.

I’ve got an Ansible-playbook that takes care of the Nvidia stuff. I’ve also got a compose file I can share. Will edit this post when I can provide a link.

As the owner of several X9 boards, I can confirm the answer is ‘no’. Java is the only option for this generation.

This is my strategy as well. Except, I will find the domain on sale elsewhere then transfer it over to CloudFlare.

Set the Immich instance to run as the UID that owns the media files?

Respectfully, you and I are basing our feedback on incomplete information. That being said, it absolutely could be a hardware problem because the further get into the boot process, more data is loaded from disk into RAM. There isn’t some point beyond which hardware is no longer a concern.

Your point about dmesg is a valid one, provided you can even get to a login prompt. Otherwise, you’re captive to the terminal output on boot.

I reserve the right to be wrong, but my money is on bad RAM. If one wants to test the hardware without taking things apart, booting to a live USB/CD is a good option.

This seems like a hardware problem. Hardware freezes would not be caused by hardware pass through to VMs. Test your RAM. Check for loose PCI cards, etc.

You’re discovering that there’s ALWAYS a single point of failure. Even if every service is fault tolerant, you likely have a single network or power infrastructure. So, you have to figure out what you’re willing to tolerate. You could look into CARP or keepalived to make your reverse proxy more resilient. It’s probably overkill for a homeland, but could be a useful learning exercise.

Majority of the code is python and vue? And, what problem is this trying to solve? What does it do that other solutions don’t? I read through the repo docs and it’s just not clear. WTF does it mean “I don’t lose control” over storage on cloud storage?! If it’s on the cloud, you are not in control. May the downvotes rain down on this.

Hire a management company and use the software they have. For the little engagement you’re going to have, it’s worth it to outsource the management of it to someone else.

/docker/compose/<project> for compose and env files

/docker/data/<project> for data to be retained

I let the docker overlay handle all the volatile data.