I would like to start managing ebooks and manga properly. I don't have many, but I plan on increasing my collection. My requirements are not so strict, I don't mind getting the books/manga myself, but I am also curious about setting up LazyLibrarian at one point, is it worth it? (I already have other *arrs installed on my server). I had similar thoughts about Suwayomi.

My confusion starts from the accessories around all this: Calibre, CalibreWeb/Automated, Komga, Kavita, Audiobookshelf, etc. Does having a Kindle as reading device limits my possibilities to use any of these? Is setting up e.g. both CalibreWeb and Kavita redundant?

I guess my question is how is everyone using these services for their own library :)

Hi all! Does anyone have a spare Drunken Slug invite? Would really appreciate it :)

Edit: Thanks to everyone who commented and helped with suggestions! I moved to Debian + Docker compose only and everything went well and it's working perfectly!

TLDR: want to get rid of casaos from my home server and learn everything on my own from the beginning, am I crazy for wanting to wipe everything and reinstall the entire system?

Hi all! A few weeks ago I got a mini-pc (Beelink S12pro), a secondary internal sata ssd (thanks to those who helped me with the choice), and I slowly set up my server with quite a few services (the *arrs, jellyfin, immich, navidrome, gotify, uptime-kuma etc.) using casaos as overlay for everything (with Debian 12 as base and tailscale to access it outside my home). I like casaos interface, and it really helped me a lot in smoothing the process of approaching docker and managing a personal server.

However, I am starting to feel a bit restricted by casaos: almost immediately I was bypassing the 1-button install and customize the container to my liking, also if I need to change something deeper I always need to check if casaos has its own way of handling things. Plus, I don't really like the frequent connections to the app store (and I couldn't figure out how to change the interval), or the fact that everything casaos does is done as root, which also forced me to run some containers as root user. My server isn't exposed to the internet so I can be less worried, but I would like to know more about permissions and stuff without being forced to just run everything as root.

Removing casaos is apparently quite easy with an uninstall script, you can also keep your containers intact, however it will leave behind a lot of the dependencies installed and modification made through the install script, apparently.

I don't think these modifications will not be useful to me, but I would like to have a system when I know what I did, what is opened/installed/activated and what is not, and by just uninstalling casaos I will not have that. Note that I am also not against UIs, I think I will install dockge for easier managment of containers, but I would like the process to be learn->setup->use ui, and not the other way around.

Am I crazy for thinking about reinstalling the entire system and start from scratch? I have backups of everything: container data folders, compose files, various media. TBH, in one week of use there are not many things that are absolutely vital, moreover, most of the media are in the secondary drive which will be left untouched. Worst case scenario, I can also avoid restoring backups (except for the arrs which were the more time-consuming to set up).

In my mind these are the pros and cons

Pros: install stuff as needed and learn what does what, without having a script automagically doing that for me, probably gaining a deeper dive into docker/compose. No overlay, no mandatory root things, possibly less maintenance?

Cons: having to set things up again (system users, ssh access, tailscale, automount usb drives, mount points for the sata drive), possibly some container stuff will not just work by re-importing from a backup?

Does the selfhosted community have some advices or opinion on this? Maybe there are also easier ways I am missing, being kind of new to all this. Thanks in advance for any answer!

Hi all,

Quite excited for my first post here and for being able to join the club :)

I recently bought a Beelink Mini S12 Pro and put Debian on it. I did use yunohost for over a year and I experimented with basic nginx, fail2ban etc. on a vps but I can't call myself an expert around these things. For this reason I installed casa-os to ease my way into docker (maybe in the future I will do everything DIY, I do like the idea). I put everything behind tailscale to be able to access the server outside my home.

My idea is to have a media server (radarr and sonarr for movies and tv shows, plus navidrome for my music collection) and some other niceties like audiobookshelf and maybe immich. I still need to learn most things about the arr stack, transcoding and such, so I don't have any rush.

However, for all these things, I definitely need a larger drive, since the mini pc comes with a 512gb internal ssd.

The S12 also has a 2.5" drive bay (SATA3), but should I go for an internal drive or an external one connected via USB?

Things I am worried about the internal solution is mostly temperatures, everything is so clumped in there and I read some stories about faulty hardware basically heating the sata ssd to death after a while. On the other hand, usb connection is maybe less "stable"? I don't know. Also, if I go with SATA drive, should I go for ssd or hdd? I don't have too much budget to invest right now, so cost is somewhat a limit at the moment.

Seeking any advice here and happy to hear more expert people opinion on this, thanks! :)