whysofurious

joined 2 years ago
[–] whysofurious@sopuli.xyz 3 points 1 week ago

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

[–] whysofurious@sopuli.xyz 2 points 1 week ago (2 children)

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^^

[–] whysofurious@sopuli.xyz 1 points 1 week ago (2 children)

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 :)

[–] whysofurious@sopuli.xyz 2 points 1 week ago (4 children)

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?

[–] whysofurious@sopuli.xyz 2 points 1 week ago

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.

[–] whysofurious@sopuli.xyz 1 points 1 week ago (4 children)

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

[–] whysofurious@sopuli.xyz 1 points 1 week ago (1 children)

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..

[–] whysofurious@sopuli.xyz 2 points 1 week ago (3 children)

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 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 :)

[–] whysofurious@sopuli.xyz 6 points 3 weeks ago* (last edited 3 weeks ago) (3 children)

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.

[–] whysofurious@sopuli.xyz 1 points 1 month ago

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 :)

[–] whysofurious@sopuli.xyz 1 points 1 month ago

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.

[–] whysofurious@sopuli.xyz 1 points 1 month ago (1 children)

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! :)

 

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!

view more: next ›