Today, we're excited to announce the release of Linkwarden 2.12! đ„ł This update brings significant improvements and new features to enhance your experience.
For those who are new to Linkwarden, itâs basically a tool for saving and organizing webpages, articles, and documents all in one place. Itâs great for bookmarking stuff to read later, and you can also share your resources, create public collections, and collaborate with your team. Linkwarden is available as a Cloud subscription or you can self-host it on your own server.
This release brings a range of updates to make your bookmarking and archiving experience even smoother. Letâs take a look:
Whatâs new:
đ«§ Drag and Drop Support
One of our most requested features is finally here! You can now drag and drop Links onto Collections and Tags. This makes it much easier to organize your bookmarks and keep everything tidy.
đ€ Upload from SingleFile
SingleFile is an awesome browser extension that allows you to save complete webpages as a single HTML file on your device. As of Linkwarden 2.12, you can upload your saved links directly from the SingleFile browser extension into Linkwarden. This allows you to easily save articles which are behind paywalls or require authentication directly from your browser.
To use this feature, simply install the SingleFile extension, and then follow the documentation.
đ Progressed Translations
Weâve made significant progress in our translations, with many languages now fully supported. If youâre interested in helping out with translations, check out our Crowdin page.
â
And more...
There are also a bunch of smaller improvements and fixes in this release to keep everything running smoothly.
Full Changelog: https://github.com/linkwarden/linkwarden/compare/v2.11.8...v2.12.0
Want to skip the technical setup?
If youâd rather skip server setup and maintenance, our Cloud Plan takes care of everything for you. Itâs a great way to access all of Linkwardenâs featuresâplus future updatesâwithout the technical overhead.
We hope you enjoy these new enhancements, and as always, we'd like to express our sincere thanks to all of our supporters and contributors. Your feedback and contributions have been invaluable in shaping Linkwarden into what it is today. đ
No what I said isn't about user registration; it's about adding these to the
docker-compose.yml
:to prevent running as root and making the file system read-only. The API needs to be exposed without a VPN or other proxy login since my parents' can't handle that, so if I was able to implement these recommended security steps I'd feel like I could open up the container to the internet at large without too much risk.
Per this issue https://github.com/linkwarden/linkwarden/issues/799 it seems like there's a lot of steps to take to get these settings to work.
It would be also ideal if I didn't have to give the container (but not a deal-breaker):
as the issue also states is required for the headless chrome scraper browser.
I am using it internally now and it's really good, but to open it up for my parents (which I think they'd dig) I'd definitely want these security settings on without major issues. Linkwarden is an internet-facing application so these recommended security practicies are in its wheel-house, feature-wise, as well.
Hope that helps clear up my comment!
Oh I see, thanks for letting me know! Yes that's actually requested and we'll be getting to it sometime.
Great to hear! Itâs seriously slick and âjust worksâ. With those security features up you can tout them on the cloud offering too :)
So I have mine running in a podman quadlet. It runs as root in the container but it is unpriviledged. Mine has NET_ADMIN and SYS_MODULE but I honestly can't remember why... SYS_ADMIN seems extreme though
Edit: I'm dumb, and the linkwarden container has no capabilities set. I set them for the tailscale container which definitely needs it.
Care to share your quartet? Iâm just getting into the quads with trixie out - and I havenât gotten this working yetâŠ
The permissions do seem intense; if youâre getting by without maybe those arenât quite needed!
Sure thing, I'll edit this reply when I get back to my computer. Just note that I also have a tailscale and nginx container in the pod which are not necessary.
You'll see my nginx config which reverse proxies to the port the service is running on. On public servers I have another nginx running with SSL that proxies to the port I map the pod's port 80 to.
I usually run my pods as an unpriviledged user with
loginctl enable-linger
which starts the enabledsystemctl --user
services on boot.All that being said I haven't publically exposed linkwarden yet, mainly because it's the second most resource intensive service I run and I have all my public stuff on a shitty vps.
Edit: My opsec is so bad hahaha
Edit2: I just realized the caps I gave were to the tailscale container, not the linkwarden container. Linkwarden can run with no caps :)
I added the tailscale stuff back
files:
linkwarden-pod.kube:
linkwarden-pod.yml:
I also have a little helper script you might like
copy.sh:
Thanks! Thisâll def help me get tooled up for podman :)