Thanks, that’s all I needed to know :)

Nice, thanks for the details :) Suwayomi usually obtains png as far as I remember, is Kavita able to read anything that Suwayomi gets, without issues or post-processing needed? Sorry for the many questions^^

No worries! I was pretty much confused myself from the beginning, so I am definitely open to any workflow :) And I do plan to read on one device only as well. My centralized approach was mostly about saving space on the tablet/reader and a possibly easier management and freedom to move to something else in the future, rather than a strict requirement.

I used to have tachyomi on my eink tablet, so this definitely rings a bell, but I thought the only working solution was Suwayomi.

I will look into Mihon and its support of selfhosted solutions then, seems like a nice combination :)

That seems nice, thanks for sharing! I read Kavita has some weird requirements for path organization for it to work correctly, or do I remember wrong? Do you also do metadata editing in Kavita itself?

Thanks so much for sharing and for such a detailed answer! I understand where you are coming from, I don’t have a tablet so for me an e-ink reader would not be too much (I work on my laptop most of the day and I don’t like reading on the phone, so a device like that is a sweet spot for me).

I tend to mostly read bw manga (webtoons I read it on my laptop usually), but I heard the same about e-ink colored devices (and most generally that you “shouldn’t” read bw on colored eink screen).

For the same reason as yours (mandatory calibre for transferring), I am looking at Onyx Boox e-ink devices, which are basically android tablets but with an eink screen. This gives me the freedom to install whatever app or sync I want, limit my exposure with something like nextdns, remove google stuff as much as I can, and things like that.

In the end I guess it’s a balance between actual functionality and convenience, if a whole pipeline become too hard to manage than doing some parts manually might actually be better.

Thanks! Never heard of both, but I will definitely check them out :)

You could just leave it in airplane mode, but not being able to use the internet to pull down books from your Calibre-web server means you may as well just send books via Calibre.

That’s sadly true. I am thinking of waiting for the kindle to die too, but I was looking more at the onyx boox go 6, since I already know I can run whatever I want on there.

Pretty much, apart from that I often add them and only fix if necessary, e.g. they’re not going into series properly.

I see, thanks! Do you mind if I ask you where you can find them with some good metadata? My attempts have been not so good until now…

Interesting, thanks! I agree with you about using specific tools for different purposes. Tbf my kindle is a 2018 model put on airplane mode since 2021, maybe I can do something about Koreader.

About comics/manga, didn’t know about comictagger, it seems very good. So your process here is get comics -> comictagger -> upload to server and kavita, correct?

I am not sure about how lightweight they are (but I guess more than WordPress for sure) but on the federated side of things you have plume (https://joinplu.me/) and writefreely (https://writefreely.org/) that you can selfhost. Not super sure about how much you can customize them.

Thanks for the composerize link, it’s super useful indeed!

Yeah I took a quick look at podman and nope for now 😂 docker compose it is and it’s working wonderfully :)

Don’t really know what some of these things are, which also means I haven’t encountered them (yet), if I will I’ll make sure to read more about it. To be honest, for now I’m just doing normal compose, everything behind tailscale. At one point I’ll need something like caddy for a reverse proxy to help with sharing services with a couple of family members, but always behind tailscale, no public exposure.

Yup I read about the folder thing but got stung by it as well ahah

Thank for taking the time to explain, I am almost done with the transition of all my services and I did exactly like you suggested and everything works perfecty! :)

Ah! I started with Yunohost too (and actually still have it on a Pi), definitely opened the port for all this in a nice way!

I agree with you on Docker, it can get complicate but the basics are very very easy. I would probably go with DockGe, I tried both before but didn’t like much portainer :)

But thanks for both comments :)

One day I will look into NixOS, I am eyeing it for a while now, but I don’t feel confident enough with my Linux skills to switch. However, I do agree with you, and it’s exactly what I am doing, stripping the compose files of all the CasaOS stuff, use one per service, and versioning them in git. I am also learning about .env files and other things that I wasn’t really aware of before, it’s fun and very customizable :)

Thanks for all the suggestions :)

The first jump to Debian was the most intimidating for me learning CLI commands for the first time and not having defaults chosen for me, but it was liberating to finally learn the actual tools and not just learn a GUI abstraction for tools.

I feel it, I am in the process now of transporting everything and I couldn’t agree more. I have a semi-idea of trying nixOS sometime, and I only recently learned about podman existence, is it that different to docker? I read it’s not a 100% replacement, but I guess it depends on the use-cases.

I see Proxmox mentioned a lot, but haven’t had the time to test it out. I will stick with Debian+Docker for now, but if it’s that convenient I might take a look at it one day :)

And you can experiment as much as you want and break stuff.

I really like this part especially

Thank you! And thanks for sharing your experience :)

Thank you for the answer :)

I don’t know much about CasaOS, but presumably you have the ability to stop your containers and access the filesystem to copy their config and mapped volumes elsewhere?

Yes absolutely, they provide a nice filebrowser which can also be mounted as a samba share (which they setup during install), in case one doesn’t want to use the terminal for everything.

As far as networking, from what I could see the only real change casaos was doing was mapping its dashboard to port 80, but not much more. Is there anything more I should be aware in general?

When self-hosting, the more you know about how things actually work, the easier it is to fix when something is acting up, and the easier it is to make known good backups and restore them.

Exactly, I feel I am at the point where I got my hands dirty enough that I can dive deeper into knowing things, not necessarily immediately, but step-by-step.

Nice to know that someone did the same move, and happy that it went well :) did you have anything specific to remove from the CasaOS compose files? (I know they fill it with a lot of stuff useful for their categorization)

This is exactly how I feel! Everything works but I feel there is a lot that was "“forced’” on me that I don’t use, and conversely a lot that is going on 24/7 and I don’t really know how it works.