Hello,

As the title suggests, how do you manage your DBs for docker services.

Do you spin a new DB for every new docker cluster or do you have a centralized DB that is accessible to the docker clusters.

What are the pros and cons of both method?

For the moment, I spin a new DB for every services as I feel it is easier to backup the service in case of a problem.

I'm a Windows guy since forever and I recently got into selfhosting. So far its a blast! Are posts about that welcome here?

Hello guys, so I have been self hosting a bunch of stuff for some years now. But I want to increase the protection of the services I host.

I was thinking of using a VPS just for ddos protecting my services like game servers, web servers, email etc.

Any suggestion on how to set this up well? I was thinking of routing all traffic from the VPS back home with wireguard. My connection is gigabit so I don't think the performance impact will be too big, any suggestion on which proxy, VPS and other things to use?

This post contains content related to media piracy. I couldn't find any rules for this community and I don't know if it's allowed. I accept the risk of getting this post taken down or being banned without knowing the rules.

With that small disclaimer out of the way, let's tackle my question.

I'm a simple self hoster: I have single server made out of an Optiplex 3060 Micro (i5 8500T, 32GB, 14TB of storage in one drive), I use duckdns instead of a real domain and I have no supporting infrastructure. I don't really like watching things, I set up arr stack mainly because everyone says it's the best thing to use a homelab for.

My family have strong opinions on piracy and I know for a fact they wouldn't use my jellyfin, even if I tried to manipulate them, which btw is a really bad practice (if it's as common as responses under posts about getting people to use your homelab suggest).

I also have hard time getting them to even allow me to run my homelab (I'm a teenager, I live with my parents), because it takes space and uses power (for context idle is around 8W).

As I said, I don't watch things that often and even if I watch, I'm extremely monothematic, I watch basically only AOT and sometimes some random popular movie.

I understand that my situation is quite unique, but I find it hard to argue for Jellyfin+arrs when fmhy and countless reliable streaming sites exists.

I already made my mind, I'll stop using those services today. I'm interested how others look at this "problem" tho.

Are you hosting arr stack/plex/jellyfin?

How much is it utilized (in watch hours/week for example, mine was less than 2/week)?

Have you considered not using it?

If you stopped using it and went back, what happened, why did you change your mind?

Hello,

First let me answer your first question : No, It's not AI generated.

I started working on a new project geared towards small self-hosted environment which automate the use of snapshot to reduce downtime when doing offline backups.

Instead of waiting for the entire external backup to finish to restart the service LaManager create a instantaneous snapshot using Copy on Write (COW) restart the service and upload the external backups reducing downtime significantly.

More details in the readme.md.

Warning the project is still very early so there might be rough edge and bugs, be careful. However I hope to be able to make something nice and usefull out of it.

PS: It is my first post on lemmy after looking around without account here for a while, the lack of history is not me being a bot, I'm just new here.

I wanted to say thank you to everyone that responded on the previous post. Whether intentional or not, some of the comments gave me some ideas for elaboration and improvement of my pipeline.

I discovered that the TINK 4k has the ability to do 480i pass through via custom modelines, which I enabled and updated my capture script to take advantage of. The biggest downside to using the TINK is that it converts color to RGB, which results in slightly-less-than-faithful raw captures.

This leads into the new VapourSynth pipeline I put together. When strung all together, we're now performing:

• Lossless RGB NTSC capture, converting to YUV 4:4:4 for processing until the final 4:2:0 output
• QTGMC source-matched deinterlacing to 59.94p
• Motion-compensated denoise and CCD chroma cleanup
• Dehaloing, contrasharpening, and debanding
• Lanczos upscale to 4:3 1080p

I'm currently punting on any neural upscaling, because I really don't want to introduce any semblance of hallucination.

You also may have noticed I added waveform and vectorscopes to the monitor stream, to get a quick and dirty readout of the brightness and color levels of a given tape.

I understand that this project is now probably blurring the lines of appropriateness for this particular community, so it will likely be my last post on the matter here. I just wanted to give an update, and say thanks!

For those who’ve never heard of us:

Libre Closet is a free, open-source, self-hosted wardrobe organizer - with client side garment image background removal. Catalog your clothes, upload photos, build outfits, and access everything from your phone as an offline-ready PWA - all on your own server.

We at Lazztech LLC have crafted and engineered this project with care and intention to be as easy to self-host as possible. It defaults to local SQLite storage and local file storage. It has optional auth/multi user support.

docker run -p 3000:3000 -v wardrobe-data:/data ghcr.io/lazztech/libre-closet:latest

Please feel free to ask any questions you may have, whether about the development choices we’ve made, or about the product itself. We’re excited to continue to build a community around this project. 

——

For those already familiar, I’d like to share some progress updates. 

First, I’d like to introduce Leolazz, who’s joined the project as our 3rd core maintainer, alongside ShoshannaTM, and myself!  

Second, I’d like to share gratitude for the warm and supportive reception Libre Closet has continued to receive. It sincerely makes my day when we get a new feature request or comment about how users are enjoying it. Since the first post, we’ve gotten 234 Github stars, over 10.8k docker image pulls, multiple community PRs contributed, and many helpful issues filed.

Latest News - Significant Performance Improvements:

We've refactored the server resulting in nearly a 2x throughput increase, almost half the latency, and the lighthouse speed score has gone from 68/100 to 99/100.

Latest Releases:

• v0.3.2 - June 09, 2026: Added background removal toggle for garment image uploads.
• v0.3.1 - May 26, 2026: Refactored server resulting in nearly a 2x throughput increase and almost half the latency.
• v0.3.0 - May 21, 2026: Garment image background touch up tool
• v0.2.5 - May 1, 2026: Added option to disable register functionality
• v0.2.4 - April 28, 2026: Fix garment photo upload cropping

For full details refer to the CHANGELOG.

We can’t wait for everyone to try it out, and we hope you enjoy v0.3.2 of Libre Closet! 

Public: https://librecloset.lazz.tech/

GitHub: https://github.com/lazztech/Libre-Closet

@

I read every single day. At home it's on my Kobo running KOReader (yes, I'm that open-source guy), and I love it. The problem: I don't always have the e-reader on me. On the train, at work, waiting somewhere — I just have my phone.

I tried Kobo's own Android app to bridge the gap and... I really didn't like it. Promos everywhere, adding your own books is a pain, the reader itself feels clunky, and the Wi-Fi handling is annoying.

So I built my own thing: Varbook, a small self-hosted EPUB library.

You drop EPUBs into it in one click. From there:

• They're readable on your phone through a simple but well-made PWA. Books are cached locally, so you can read offline; when you're back online your reading position syncs to the server.
• The server exposes everything over OPDS, so any compatible app works (KOReader, Moon+ Reader, etc.).
• I also wrote a KOReader plugin that pushes/pulls your reading position to the server in a single gesture.

My actual daily workflow:

• Evening, at home: I wake up my Kobo in KOReader, tap the top-right corner → Wi-Fi turns on, my current book jumps to the right position, Wi-Fi turns back off to save battery.
• I read.
• Done reading: tap the top-right corner again → Wi-Fi on, my reading time + position sync to the server.
• Next day, at work: I open the PWA on my phone. It drops me exactly where I left off, and syncs my position on every page turn.
• Evening: back to the Kobo, which picks up my position from the phone.

All of this with fully open-source software, no commercial service in the loop, my books staying on my own server.

The trickiest part was cross-device position sync — every reader engine (epub.js in the browser, KOReader's CREngine, Moon+) tracks position differently. Varbook uses a "pivot" format based on EPUB spine items (chapter index + percentage) so your position survives the jump from one device to another without throwing you 30 pages off.

It's open source (MIT), built with Laravel + React, and ships as a single Docker container (SQLite by default, no external DB needed). The entire UI is translated in English, French, and Spanish.

Honest disclaimer: a good chunk of this is vibe-coded. That said, I've been a developer for 20 years, so it's opinionated vibe-coding — I know what I'm looking at. It's been used daily and intensively by about 5 people for the last 3 months, and I keep improving it regularly. It's not bug-free, but I'd call it reasonably stable. I'm being upfront so you know what you're getting into.

There's a free public instance if you just want to try it without installing anything: https://varbook.hophop.be/

• Full write-up on my blog: https://trucs.hophop.be/en/blog/varbook-bibliotheque-epub-self-hosted
• Code: https://github.com/ndieschburg/varbook
• KOReader plugin: https://github.com/ndieschburg/varbook.koplugin

Happy to answer questions or hear what's missing — it scratches my own itch, but I'd love to know if it's useful to anyone else.

Hi everyone

I posted before here. I'll try once more but don't want to get over bearing.

I'm trying to self host all my contacts and my calendar.

I've managed to install radicale but there very little ui and I'm not actually sure how to import my contacts and calendar, or how to start using it with a client.

This is all I see

I've set up the calendar and contacts server but I can't find any security settings to password protect it

Any guidance would be awesome, thank you

So far, my self-hosting has been limited to Pi-Hole, and a static website. I now want to try out something new, an Immich server.

I have a static IP from my ISP, so I don’t need to rent out a VPS. However, given that this IS a home internet, I want to be extra sure that it is going to be secure.

In my existing website, I use Fail2Ban + BadBotBlocker + Anubis + Nginx rate limits to protect it from scrapers, bots and malicious users, and it works well. With photos (especially family photos) at stake, I just want to know more on how to protect my server.

Add: thanks for the helpful replies. I will be sharing the photos with family, many of whom live abroad.

Is anyone aware of any self hosted portfolio tracking software?

Something like TradingView or Yahoo Finance, where I can input my trades, and track tickers.

I recently found out that you can get up to 3 free .eu.cc domain from GNAME, which also claims that you can renew for free when its within 90 days of expiring. So I got one to check it out.

Obviously, the next step is making one of my local machines act as the target destination for any queries to the address, so it becomes accessible for the wider web. I'm not entirely sure, however, what to configure on GNAME (there's the option to setup A and AAAA records, which I suppose I should just point to my IP, but there's also CNAME, TXT, NS, SRV and what configurations/programs my local server (rPi 3) needs to have running besides a webserver (Apache2 or Nginx)

My intent is to have it run a single-user fediverse server, possibly friendica, as it seems to have the best support for seeing all sorts of APub posts. If that proves too heavy for my old pi, I'll try one of the lightweight APub alternatives

I know I'll also need to do some configurations on my router, so I'd appreciate help on this, too.

Hi all, my Unifi Doorbell just died after only 4 years of service. I've been pretty disheartened with them lately, other products haven't lived up to the company's promise.

So I'm not looking to replace my networking stack yet, but I am looking for a doorbell camera. I only have the Unifi machine, but I also have an extensive docker/kubernetes stack, and mostly I want to use it with Home Assistant.

Any recommendations? Open to software, hardware, you name it. I have a few other Unifi cameras too, if they could be brought into the fold while I slowly migrate, I'd be interested. Thanks!

There are so many options to get started with self hosting that I feel myself stuck in the "paralysis of choice". For a novice, does anyone have a good resource for the equivalent of good/better/best paths that cover the "basics" (In my mind this is hosting images, music, video, connected home controls, search and email)?

Thinking something like first try path A, if you feel comfortable and your HW can handle A, then try path B, etc. I guess a it of a tutorial mode feeling where you get exposed to key boxing blocks initially and then you are released into the large open world on your own.

I know the advantage of this movement is the choice and the well distributed variety, but just feels hard to start.

I have an old laptop, an SFF workstation and a NAS to play with.

Any suggestions?

Edit: Thank you all for a very generous response. I knew this was a tough ask from the start because, by design, this area is vast and constantly evolving. A lot of great starting points here that I'm now considering.

I only read about people using continuwuity and tuwunel, but apparently none are using conduit. When searching, I only find "hate" against conduit, but no actual reason why people prefer the fork, except some ominous comments stating that it is practically unmaintained (which is not true). I found that conduit has the majority of features implemented, except minor things like threads (which is still WIP, to be fair) and presence. Also, it is rock solid, only using minimal resources. It may be slow in development, taking a bit longer to implement a new feature, but not too much longer. Or am I missing something the others have to offer?

If you are running a conduit fork, what is your reason for leaving conduit, and if you are running conduit, why didn't you switch?

If it is not obvious: I mean compared to conduit and its forks, not synapse, ....

I am trying to increase the upload limit on my matrix server. I would like to push it to 500MB, but it keeps failing the upload past ~180MB. There is very little information about the failure, the client just says "Unkown error", nginx says "error 499", which means the client disconnected to quickly. Additionally, trying to recreate the failure with curl just results in a success, so the issue seems to be with the client. I tried with element-web, element desktop, element x and cinny and they all have this issue.

I run a continuwuity server on a Raspberry Pi 4B, behind two nginx reverse proxies and a rathole tunnel. Continuwuity, and the two reverse proxies run inside docker compose projects. Here is my architecture :

                   __
                 .(  ).
               (`Cloud )
                `-----`
                   |
                   V
          +- Outside server -+
          |   +---------+    |
          |   | rathole |    |
          |   +---------+    |
          +--------|---------+
                   |
+- Home network ---|-------------------------+
| +- RasPi --------|-----------------------+ |
| |                V                       | |
| |       +- tunnel docker -+              | |
| |       | +---------+     |              | |
| |       | | nginx 1 |     |              | |
| |       | +---------+     |              | |
| |       +-----|-|---------+              | |
| |             | |                        | |
| |             | +- other services -->... | |
| |             |                          | |
| |             V                          | |
| |       +- matrix docker --+             | |
| |       |   +---------+    |             | |
| |       |   | nginx 2 |    |             | |
| |       |   +---------+    |             | |
| |       |        |         |             | |
| |       | +------V-------+ |             | |
| |       | | Continuwuity | |             | |
| |       | +--------------+ |             | |
| |       +------------------+             | |
| +----------------------------------------+ |
+--------------------------------------------+

Of course, I made sure to increase the upload limit in Continuwuity :

max_request_size = 500000000

And in both nginx instances :

client_max_body_size 500M;

From what I can gather from other issues on the internet, it seems it could be related to timeout errors. Although they all seem to be talking about 2-8Gb files, I am probably running much weaker hardware than they do, so it checks out.

I tried setting the following values in both nginx instances :

location / {
    proxy_connect_timeout       600;
    proxy_send_timeout          600;
    proxy_read_timeout          600;
    send_timeout                600;
    proxy_next_upstream         off;
    proxy_buffering             off;

    proxy_pass ...;
}

And setting timeout values in Continuwuity :

client_receive_timeout = 75
client_request_timeout = 180
client_response_timeout = 120
client_shutdown_timeout = 10

Since that didn't have any effect, I bumped them by 20x and 40x respectively :

location / {
    proxy_connect_timeout       18000;
    proxy_send_timeout          18000;
    proxy_read_timeout          18000;
    send_timeout                18000;
    proxy_next_upstream         off;
    proxy_buffering             off;

    proxy_pass ...;
}

client_receive_timeout = 3000
client_request_timeout = 7200
client_response_timeout = 4800
client_shutdown_timeout = 400

But that did not have any effect. I also looked at modifying element-web's settings, but there doesn't seem to be anything related to timeouts.

I also saw that encrypted vs. unencrypted rooms might have an effect, but I got ~190MB max in encrypted rooms and ~180MB in unencrypted rooms.

Finally, I tried using curl :

curl -X POST https://server.domain/_matrix/media/v3/upload -H "Authorization: Bearer <token>" -H "Content-Type application/octet-stream" --data @200mb.file
# success
# returns a mxc:// url
curl -X POST https://server.domain/_matrix/client/v1/media/download/server.name/file_id -H "Authorization: Bearer <token>" -o 200mb_copy.file
# See that the two files are identical

I am at a loss. What can I do to solve this issue?

Self-hosting journey update, and WordPress: latest development from a super-newbie

@selfhosted

I must recap as I set my instance to delete 2-weeks-old posts.

Months ago, I talked about my very first journey with self-hosting my digital services, including my website.
As I'm not very skilled with sysadmin stuff, I use a YunoHost installation with all its pros and cons.

Having severe accessibility needs (I'm totally blind) I have limited choices for what concerns CMS software with related extensions if any. So after months of exploration and test, I've come back home. To WordPress.

Last time I updated Fediverse about my experience, I was struggling with multisite network giving an unpleasant error in the non-main site, such as "too_many_redirects"
Making it short, I discovered that YunoHost doesn't let me run a multisite properly when installed in a subdomain such as blog.domain.tld
So I had forcefully to install it in the main domain, and a subdirectory such as domain.tld/wp

Now I'm concentrating on my theme, I will clone it with the plugin "CreateBlockTheme" then activate it network-wide.
I need a multisite for multilingual, as all current multilingual plugins have poor accessibility support, and are mostly paid.

Then I may need a new taxonomy registered to organize stories, the glossary plugin, SEO plugin, ActivityPub, and I should be all set!

The last, hard, challenge I have, is the fact that now my site runs into "domain.tld/permalink-post" for Italian, and "domain.tld/english" for English
The new one should run "domain.tld/wp/post" and "domain.tld/wp/english/post"

YunoHost doesn't let me build a WordPress site in the root directory with multisite installed, so I must find the way to tell nginx I want the product to be physically on /wp/ but browser can point to domain.tld/post or domain.tld/english/post...

And if possible, this change to be in a file on its own, in order to be able to delete it without damaging the whole nginx conf.

Last detail, I'm on hostinger, kvm2 package. vps.

#experience #multisite #nginx #SelfHosting #WordPress #YunoHost

Recently I spent part of the weekend to build a small companion for Traefik. Beacon automatically scrapes the Host() part of Traefik rules and announces them via mDNS in the local network.

The idea is to use this in our greenhouse, hence the greenery in the name. Shooting for a small solar powered RPi Setup, and this gives me easy acces via local Wi-Fi e.g. for debugging or sensors/bridges.

I hope to spend some time around the ideas of air gapped/remote self hosting.

Say ww3 kicks off and power goes off - how are you keeping your servers up? Solar panels and batteries?

What if there's a biblical flood and you dont have the means to build an arc? All your servers are destroyed beyond repair?

What if you heard the Feds are coming to cart you and your servers away cos they suspect you of bad mouthing Emperor Tromp? (you're on the run or subject to months of torture and yeah, you're never getting your kit back)

What if theres a war and Luxembourg (you know, the enemy) let's of an EMP pulse that kills your servers and all the infrastructure (power, internet...). How do you access all those cherished pics on Immich?

I'm not suggesting any of this will/can happen, its all just for lols, but have you made any contingency plans? Big binders full of printouts, bug-out bags, those flower-type solar things that track the sun, Faraday cages....

Cross-posted from "Self-hosting email the hard way from your own routable IPv4 block up" by @lemmydev2@infosec.pub in !pulse_of_truth@infosec.pub

Comments

At 10.06.2026 openmediavault 7 will become EOL because Debian 12 estimates EOL (end-of-life) for the same time. This means no security/bugfix updates will be released anymore. Please upgrade to openmediavault 8 to be up-to-date.

2026-06-10 for people using a not insane date format. Already updated some of my omv installs, went without a hassle. Check if your plugins are supported, some of them were removed.