Every time someone asks "will this run on a 1 GB VPS?" the answer is a guess, or a vendor minimum that was written to be safe rather than accurate. So I measured it.

Same box, same method, every app: install, start it, let it settle for 60s at idle with no clients connected, then sum the RSS of the whole process tree. No Docker overhead in the numbers — these are the apps themselves.

Things I did not expect:

• The *arr apps are all the same size. Sonarr, Radarr, Lidarr and Prowlarr land within 5 MB of each other (188–193 MB). That is not a coincidence and it is not the app — it is the .NET runtime setting the floor. Which also means the folklore of "budget ~2 GB for an *arr stack" is roughly right, and I say that as someone who started this expecting to debunk it.
• Go binaries are absurdly cheap. File Browser, Gotify, ntfy, PocketBase, Caddy and Navidrome together idle at about 181 MB — less than one Sonarr.
• Grafana's 512 MB minimum is honest. At 172 MB idle it has real headroom needs once dashboards start querying. Not every vendor minimum is padding.
• Node apps cost you. Uptime Kuma at 136 MB is ~8x File Browser for a job that is not 8x harder.

Caveats, because they matter: this is idle RSS, not what you need under load. Databases, media transcoding and indexing all blow past these numbers. Treat it as the floor, not the budget. My own rule of thumb from this: sum the idle figures, add ~300 MB for the OS, then add 30% headroom — that has matched what actually fits so far.

Raw data is free under CC BY 4.0 (CSV and JSON), plus per-app pages with the exact commands used so you can reproduce or dispute any number:

https://smeltworks.com/smallserver/

CSV direct: https://smeltworks.com/smallserver/smallserver-dataset.csv

Happy to take corrections — if a number looks wrong for your setup I would rather fix it than defend it. Also taking requests for what to measure next; Jellyfin and Immich are the two I keep getting asked for.

that hard drive prices return to normal and think about all the things i can build.

silliness aside, i honestly sit there and plan it out. i wish i pulled the trigger and started earlier. i actually bought two mini pcs before this mess and have one setup running proxmox. o have this beautiful jellyfin -> jellyseer -> radarr/sonarr -> sazbd -> gluetun -> newsreader setup on proxmox and i founf 1 8tb wd red plus on sale that i put in a ugreen nas running truenas and its filling up quickly.

i wont move to nextcloud until i get a second drive for mirroring. i still have to find a place to backup those future files as well.

there is not really a point tp this post except i know people here feel my pain. how i dream of buy a few 12 tb drives.

for now i find stuff and put price alerts on them. o have tried ebay but i dont always get what i pay for. like buying wlanlisting that says wd red plus cmr and getting a wd red (non plus) smr.

i fantasize about the cool rack setup i could build. right now everything, jellyfin stack, home assistant, glance dashboard, pteradactyl, netbird , anf any vm i want to play with all on one proxmox mini pc. next comes books

sorry for the rant but maybe you can relate

Of the many useful things I could do with my spare time instead I'm setting up a Lemmy instance because why not. The scope of this is definitely greater than any self-hosting I've ever attempted, so please feel free to tell me just how much trouble I'm in. I'm just giving the broad strokes to see if I've made any crucial errors (other than deciding to do this at all).

And if this is a completely wrong place for a post like this or I'm missing data I'm supposed to include I apologize, I probably need a sanity check, in more ways than one.

First limitation, I'll be hosting it on an existing Linux Mint box acting as a file share mostly and occasional gaming PC/movie streaming box. Its hardware is overkill for this, I do not anticipate issues when it is in use. It receives regular updates and weekly reboots, instance will be set to automatically restart. NVMe with loads of space for local storage, RAID SSDs for data offload/backup.

Second limitation, I hate Cloudfare and Oracle. I do not want to use either of them.

Third limitation, money. Cheaper is better. I have a URL picked out and a registrar which will give me the cheapest long term option, in case I actually keep this thing going.

Last limitation, I'm already in over my head so I'll be relying on a lot of googling and probably some chat bots to figure things out as I go through the actual deployment process. What could go wrong?

So, Lemmy hosted on Linux Mint box using Docker containers. ISP is a good one for this I'm told, no CGNAT, largely stable public IP but I'll have a script running in case it does change. Confirmed ports 80/443 are open. Using Caddy for the HTTPS. Closed registration to start, if by some miracle I make it to actually wanting to allow additional users it will not be fully open, and I'll use Brevo for the email SMTP. Security wise I know I'm making it harder for myself by exposing my IP, I'm going to have UFW running and Crowdsec to help keep incoming bad traffic out.

Down the line I'll get Lemmy updates, backups, retention rules in place/automated, and make decisions on federation, etc. Thoughts?

I’ve got an HPE R1500 G3 UPS that I was given and refurbed to be useable. Now that it’s in the rack and running, I want to fix things up a bit more.

Unfortunately the ears were not given with the UPS and I’d like to replace them. However everything I’m finding is listed as intended for switches/routers. Can anyone point me in a good direction, other than just watching eBay, where I might be able to get some replacement ears?

TIA

Edit: The ears WONT be bearing any weight, it’s just to keep it in place so it stays in until I want it out. I know it’s too heavy for ears alone.

I'm looking for a server I can host in my home that has a simple ui where I can put in URLs for download and have them all show up on my Jellyfin. Bonus if there is VPN support.

Update: Thanks to everyone for the suggestions! Several projects to check out: youtube-dl, pinchflat, ytptube, metube, tubearchivist, yt-dlp-webui, ytzero, igloo, youtarr

Birdnet-go is a real-time sound analyzer that detects bird species. It can take in audio from microphones. I set mine up to stream audio from my security cameras that I already had installed. There's even a Home Assistant App, if you're using it.

I live in a more suburban/semi-urban environment, but was really surprised to so many different bird species.

My blog has been up and running for a few months now and I wanted to have a better idea of what sort of visitor numbers I was getting but as it is a blog about FOSS, self-hosting and privacy I wasn't just about to hand data to Google.

I managed to set up a self hosted instance of Rybbit but it was a bit heavier resource wise than other options I have looked at so I had to have a major overhaul in my Proxmox node layout!

Omada platform was found to be vulnerable in several ways

For context: I have 0 programming, coding, etc. related knowledge.

For some months I've been dedicating time into setting up a Homelab that hosts music, movies, maybe home security (Frigate, I suppose), minecraft servers (or maybe other games too) and maaaaybe local AIs (if I get a better system), in that order, from more to less important. Some of the caractheristics that I prioritize are: privacy first, Zero third-party exposure, disk data encryption, self-hosting, FOSS priority perspective, trying not to compromise in any way my home network-using devices through all the process. Since, as I said, I have 0 programing or even Linux experience, I've done all this process guided by a local ran AI (Qwen 3.6), YouTube videos and forums (not the perfect formula for a cybersecurity safe environment, I know).

In an old laptop (Acer Aspire ES15-... with AMD A6-6310 / 16GB RAM) I've installed Linux Debian Trixie 13 (GNOME) with Docker and CasaOS with Jellyfin (for movies, it worked), Navidrome (for music, also worked) and recently Netbird, this one to connect into the local network from outside my home net, which kinda worked, but not as I expected it to work.

And this is where I feel I'm stuck. My main absolute priority the whole time setting this all up was being able to stream music from my homelab in my phone from everywhere in the world as long as I had internet connection, but when I managed to achieve that connection after soooo many hours and even stream music from my phone only with mobile data, it needed like 1 minute to load 3 seconds of a song, so it's not enough at all. After seeing this, I've reseted all netbird data so I can do a clean install.

I need help with the process of setting this (I believe it's a VPN) up in a way that it is Self-hosted, secure and fast enough so I can make it all achieve my expectations. Any video, forum thread or personal recomendation that you can give me will be so much appreciated.

Summarizing it a little, this is what I was trying to achieve:

CasaOS Architecture: Netbird (FOSS WireGuard mesh) + (maybe) Caddy Reverse Proxy + (maybe) Internal PKI + (maybe) LUKS Encryption Security Model: Zero port forwarding, outbound-only private tunnels, device-by-device approval, end-to-end HTTPS, full data-at-rest encryption.

Let me know if I'm missing any important information and I will do my best to share it.

Thank you so so much in advance!!

Hello beautiful people of this community!

I asked for your help a month back about setting up OPNsense on Proxmox. I went through all the comments in the post.

I got a bit distracted by IRL commitments but I sat down with it properly last week. After a lot of studying, and a bit of trial and error, I have done it!

My Journey

This was my first time with Proxmox, so I spent a few weeks with Proxmox initially before undertaking OPNsense. OPNsense took me a week to install and deploy. I did a staggered deployment over multiple days, i.e., installed the VM first, check connectivity, check DHCP, and then make it part of my homelab.

Architecture

The diagram might look complicated, but it's simple.

My host has 3 interfaces, onboard NIC and a dual NIC card. I made a LAN and WAN interface out of the dual NIC card, and made the onboard NIC as a management interface. I connected all of the interfaces to dedicated Linux bridges and the underlying OS/VMs only use the Linux bridges. The onboard NIC is only used to configure Proxmox in case something catastrophic happens. The other VMs can communicate with the OPNsense VM via the virtual LAN interface.

I initially was thinking of going through the pass-through option, but after some research, I saw the upsides were very low and you lose a bit of flexibility.

Challenges

1. KEEP TRACK OF YOUR NIC TO LINUX BRIDGE MAPPING - This caused me a lot of stress and trails. I thought I was trying to ping the LAN interface, was connected to the WAN bridge.
2. The Chicken & Egg Problem - During boot, Proxmox needs an IP but the DHCP service inside OPNsense is not up yet. Without that IP, I cannot log into Proxmox. I solved it using a hard-coded IP for Proxmox.
3. Options galore - Coming from standard routers, OPNsense is a different beast; it has so many options that it becomes a crazy labrynth. Had to read again and again to understand what the options meant.
4. Where is dark mode? - The first change that I wanted to do was set dark mode and I don't know why but it an ungodly amount of time for something so simple. It's present in such a weird location (System -> Settings -> General -> Theme)
5. This ain't Kansas anymore - This is OpenBSD, not Linux. So the same commands won't work. There is drill, no dig.
6. PLEASE CLICK APPLY - Many times I just forgot to click Apply after making a change and I got super confused.
7. DNS, YOU DEVIL - This was the setting which made me question my own sanity. I have a simple but non-standard setup for DNS. I am running Pihole (Ad-blocking + Local domains) + Adguard DNS Proxy (Supports encrypted DNS). I wanted to tell OPNsense "Hey, use this IP to resolve all internal and external DNS queries". OPNsense was just not having it. It took me two days of experimentation to finally figure out the right approach (Disable WAN populated DNS, turn off Unbound, and use DHCP options).

Thanks to these people

Their comments really helped me out (Technical and encouragement)

• @chief@lemmy.zip
• @dbtng@eviltoast.org
• @zarathustrad@lemmy.world
• @possiblylinux127@lemmy.zip

Closing remarks

I am still documenting the entire process. I will publish the entire process of how I got a bare Lenovo M720Q working as a virtualized OPNsense router. Remember, if I can do it, anyone else can do it.

Heya, I just wanted to post here before doing something that puts my stuff out on the internet for anyone to see 😅

So I have a basic, still in-configuration homelab network going on. It's Modem --> OPNsense router --> Ubiquiti switch --> Openwrt AP. DNS and DHCP (via Dnsmasq) are working right now, each VLAN (Home Devices, IoT, and Guest) can access the internet. But I'm still tinkering and doing firewall stuff, so sometimes I reactivate the ISP router and switch back to that until I have everything perfect enough to not bother my family

I have a Proxmox homelab that I've been running services like Jellyfin and Immich in a Docker Debian VM for a few months now, but I was getting tired of typing out IPs and remembering port nums, especially after bouncing between my router and the original ISP router whenever I'm having network issues. So I wanted to finally map those IPs to human-friendly domains. So like, 192.168.10.247:8096 --> jellyfin.example.com, 192.168.10.247:2283 --> immich.example.com, etc.

I quickly learned that DNS services like Unbound and Dnsmasq do what they say on the tin, DNS only, so I can't do a override to map ports to a domain, as they can only do IPs. My research led me to reverse proxies, and people said Caddy was simple on OPNsense, so I installed that and followed the official guide/documentation. But then I ran into the issue of needing the domain to be externally resolveable. Which then led me to realizing I need to use some sort of CA.

I know Let's Encrypt does it for free, plus the guide mentions them as a default so why not? Except I still need an actual external domain so... Cloudflare? DuckDNS? Someone else? I'm so lost...

The biggest concern of mine right now is, if I set up a reverse proxy, does that mean my services are externally accessible? I was using Tailscale so I could avoid that, especially since I know services like Jellyfin have had serious vulnerabilities, and everyone says it's a good rule of thumb to just not expose services. But how do I map ip + port #s to a domain on OPNsense?

Is there a good way to do this? I could find surprisingly little information about it online.

Fathom is an all-in-one client for Jellyfin, on Linux, Windows, and now Android. It brings movies, shows, music, and Live TV into one window, with most of Jellyfin's server-side management built in, plus optional Seerr requests and a full YouTube client. Everything plays through mpv (via media_kit), so you get direct play, hardware decoding, and real subtitle and audio track control. Free and open source (AGPL-3.0).

Feedback is very welcome. Bug reports and feature requests both belong on GitHub Issues, and questions are fine in Discussions. Fair warning: the new Android TV build is still rough around the edges, so testers and reports there especially would help a lot.

This is my first update post since the 0.9.0 launch, so here's everything added since then.

New platforms

• Android phones and tablets, from a single universal APK.
• Android TV, experimental for now: D-pad navigation and a 10-foot interface, still being refined.
• Android Auto (audio-only): browse Jellyfin music, internet radio, and YouTube, search by voice, and control playback from the car.
• ARM64 (aarch64) Linux builds alongside x86_64.

Player

• Up Next over the credits (a poster card or a compact Netflix-style pill) that rolls into the next episode, with configurable timing and autoplay.
• Skip Intro, Skip Credits, and Skip Recap.
• Audio passthrough: bitstream Atmos, Dolby Digital, and DTS to a receiver on the desktop player.
• Playback Info overlay: play method, codecs, resolution, the live hardware-decode path, and dropped frames.
• Display Sync for smoother playback on high-refresh displays.
• Chromecast casting from Android.

Library and management

• A per-item menu on posters, episode rows, and the detail page: Play or Resume, mark watched, favorite, add to a playlist, refresh metadata, and delete.
• Delete media from the app (with the right server permission): a whole series, a season, a single episode, or a movie.
• In-app plugin configuration as a real form with toggles and fields, instead of a raw JSON blob.
• Backup and Restore your settings to a portable file, by group.

Beyond Jellyfin

• Internet radio: add stations by URL or from the radio-browser.info directory, organize them into groups and favorites, with live time-shift to pause and rewind a live station.
• OS media controls: system media keys and on-screen controls on Linux (MPRIS) and Windows (SMTC), covering video, Live TV, YouTube, and radio.
• The built-in YouTube client gains a Shorts viewer, background audio, a playlist queue, and much faster browsing, on top of the existing SponsorBlock, DeArrow, and downloads.

Quality of life

• Unified search, drag-to-reorder lists, and a customizable Home and navigation.
• Diagnostics screen with exportable logs, internal/external server address auto-switching, and a documentation site.
• Reliable HTTPS on Windows, and in-app updates that verify the download's size and architecture before installing.

Platforms: Linux and Windows (self-contained downloads) and Android (APK; Android TV experimental). macOS and iOS need Mac hardware I don't have yet.

• Code and releases: https://github.com/Fathom-Media/fathom
• Latest release: https://github.com/Fathom-Media/fathom/releases/latest
• Docs: https://fathom-media.github.io/fathom

AI Disclosure

Per Rule 7 / [AIP] disclosure requirements AI was used during development as a coding assistant. Level per category:

• Design (architecture, system design): Hint — I make the architectural calls; AI suggests trade-offs and edge cases I might have missed.
• Implementation (production code): Pair — roughly 50/50. AI drafts, I review, adjust, test on real hardware, and only commit what I've verified. Every commit is manually reviewed before it goes to my dev repo.
• Testing (writing tests, test plans, QA): Assisted — real-device testing is manual (I test on my own PC and mobile devices before every release). AI helps draft test plans and think through edge cases.
• Documentation (docs, comments, README, CHANGELOG): Pair — release notes and changelog entries are drafted with AI then edited for tone; comments and code docs are mostly Pair as well.
• Review (code review, PR feedback): Assisted — I'm the reviewer; AI helps with security sweeps, audit passes on complex changes, and consistency checks.
• Deployment (CI/CD config): Hint — the GitHub Actions build and release pipeline (Linux AppImage, Windows, Android APK) is largely conventional; AI-suggested improvements only.

I am fairly new in the selfhosting business. I host a few services like Jellyfin or AdGuard, but most of my data just sits on plain SMB shares on my NAS.

I am interested in setting up things like Paperless-ngx, Nextcloud maybe Immich as well. One thing I am struggling with is how to organize all this so I don't have the data scattered around multiple places or in the worst-case even duplicated. I like the simplicity of network shares and the fact that I am not relying on a third-party application to keep being maintained. I am currently not sure I am willing to give that up. However, I am also intrigued by the features these services provide. I know Nextcloud has the option to mount external storage, but I don't know which downsides come with that. It gets more complicated with Paperless. As far as I know you typically have a consume directory where you throw in your data and Paperless stores it using its own system in the media directory. This means I either throw in everything or I suddenly have two locations where my documents are stored. If I would mount that media directory in things like Nextcloud I probably wouldn't be able to find anything because of the different structure and naming scheme.

The idea that I had in mind is that I have a single directory structure of my data that can be used on its own and all these tools are just different frontends and provide different views and information of the same data. Maybe this approach is just something from the past and I should move on.

I should add that I am not planning to expose any of these services to the public. All of this is only accessed from inside my house or using a Wireguard VPN.

• How do you guys handle all this?
• How do you avoid data duplication?
• How do you avoid multiple potential file locations? Is a document in my Nextcloud, in my Paperless or just on the network share?
• Do you prepare in some ways in case an application stops being maintained?
• How has this reliance on multiple services impacted other things e.g. your backups?

So for those of you that are curious and have follow my problems on this thread

https://startrek.website/post/43045171

I’ve set up an AudiobookShelf server and so far it work perfectly, tomorrow I’ll try one of their suggested app but it worked really well in browser too

A few weeks ago Rayfish was released and only worked on PCs. But today I checked and noticed V2 was out. I updated my V1 on my PC and then installed it on my phone.

I had to restart the network on my PC to refresh the VPN networks I had already created. I setup a searcXNG on my PC just to try some sort of server. Next I created a firewall rule for that port on the rayfish network and another rule for the network on my Linux firewall. On rayfish I created a network and an invite code for my phone. On the phone I entered the invite code and was immediately connected. I could then ping from my phone to my PC and viseversa.

Finally I searched for the PCs rayfish IP and just connected to it on my browser on the phone. That worked and I was happy. But then I turned off my WiFi on my phone and clicked refresh... A few seconds later the phone re-connected and I got to my searcXNG!

My outside IP is not fixed and I rely on Cloudflare. But none of my services are actually public and are not planned to be public. So now with rayfish I get a permanent IP for free regardless of what my actual IP is. The possibilities are endless.... Big big!

This is very cool! Yeah it's AI developed, but this is AI for us. It's clear and well defined for me, AI working for us is small potatoes vs AI the evil resource sucker spy tool. So let's take advantage. Specifically this project is great and solves my privacy issues with Cloudflare.

Bug Maybe I'm putting it too simply. Any thoughts on this?

I want to expose my services publicly on my own domain name, how would you guys do that?

I have seen people using Cloudflare, but I don't want to use Cloudflare out of principle. I have also seen stuff on caddy and frp that I've done some rough researching.

What do you guys do?

Hello all,

Hubzilla version 11.4 was released recently, now has a new docker image built and should be ready for use.

On a technical note, if your setup involves connection pooling regarding your database, you will need to set system.pdo_emulate_prepares to true within your htconfig.php. The 11.4 release of the docker image, has the appropriate line in the htconfig.php commented out, for your convenience; naturally if you edit your htconfig in other ways (CLI, etc) that will still work, as well. Whichever way you choose to deploy your instance, you have options available to you.

If you are unsure about connection pooling, techbuzz has a great article on the subject, that you can access via the link at the end of this post.

Special thanks to the Hubzilla devs, and contributors for their ongoing work.

You can find their work at: https://framagit.org/hubzilla/core

Please review the new release at: https://framagit.org/hubzilla/core/-/releases

And lastly, within the next hour or so, the docker image will be ready to go at: https://hub.docker.com/r/dhitchenor/hubzilla

I hope this finds you all well; please stay safe.

EDIT: Here is the TechBuzz Online article that I mentioned earlier https://techbuzzonline.com/database-connection-pooling-guide/

Hello there my good people of self-hosted Lemmy! Dawarich got some new stuff since my last post, so here I (Evgenii) am, ready to tell all about it! Make yourself comfortable and prepare for awesome stuff :)

By the way, Dawarich — is your free (now and forever) open source self-hostable alternative to Google Timeline. And hey — we just reached 10k stars on Github! Yay! Here's a small bonus for you! https://youtu.be/-7o2WJPXMVw

AI Disclosure (as per https://lemmy.world/post/49320548):

Implementation - Generated

Testing - Generated

Design - Generated

Our links:

Github: https://github.com/Freika/dawarich

Website: https://dawarich.app/

iOS app: https://apps.apple.com/us/app/dawarich/id6739544999

Android app: https://play.google.com/store/apps/details?id=app.dawarich.Dawarich

First of all, tons of bugs were fixed. Right now I'm steadily keeping number of open issues on Github at around a hundred, and, hopefully, I'll be able to significantly reduce it in the upcoming months. It's time for Dawarich to get some more stability.

So, let's start with the big things!

Since 1.9.1, the following changes were introduced:

• Poster Studio: you can now generate posters, wallpapers or images for your social media, featuring your location history on the map, in a beautifully styled way. Check out screenshot below.

• You can also order a printed poster via our print-on-demand integration, thus supporting Dawarich development. Print quality is superb: I personally ordered two posters to test it, pictures are also can be found below. Important: it's built with privacy in mind, so nothing gets sent to our print-on-demand provider unless you explicitly click a button. Prices are 44,99€ for 30x40cm, 54,99€ for 50x70cm and 74,99€ for 70x100cm poster, printed on 200 gsm premium matte paper. Delivery and VAT included, for now — EU only.

• As a side-effect of the Poster Studio introduction, you can now apply same styles to your main map and customize the colors or provide custom schema for vector maps. It's pretty fancy, check it out!

• Dawarich can be installed as PWA! Pretty neat for read-only purposes on mobile, and I have some ideas on how to make it look nicer on mobile screens in the future.

• Replay upgrades — Polaroid photo pile, live photo-layer toggling, recenter & follow camera

• Google Takeout & Polarsteps imports now extract visits, named places, tracks, and transport modes, not just points (1.11.0); retroactive via "Extract additional data" on the Import page TCX/FIT/Google-takeout activity types now feed transportation-mode detection

• File imports stopped storing raw_data copies; streaming batches for large GeoJSON/Timeline files. Less space on disk taken, less memory during import consumed. Existing points are re-checked after upgrade, with tracks/stats/digests rebuilt on the lowest-priority queue. If you're updating and noticing resources consumption surge, just let it work through the background jobs.

• Self-hosted stack ~20% lighter: 452 → 325 MB app container, 843 → 690 MB total. I also have some more ideas on how to make it even slimmer later

• GET /api/v1/points endpoint now works up to 5 times faster than before

• ImageMagick removed from the image, making the docker image smaller

• Oh, and mobile app update was released, for now just for Android, iOS is following in a few days: you can now enable/disable points, routes, heatmap and visits layers, easily navigate between days and replay your daily movements. The iOS version will also include an (for now, optional) experimental tracking mode, that shown pretty good results, but it needs the famous blue arrow to be on all the time. The choice is yours. Oh, and Dawarich for mobile now eats a lot less of your phone battery. Thanks for all the detailed reports.

These are the most notable changes, but under the hood, there is a lot more. If you're interested, check our our Releases page ( https://github.com/Freika/dawarich/releases ), it's all there.

And now, that we're done with what's already there, let's talk a bit about the future.

Dawarich started as a tool to show location history on the map, but it became so much more since then (all thanks to you, by the way). In the nearest future, subjects of our primary focus are:

• Better mobile experience: UI, more feature parity with the web, better onboarding and family features
• Reworked Search UI
• Simpler and more concise UI overall across the app (I heard Timeline is not that easy to work with)
• Geofence (tell me about your use-cases!)
• Less bugs
• Two new locales (German & French, web first, mobile will follow)
• Better performance and architecture improvements
• I also want to play around MCP so your LLMs of choice could easily talk to Dawarich, improve visits detection and transportation mode detection, but the last two will take some work.

So yeah. As usual, lots of work behind us, even more is ahead of us. I want to say thank once again to all of you who are using Dawarich on daily basis, reporting bugs, suggesting features, opening PRs with fixes and new features supports us financially or just spread the word about the work we do. Without you guys there would be no Dawarich, so — thank y'all.

We also highly appreciate your donations, every single one makes a difference, whether it's a 1 time 1 euro donation or a recurring one on Patreon paid in full for the next year. Every single one of them brings us one step closer to a point where Konstantin (who is in charge of our mobile apps) and I will be able to spend more time polishing Dawarich.

If you happened to be (or know someone who is) a Youtube blogger, a podcaster or just have a blog, we'll be happy to talk to you in case you'd like to create something featuring Dawarich (or Dawarich Atlas for that matter, I'll be giving a talk on it on October's Berlin Geomob). So ping me!

As always, our links to save you a scroll:

Github: https://github.com/Freika/dawarich

Website: https://dawarich.app/

iOS app: https://apps.apple.com/us/app/dawarich/id6739544999

Android app: https://play.google.com/store/apps/details?id=app.dawarich.Dawarich

Donate: https://www.patreon.com/freika / https://github.com/sponsors/Freika/

Thanks and see y'all in a ~month!

P.S. Cooking something legendary

Hi guys! I have a frequent issue on Jellyfin, that is, whenever there's a new TV show or movie, it quickly gets buried behind by new episodes of existing TV shows, and in the case of movies, even old releases being updated can push behind a brand new release. I was wondering if there was a better theming that might prioritize better brand new movies and TV shows over repeating ones?

So I used Jellyfin mostly for series and movies, so far work great. However I got a couple of audiobooks I want to listen to on my way to work and Jellyfin stop working each time I close my screen. So yeah…

What are you using for music ?

Update : People suggest Finamp, which I installed on my phone and tried to make it work on my server. After rebuilding my audiobook library to a music library, Finamp didn’t find anything. I’ve restarted, update, etc.

Work out the problem in naming my library « Musique », now Finamp seems to be able to open it

Thanks for all your help 🤟 you rock

Update 2 : Finamp don’t seems to remember where I’ve finish my last listening 🤣 all that for this. Great app however

CookTrace is a self-hosted recipe, pantry, and cook-diary app. Single Docker container, PWA + native Android app, no accounts on external services, no telemetry. Third app in the Trace family alongside NutriTrace and LiftTrace.

v1.1.1 rolls up everything since v1.0.3 (a couple months of work, went straight from 1.0.3 to 1.1.0 to 1.1.1).

Added

• In-app updates. New Settings → Updates panel checks GitHub Releases for a newer version. On Android, downloads the signed APK and hands off to the system installer via FileProvider. One primary button drives the whole flow: Check Now → Download & Install → Downloading X%. Skip This Version link when an update's available, inline "What's new" markdown panel, opt-in Stable or Dev channels. Silent shade notification when the OS notification permission is granted; top-of-app banner as fallback.
• Full i18n retrofit across the app. Every hardcoded UI string extracted into src/i18n/en.json and reads via svelte-i18n. ~460 new keys, Weblate-ready. Covers Settings, Pantry, Recipes, Cook Diary, Shopping, Trace AI, and every shared widget. Chicago-style title case for labels/buttons/headings, sentence case for body prose. Column-aligned values and paired <key>_desc sibling keys so translators get inline context.
• Pull-to-refresh sync (Android). Swipe down from the top of any page to trigger a manual sync in native server mode.
• Smart connection banner. When sync fails, the banner explains what actually went wrong (no network vs cellular-only vs server unreachable vs HTTP error) with a Retry button, instead of a generic "sync error".
• Cloud icon in hamburger menu goes red on server disconnect. Previously only lit up when the OS reported offline; now also triggers on server-side outages and cellular-vs-LAN routing mismatches.
• Pantry page: configurable default search source. New setting under Settings → Food Sources → Pantry Search picks which chip the Pantry page opens with (All, My Pantry, OFF, USDA). Sticks across sessions + devices.
• Optional email on Create Admin Account form. Shows up when SMTP is configured via environment variables. Stored on the admin user record for password-reset and invite emails later.
• Accent-tinted browser chrome. The browser tab bar picks up the current accent color via <meta name="theme-color">. Running CookTrace alongside NutriTrace / LiftTrace? Distinct accent per install makes tabs visually distinguishable at a glance.
• Docker Hub mirror. Images now publish to both ghcr.io/traceapps/cooktrace (primary) and traceapps/cooktrace on Docker Hub. Identical multi-arch tag set on both registries.

Changed

• Bitwarden and other password managers show a real app identifier instead of "localhost" (Android). The Android app used to serve its WebView from https://localhost/, so autofill entries saved as "localhost" and were indistinguishable from any other localhost app. Now identifies as app.cooktrace.local, which reads clearly in autofill dialogs and saved-credentials lists. One-time upgrade cost: the origin change orphans locally cached web-only state, so on first launch after upgrading you'll re-enter your server URL + log in again (server-connected users) or lose theme / accent / display prefs (standalone users). Recipe, pantry, and shopping data is unaffected (that lives in a separate local SQLite DB).
• SMTP "Username" field relabeled to "Email or Username". Most providers want the full email; the label change removes the guesswork.

Fixed

• OFF country filter works again + picker expanded 15 → 30 countries. The Pantry's Open Food Facts country filter was being passed with the wrong query shape (countries_tags_en=<slug>), so selecting Norway or any non-World option silently had no effect. Fixed by using search-a-licious's native inline Lucene syntax. While in there: alphabetized the picker and added Argentina, Austria, Belgium, Chile, Denmark, Finland, Ireland, Netherlands, New Zealand, Norway, Poland, Portugal, Singapore, South Africa, South Korea, Sweden, Switzerland.
• App icon no longer shows a white halo. Bundled icon PNGs had ~15px of solid white padding baked into their corners; on tinted browser chrome the halo was visible around the tab favicon. Corners now clear cleanly. Icon URLs cache-busted with the app version so future icon fixes take effect without a browser cache clear.
• Create Admin form password field no longer crushed. The password input on the Enable User Management form was rendering as a colored sliver because of a flex-layout bug. Password + Confirm now sit symmetrically side-by-side, each with its own eye toggle sharing show/hide state.
• Server-connection banner no longer covers the phone's notification bar (v1.1.1). The red "server unreachable" banner sat edge-to-edge at viewport top:0, which on Android slid it up over the status bar / clock. Now floats as a rounded card below the status bar and the compact header.

Where to Get It

Docker Compose:

services:
  cooktrace:
    image: ghcr.io/traceapps/cooktrace:latest  # or traceapps/cooktrace:latest on Docker Hub
    container_name: cooktrace
    ports:
      - "3003:3001"
    volumes:
      - ./data/db:/data/db
      - ./data/uploads:/data/uploads
    environment:
      JWT_SECRET: change-me-to-a-long-random-string
      DB_PATH: /data/db/cooktrace.db
      UPLOADS_PATH: /data/uploads
    restart: unless-stopped

Then docker compose up -d and open http://localhost:3003/.

• GitHub: https://github.com/traceapps/cooktrace
• Docs: https://traceapps.github.io/docs/cooktrace/
• v1.1.1 release notes: https://github.com/traceapps/cooktrace/releases/tag/v1.1.1
• Full CHANGELOG: https://github.com/traceapps/cooktrace/blob/main/CHANGELOG.md
• Android APK: signed, on the Releases page (shared TraceApps keystore, in-place upgrades work)

AGPL-3.0. No accounts, no telemetry, no external cloud unless you opt in (Open Food Facts, USDA, or an AI provider you supply the key for).

AI Disclosure

Per Rule 7 / [AIP] disclosure requirements AI was used during development as a coding assistant. Level per category:

• Design (architecture, system design): Hint — I make the architectural calls; AI suggests trade-offs and edge cases I might have missed.
• Implementation (production code): Pair — roughly 50/50. AI drafts, I review, adjust, test on real hardware, and only commit what I've verified. Every commit is manually reviewed before it goes to my dev repo.
• Testing (writing tests, test plans, QA): Assisted — real-device testing is manual (I test on my own PC and mobile devices before every release). AI helps draft test plans and think through edge cases.
• Documentation (docs, comments, README, CHANGELOG): Pair — release notes and changelog entries are drafted with AI then edited for tone; comments and code docs are mostly Pair as well.
• Review (code review, PR feedback): Assisted — I'm the reviewer; AI helps with security sweeps, audit passes on complex changes, and consistency checks.
• Deployment (CI/CD config): Hint — Docker/GitHub Actions/release pipeline is largely conventional; AI-suggested improvements only.

Hi everyone

I'm looking to expand my storage. I have a case capable of 8 bays and I don't think I'll exceed that soon (currently at 3 drives).

I bought a m.2 slot with a bunch of sata ports on it but it doesn't work. I've researched and read an HBA is a much better solution anyway.

If I'm going to get the HBA I might as well run all 8 ports on it.

Aside from the clearance on the card in the case, are there any other considerations I need to he aware of? I justbeant to get something that works from the get go. For my uses I have a good amount of apps and I stream media from the server

CPU- i5-10400f 2.90ghz

MOBO - asrock h570m-itx/ac

RAM - gskill f4-3200c16-8gvkb

GPU - Quadro k620 (gm107gl) rev a2

CASE - Jonsbo N3