whysofurious

joined 2 years ago
[–] [email protected] 1 points 3 hours 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.

[–] [email protected] 1 points 3 hours 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! :)

[–] [email protected] 2 points 3 hours ago

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

[–] [email protected] 1 points 3 hours ago

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

[–] [email protected] 1 points 3 hours ago (1 children)

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.

[–] [email protected] 1 points 3 hours ago (1 children)

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

[–] [email protected] 3 points 2 days ago

Thank you! And thanks for sharing your experience :)

[–] [email protected] 2 points 2 days ago (2 children)

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.

[–] [email protected] 1 points 2 days ago (3 children)

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)

[–] [email protected] 2 points 2 days ago (3 children)

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.

[–] [email protected] 5 points 2 days ago

Archwiki is really an invaluable source of information, I use it regularly even if I never touched Arch.

[–] [email protected] 2 points 2 days ago (3 children)

Nice to know I am not alone! And I only recently started with linux, so I guess it's not really something that goes away with time 😂

I need to take a look at an immutable OS sooner or later, although I feel I would be annoyed for not being able to modify stuff for my liking (probably I will never be satisfied in any case)

 

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

view more: next ›