PSA: Trivy container scanner compromised
Please be advised that all versions of Trivy (container vulnerability scanner) 0.69.4 were compromised because of credential theft:
https://www.bleepingcomputer.com/news/security/trivy-vulnerability-scanner-breach-pushed-infostealer-via-github-actions/
Everybody who used this version with any tag can consider their environment breached.
https://redd.it/1s04ae3
@r_SelfHosted
Map Tracker and Trip Planner - Updated
https://redd.it/1rzsnuu
@r_SelfHosted
Why Is everyone persisting Redis… Even when it’s just a Cache?
I’m not sure if this is the perfect sub, but the question is definitely related to selfhosting
I see most tutorial even official documentation of large projects set up redis/valkey in the compose file with `appendonly yes` or bind mount a directory for redis-data when it's only used as cache.
But… isn’t cache supposed to be ephemeral?
Immich, Nextcloud, Paperless, ... etc. Almost every docker-compose example I find uses persistent storage for Redis.
Instead I'm using the following for all my compose files
redis:
image: docker.io/valkey/valkey:latest
container_name: nextcloud-redis
restart: always
command: valkey-server --save "" --appendonly no
user: 1000:1000
read_only: true
security_opt:
- no-new-privileges:true
tty: false
stdin_open: false
cap_drop:
- ALL
networks:
- nextcloud-redis-net
So… what am I missing?
* What’s the real benefit of mounting a Redis data directory?
* Why use AOF or RDB persistence when Redis is only functioning as a volatile cache?
* Are there cases where persistence is required even if the project calls it a “cache”?
I hope someone here can shed some light on this as this sub has been my most valuable source of learning from the experts.
https://redd.it/1rzmjb0
@r_SelfHosted
First pass at a Grafana dashboard for network monitoring
https://redd.it/1rzj0qu
@r_SelfHosted
Docker image for Obsidian Sync Headless
Hello,
One of the thing that kept me from using Obsidian Sync and instead self-host multiple solution for it was the fact I couldn't easily sync the data directly to my homelab without using other tools on top of Obsidian Sync.
This has now changed, since February they released a Headless version that can be setup to just do sync.
I've reworked a non-working docker image to have a fully working configurable docker image for it.
Full information:
https://github.com/Belphemur/obsidian-headless-sync-docker
Basically I use s6-overlay with their obsidian-headless npm tool.
>AI DISCLAIMER:
I used AI to help me configure s6-overlay, I have experience doing it in other project like my protonmail-bridge. But I wanted to avoid having to rewrite everything from scratch again, so I used GitHub Copilot Agent to make the change while doing multiple full interactive session and reviewing the change as they happened.
ps: also this full post is actually written by a human for once.
https://redd.it/1rz6ycy
@r_SelfHosted
Houndarr: A polite, automated search scheduler for your *arr stack
https://github.com/av1155/houndarr
https://redd.it/1rz4dfu
@r_SelfHosted
Update: TapMap now supports Linux and Docker as requested
https://redd.it/1rz2zsb
@r_SelfHosted
Don't expect us to try your AI app
Developing a niche or custom tool with AI that solves your problem is great and it is changing the landscape for a few SAAS on a few specific services. But man...! Sooo many posts in the past few weeks either here or a few related subs, of self proclaimed Zuckerbergs promoting their ground breaking new flavor of the day AI apps... Don't expect most people (anyone really) to ever install or try it.
There is a GIGANTIC gap (think of a giant gap, and do x10) between "prompt and pray" AI apps, and production ready, stable and SAFE products. DevOps and cybersecurity principles you do not know exist, and that your coding agent won't advertise because they're trained to be helpful, efficient and to take the path of least resistance.
There is nothing user-friendly about 99% of these principles, your LLM will avoid them by default, and if you don't know anything about software architecture, PLEASE, keep these apps to yourself.
Also; NOT ALL IDEAS ARE WORTH SHARING. Most of them sucks actually, that's why they get peer reviewed in a real development environment.
TLDR; if you don't know what stable and secured software architecture is - don't promote your AI coded app.
https://redd.it/1rywekd
@r_SelfHosted
Pi-Hole vs AdGuard for casual users
I know it's a recurring question, but everytime you see opinions from users that have particular needs or setups.
My question is: from a "casual user" perspective, that doesn't need any strange setup but just and Ad blocker setup and just want a little home security, what's the best between those two?
Also, for user that don't want to waste time to setup the whole system, just put Linux on a PC and install one of those, a couple of configuration and done.
I have mine on an old Asus VivoStick that I almost never used and was sitting there alone, put Lubuntu on it, connected via USB to LAN and done.
For example I just saw that AdGuard has built in encryped DNS that Pi-Hole hasn't and a "web interface" that I don't think I ever use it but it's a nice perk.
https://redd.it/1ryox87
@r_SelfHosted
**Batch DELETE 1000**: MinIO 165ms, SeaweedFS 189ms, Garage 385ms — Garage is 2.3× slower
- **SeaweedFS S3 bug**: `mc mirror` fails with ContentLength mismatch on some files. boto3 works fine.
- **Garage deduplicates**: Content-addressed blocks mean identical files are stored once. Didn't realize this until I noticed 1000 "different" files stored as 1 block (my benchmark initially used the same random payload per size class 🤦)
## My Verdict
| If you care about... | Pick |
|---|---|
| **Upload speed** (small files, ingestion pipelines) | **SeaweedFS** |
| **Memory efficiency** (low RAM VPS, edge, RPi) | **Garage** |
| **Simplicity + S3 compatibility** | **MinIO** |
| **Disk efficiency** | **SeaweedFS** (1.02×) or **MinIO** (1.00×) |
| **Lowest per-request latency** (HEAD, DELETE) | **Garage** |
| **Large files** (10MB+) | **MinIO** |
For my workload (326K small files, write-heavy burst ingestion, write-once filings), **SeaweedFS has the strongest case** — 3.8× faster sequential uploads, best LIST performance, best disk efficiency. The tradeoff is operational complexity (3 containers vs 1) and an S3 compatibility edge case.
**Garage is the dark horse** — incredibly memory-efficient (~4 MB heap!), fastest HEAD/DELETE, competitive uploads. But LMDB metadata scaling (~2 KB/object = 675 MB at my scale) and slow batch deletes are real concerns.
**MinIO remains the safe default** — simplest to run, best S3 compatibility, lowest CPU usage, but noticeably slower for small-file ingestion.
---
*Benchmark tool: Python/boto3 with `time.perf_counter()`, 20 iterations per test, all on localhost.
https://redd.it/1ryfzw4
@r_SelfHosted
MinIO vs SeaweedFS vs Garage
I'm building a new server to ramp up my workload ~10×, so I re-evaluate my storage backend. I've been running MinIO, but since it's been archived, I wanted to explore
alternatives. SeaweedFS and Garage both looked promising, so I ran all three side-by-side on the same machine and benchmarked them.
I'm debating between SeaweedFS and Garage. SeaweedFS has better storage efficiency and raw throughput, but Garage's tiny memory footprint is tempting — my 64 GB server is shared with databases, app servers, and other services. Note: I only need a single server, no clustering. I'd love feedback from the community — especially anyone running SeaweedFS or Garage in production.
Full disclosure: The benchmark scripts and this write-up below this point were generated with AI. I caught and corrected
several issues along the way (dedup skewing Garage's storage numbers, docker stats under-reporting Garage's memory due
to mmap, AWS CLI adding 500ms overhead masking real latency). I think the numbers are reasonable now.
My workload: A self-hosted project storing Japanese stock filing documents (EDINET/TDnet) — 326K files, 20 GB
total. Most files are tiny: 84% of one bucket is under 10KB (daily JSON/CSV stock snapshots), another has 91K filing
images (PNG/PDF, 100KB–1MB). Write-once, read-occasionally. Burst ingestion pattern. Single server only — no clustering
needed.
## The Setup
- MinIO: Fresh empty instance, single container, default config
- SeaweedFS: Master + Volume + Filer (3 containers), -volumePreallocate=false
- Garage v2.2: Single container, LMDB backend, block_size=1MB, compression off
- All on localhost, same Docker host, 32 GB RAM
## Upload Latency (p50, 20 iterations each)
| File Size | MinIO | SeaweedFS | Garage |
|-----------|-------|-----------|--------|
| 1 KB | 7.4 ms | 2.3 ms | 1.8 ms |
| 5 KB | 9.3 ms | 2.3 ms | 3.0 ms |
| 100 KB | 9.5 ms | 3.2 ms | 3.6 ms |
| 1 MB | 19.7 ms | 10.7 ms | 8.4 ms |
| 10 MB | 48 ms | 65 ms | 63 ms |
SeaweedFS and Garage are 3–4× faster than MinIO for small file uploads. MinIO only wins at 10MB+.
## Sequential Batch Upload (1 worker, 1000 × 5KB files)
| Backend | ops/s |
|---------|-------|
| SeaweedFS | 431 |
| Garage | 376 |
| MinIO | 113 |
MinIO is 3.8× slower at sequential small-file ingestion. At 50 concurrent workers they all converge to ~570 ops/s.
## Downloads — Basically a Tie
All three deliver sub-2ms p50 for files under 1MB. Garage has a slight edge at 1–5KB (~1.1ms), SeaweedFS wins at 10MB (12.9ms vs 35ms Garage). No dramatic differences — downloads aren't the differentiator.
## Resource Consumption (the surprise)
Measured with a fresh MinIO instance (no production data) for fair comparison.
| | MinIO | SeaweedFS (3 containers) | Garage |
|---|---|---|---|
| Idle memory | 269 MB | 247 MB | ~90 MB (cgroup) |
| Memory under write load | 441 MB | 421 MB | ~13 MB (docker stats) |
| CPU under write load | 53% | 101% | 134% |
| Containers | 1 | 3 | 1 |
\Garage uses LMDB (mmap), so docker stats under-reports. Cgroup memory is ~90 MB idle. The OS manages which LMDB pages stay in RAM via page cache — cold pages get evicted automatically under memory pressure. Actual non-evictable heap is just ~4 MB.
Tradeoff: SeaweedFS/Garage burn more CPU for faster uploads. MinIO is the most CPU-efficient.
## Storage Efficiency (tested with unique random data per file)
| Backend | 24.65 MB logical → disk | Ratio |
|---------|------------------------|-------|
| SeaweedFS | 25.29 MB | 1.02× |
| MinIO | ~24.7 MB | 1.00× |
| Garage | 31.79 MB | 1.29× |
Garage has ~6 MB LMDB metadata overhead per 1K objects (~2 KB/object). At my 326K objects that's ~675 MB just for metadata on disk. SeaweedFS and MinIO are essentially 1:1.
## Other Notable Findings
- LIST 1000 objects: SeaweedFS 68ms, Garage 72ms, MinIO 86ms
- HEAD latency: Garage wins at ~1.1ms across all sizes (vs ~1.25ms for both others)
-
Foldergram: Self-hosted local photo gallery with an Instagram-style feed and layout
https://redd.it/1ryjc9e
@r_SelfHosted
What's your 'I can't believe I self-hosted that' service?
Curious what services surprised you by being worth self-hosting. Not the obvious stuff like Plex or Pi-hole, but things you didn't expect to work well or didn't think were worth the effort until you tried. What's running on your setup that you'd never go back to a hosted version of?
https://redd.it/1rykzo4
@r_SelfHosted
PSA: Think hard before you deploy BookLore
Wanted to flag some stuff about BookLore that I think people need to hear before they commit to it.
**The code quality issue**
There's been speculation for a while that BookLore is mostly AI-generated. The dev denied it. Then v2.0 landed and, well: crashes, data not saving, UI requiring Ctrl+F5 to show changes, the works. These are the kinds of bugs you get when nobody actually understands the codebase they're shipping.
The dev is merging 20k-line PRs almost daily, each one bolting on some new feature while bugs from the last one go unfixed. And the code itself is a giveaway: it uses Spring JPA and Hibernate but is full of raw SQL everywhere. Anyone who actually built this by hand would keep the data layer generic. Instead, something like adding Postgres support is now a huge lift because of all the hardcoded shortcuts. That's not a style preference, that's what AI-generated code looks like when nobody's steering.
**How contributors get treated**
This part is what really bothers me.
People submit real PRs. They sit for weeks, sometimes months. Then the dev uses AI to reimplement the same feature and merges his own version instead. Predictably, this pisses people off. At the time of writing this, the main dev has alienated almost all of the contributors that were regularly supporting, triaging issues and doing good work on features and bugfixes.
When called out, he apologizes. Except the apologies are also AI-generated. And more than once he forgot to strip the prompt, so contributors got messages starting with something like "Here's how you could apologize—"
One example I'm familiar with, because I was following for this feature for a while (over 2 months?): someone spent serious time building KOReader integration. There was an open PR, 500+ messages of community discussion around it. The dev ignored it across multiple releases, then deleted the entire thread and kicked the contributor from the Discord. What shipped in that release instead? "I overhauled OIDC today!" Cool.
Every time criticism picks up in the Discord, the channel gets wiped and new rules appear. This has happened multiple times now.
**The licensing bait-and-switch**
This is the part that should actually scare you if you're thinking about deploying this.
BookLore is AGPL right now. The dev is planning to switch to BSL (Business Source License), which is explicitly *not* an open source license. He also plans to strip out code from contributors he's had falling-outs with. Everyone who contributed did so under AGPL terms. Changing that out from under them is a betrayal, full stop.
The main dev had a full on crashout on another discord, accusing people of betrayal etc because they were....forking his code? I am not going to paste the screenshots of the crashout because it is honestly just unhinged and reflects badly on him, maybe its something he'll regret and walk back on - hopefully.
It gets worse. There's a paid iOS app coming with a subscription model. What does that mean concretely? You'll be paying a subscription to download your own books offline to your phone. Books you host yourself. On your own hardware.
The OIDC implementation, which should be a standard security feature, is being locked down specifically to block third-party apps from connecting, so the only mobile option is the paid one. Features the community helped build are being turned into a paywall funnel.
The dev has said publicly that he considers forking to be "stealing" and wants to prevent it. He's also called community contributions "AI slop." From the guy merging AI-written 20k-line PRs daily. Make of that what you will.
**Bottom line**
* Contributors get ignored, reimplemented over, and kicked out
* AGPL → BSL relicense is coming, with contributor code being stripped
* Paid iOS app will charge you a subscription to access your own self-hosted books offline
* OIDC is being locked down to kill third-party app access
* The dev thinks forking is theft and has open contempt for OSS
Self hosted options for Youtube videos & clips
So, obviously there is Plex for videos and I self host an instance of that for our Movies & TV shows.
But recently was wondering if there could be an option for some sort of filtered YouTube.
I came across one project on Github that um... advertises itself for Gooners and organizing your goon collection, lol. It looked functional for SFW content, but maybe not ideal.
Just wondering if anyone has any suggestions or if I should just consider sticking with videos inside Plex.
https://redd.it/1rrwv91
@r_SelfHosted
It's Not Friday Anymore - Roundup
But on Friday, there were lots of really cool projects shared.
Here are the top projects:
Top 10 posts in markdown format:
1. Update: TapMap now supports Linux and Docker as requested
- u/Old-Marketing6949 | 272 pts | 34 comments | 17:43 UTC
- GitHub: https://github.com/olalie/tapmap
2. Foldergram: Self-hosted local photo gallery with an Instagram-style feed and layout
- u/sajjadalis | 240 pts | 33 comments | 01:49 UTC
- GitHub: https://github.com/foldergram/foldergram
3. Project Nomad - the offline knowledge repo
- u/Th3LonelyBard | 235 pts | 43 comments | 13:10 UTC
4. Docker image for Obsidian Sync Headless
- u/Belphemur | 79 pts | 13 comments | 20:13 UTC
- GitHub: https://github.com/Belphemur/obsidian-headless-sync-docker
5. Kumiho v0.12.0 - Fast & Flexible Self-hosted E-Book/Audiobook Server (Docker)
- u/SuspiciousCow7289 | 34 pts | 12 comments | 11:54 UTC
- GitHub: https://github.com/aha-hyeong/kumiho
6. [Fishing of the day](https://reddit.com/r/selfhosted/comments/1rzmx51/fishingoftheday/)
- u/badrrrrmoon | 17 pts | 3 comments | 09:12 UTC
7. X(P)FeRD: Design and manage XRechnung and ZUGFeRD compatible e-invocies
- u/testheit | 12 pts | 6 comments | 06:24 UTC
- GitHub: https://github.com/tiehfood/xpferd
8. CollabMD: Turn local Markdown folders and Obsidian vaults into a real-time collaborative web app
- u/ndezt | 7 pts | 9 comments | 10:02 UTC
- GitHub: https://github.com/andes90/collabmd
9. I built a small self-hosted Discord-style Matrix client for my community
- u/VitosiCZ | 5 pts | 7 comments | 17:02 UTC
- GitHub: https://github.com/Vitosicz/Heorot
- GitHub: https://github.com/Vitosicz/Heorot-voice-relay
10. Anything stand out as an oof?
- u/ss5raditz | 5 pts | 12 comments | 22:00 UTC
https://redd.it/1rzz3dt
@r_SelfHosted
Fishing of the day
https://redd.it/1rzmx51
@r_SelfHosted
self hosted wireguard vs tailscale?
im currently using tailscale to bypass CGNAT, but im thinking about self hosting a wireguard VPN server with ipv6 to not have to rely on tailscale and be completely independent.
which would be more secure? and would setting up wireguard be worth it?
https://redd.it/1rzediq
@r_SelfHosted
If Docker Hub images are so insecure why does everyone still use them as the default?
This is something ive been thinking about for a while and i genuinely dont understand.
Every time someone scans their Docker Hub images the reaction is shock. Hundreds of CVEs, multiple criticals, packages nobody needs or uses. This isnt new information. Weve all seen the scan results. And yet every tutorial, every quickstart guide, every stackoverflow answer still starts with docker pull official-image like thats fine.
Hardened alternatives exist. Distroless exists. Minimal images with single digit CVE counts exist. So why is the default still bloated debian images with 400+ packages?
Is it just inertia? Cost? Nobody knows the alternatives exist? Or does everyone just accept this as normal and move on?
Genuinely curious whats keeping the ecosystem stuck here.
https://redd.it/1rzddrb
@r_SelfHosted
What's something you have recently removed from your server?
couple weeks ago there was a handy topic about stuff that you have recently removed from your server. Whether it was because it wasn't working for you or you moved to something else or you just wasn't using it enough. I think this is very good way of trimming down your stuff or finding new things that do things better.
I will start here:
Adguard Home - moved to Technitium because of their cluster feature.
Transmission - moved to qBittorrent as Transmissions started being laggy with loads of torrents
Tracearr/Yamtrack - I just wasnt using it enough. They are great apps, but I get streaming tracking via Emby and TV Shows/Movies releases are tracked in arr stack.
UpSnap - Great app, unfortunately I only have WiFi available so this one didn't work for me.
Komodo - I tried liking it but it was just too much for me, I am back to Arcane.
Flood - As I moved to qBittorrent I switched to Qui
https://redd.it/1rz1pns
@r_SelfHosted
This is the reason you shouldn't host your own email... Microsoft says 🖕to 200k user ISP.
https://www.ispreview.co.uk/index.php/2026/03/microsoft-domain-blacklist-causes-email-problems-for-uk-isp-zen-internet.html
Microsoft seemingly don't care that they've black listed the IPs of a fairly large and well-respected UK ISP. If they can't get help, what chance does an individual have?
Email does feel like a cartel in many respects. I look forward to the flurry of stories of you hosting your own email since the 90s without issue. But, the truth comes from those who have had issues and how painful it was to resolve.
https://redd.it/1rz3zxp
@r_SelfHosted
Project Nomad - the offline knowledge repo
https://youtu.be/P_wt-2P-WBk
https://redd.it/1ryvufj
@r_SelfHosted
Kumiho v0.12.0 - Fast & Flexible Self-hosted E-Book/Audiobook Server (Docker)
https://redd.it/1ryu7g7
@r_SelfHosted
Do you self-host Matrix?
https://redd.it/1rysyw3
@r_SelfHosted
MinIO vs SeaweedFS vs Garage
I'm building a new server to ramp up my workload ~10×, so I re-evaluate my storage backend. I've been running MinIO, but since it's been [archived](https://github.com/minio/minio), I wanted to explore
alternatives. SeaweedFS and Garage both looked promising, so I ran all three side-by-side on the same machine and benchmarked them.
I'm debating between SeaweedFS and Garage. SeaweedFS has better storage efficiency and raw throughput, but Garage's tiny memory footprint is tempting — my 64 GB server is shared with databases, app servers, and other services. Note: I only need a single server, no clustering. I'd love feedback from the community — especially anyone running SeaweedFS or Garage in production.
**Full disclosure:** The benchmark scripts and this write-up below this point were generated with AI. I caught and corrected
several issues along the way (dedup skewing Garage's storage numbers, `docker stats` under-reporting Garage's memory due
to mmap, AWS CLI adding 500ms overhead masking real latency). I think the numbers are reasonable now.
**My workload:** A self-hosted project storing Japanese stock filing documents (EDINET/TDnet) — **326K files, 20 GB
total**. Most files are tiny: 84% of one bucket is under 10KB (daily JSON/CSV stock snapshots), another has 91K filing
images (PNG/PDF, 100KB–1MB). Write-once, read-occasionally. Burst ingestion pattern. Single server only — no clustering
needed.
## The Setup
- **MinIO**: Fresh empty instance, single container, default config
- **SeaweedFS**: Master + Volume + Filer (3 containers), `-volumePreallocate=false`
- **Garage v2.2**: Single container, LMDB backend, `block_size=1MB`, compression off
- All on localhost, same Docker host, 32 GB RAM
## Upload Latency (p50, 20 iterations each)
| File Size | MinIO | SeaweedFS | Garage |
|-----------|-------|-----------|--------|
| 1 KB | 7.4 ms | 2.3 ms | **1.8 ms** |
| 5 KB | 9.3 ms | **2.3 ms** | 3.0 ms |
| 100 KB | 9.5 ms | **3.2 ms** | 3.6 ms |
| 1 MB | 19.7 ms | 10.7 ms | **8.4 ms** |
| 10 MB | **48 ms** | 65 ms | 63 ms |
**SeaweedFS and Garage are 3–4× faster than MinIO for small file uploads.** MinIO only wins at 10MB+.
## Sequential Batch Upload (1 worker, 1000 × 5KB files)
| Backend | ops/s |
|---------|-------|
| SeaweedFS | **431** |
| Garage | 376 |
| MinIO | 113 |
MinIO is **3.8× slower** at sequential small-file ingestion. At 50 concurrent workers they all converge to ~570 ops/s.
## Downloads — Basically a Tie
All three deliver sub-2ms p50 for files under 1MB. Garage has a slight edge at 1–5KB (~1.1ms), SeaweedFS wins at 10MB (12.9ms vs 35ms Garage). No dramatic differences — downloads aren't the differentiator.
## Resource Consumption (the surprise)
Measured with a fresh MinIO instance (no production data) for fair comparison.
| | MinIO | SeaweedFS (3 containers) | Garage |
|---|---|---|---|
| **Idle memory** | 269 MB | 247 MB | **~90 MB** (cgroup) |
| **Memory under write load** | 441 MB | 421 MB | **~13 MB** (docker stats*) |
| **CPU under write load** | **53%** | 101% | 134% |
| **Containers** | 1 | 3 | 1 |
\*Garage uses LMDB (mmap), so `docker stats` under-reports. Cgroup memory is ~90 MB idle. The OS manages which LMDB pages stay in RAM via page cache — cold pages get evicted automatically under memory pressure. Actual non-evictable heap is just **~4 MB**.
**Tradeoff: SeaweedFS/Garage burn more CPU for faster uploads. MinIO is the most CPU-efficient.**
## Storage Efficiency (tested with unique random data per file)
| Backend | 24.65 MB logical → disk | Ratio |
|---------|------------------------|-------|
| SeaweedFS | 25.29 MB | **1.02×** |
| MinIO | ~24.7 MB | 1.00× |
| Garage | 31.79 MB | 1.29× |
Garage has ~6 MB LMDB metadata overhead per 1K objects (~2 KB/object). At my 326K objects that's **~675 MB just for metadata** on disk. SeaweedFS and MinIO are essentially 1:1.
## Other Notable Findings
- **LIST 1000 objects**: SeaweedFS 68ms, Garage 72ms, MinIO 86ms
- **HEAD latency**: Garage wins at ~1.1ms across all sizes (vs ~1.25ms for both others)
-
What’s the most “boring reliable” self-hosted stack you’ve used that still scales well?
I’m not looking for the coolest stack or the most “cloud native” answer.
I’m looking for the setup you’d put on a box, sleep well at night with, and not hate 6 months later.
The project is not huge, but it’s also not just a toy. Think somewhere in the middle:
content/site layer,
some app logic,
user accounts,
background jobs,
APIs,
a database,
maybe Redis,
maybe object storage later.
I keep seeing 2 extremes:
one side says “just run everything in Docker Compose and keep life simple”
the other says “you need Traefik, queues, workers, metrics, S3, separated services, external DB, secrets management, and three dashboards before you even launch”
I’m trying to avoid both underbuilding and building myself a tiny DevOps trauma machine.
So I guess my real question is:
If you were self-hosting a small-but-real production app today, what stack would you choose if your main goal was long-term sanity?
Not “maximum scale”
Not “best on paper”
Just stable, maintainable, easy to restore, and not annoying.
Would love answers from people who’ve already gone through the phase of overengineering everything and came back to something simpler.
Thanks :)
https://redd.it/1ryr1en
@r_SelfHosted
Proud of my little self hosted server
https://redd.it/1ryflmp
@r_SelfHosted
norms
[https://postimg.cc/gallery/R3WJKVC](https://postimg.cc/gallery/R3WJKVC) \- some examples. I couldn’t grab some from the official discord, seeing as how ACX has a habit of wiping that one whenever some pushback is posted.
This is the huntarr situation all over again. Deploy with caution, or honestly, wait and see if a community fork shows up under a license that actually holds.
https://redd.it/1rs275q
@r_SelfHosted
Looking to self host a word processor for creative writing
My sister is a creative writer. She uses Google docs and frequently writes on her phone. She (understandably) is becoming increasingly uncomfortable with Google having her work on their hardware and wants to move it to my nextcloud server. The only issue is that every word processor I have come across has a really awful android app experience when compared to Google docs.
She wants just some really basic features doesn't need crazy formatting or anything like that, just the following:
-Dark mode
-An app navigation interface that is more similar to a notes app that doesn't load the whole damn page and make you zoom in just to see what your writing
-a few font options
-the ability to toggle spell check off
-a nice to have would be an autocorrect feature
I have yet to find anything that really suits this use case that I can self host. Any ideas?
https://redd.it/1rrxdnx
@r_SelfHosted
Discord to Unifi Access Chatbot
I wanted a way to allow my friends access to my game servers without exposing the game server to the world. I created a chatbot that allows users with a specific role on my discord server to request access. It will then send them a unique link and allow them to add their public IP to the access rules on my firewall.
I'll have to update my docs to include this, but this app assumes you are running a Unifi firewall and that you are using some sort of domain services for a persistent hostname. (Static IP or DDNS)
Looking to make it more modular for other firewalls and game servers.
https://github.com/Copter64/chatbot\_access\_project
https://redd.it/1rrv006
@r_SelfHosted
