doeknius_gloek

joined 11 months ago
[–] doeknius_gloek@discuss.tchncs.de 7 points 1 week ago (1 children)

Having a solution that works for you is never a bad thing.

Now it comes down to what you want to archive: Do you want something that just works? Great, you're done - now go on and do some other things that you like, that's perfectly fine. Or do you want to learn more about servers, virtualization, linux, networking and selfhosting in general? Then there are a million ways to get started.

I'd suggest to setup a little lab, if you haven't already. Install Proxmox on your server and run CasaOS inside a virtual machine. Now you've learned about hypervisors and virtual machines. Afterwards you could create a second virtual machine to play around - maybe install debian and get used to the linux cli. Install docker manually, run some apps using docker-compose. Now you're already doing some stuff that CasaOS does under the hood.

The possibilities are endless, the rabbit hole is deep. It can be a lot of fun, but don't force youself to go down there if you don't want to.

Thanks for your response! It wasn't my intention to sound overly critical. Congratulations on your spectacular growth and good luck for the future! I'll definitly keep an eye on ChartDB.

[–] doeknius_gloek@discuss.tchncs.de -2 points 1 week ago (2 children)

Interesting project. I wonder though how a repo that's merely a few months old and has only seen 117 issues in total does accumulate 9.8k stars? Seems a bit fishy to me.

This reminds me of nebula although nebula does require a central server to coordinate hosts.

[–] doeknius_gloek@discuss.tchncs.de 30 points 3 weeks ago (3 children)

Security is something you do

Like by reducing the attack surface on internal APIs?

I don't even necessarily disagree with you, everybody has to decide themselves if this app offers enough upsides to be worth the downsides.

That being said, instantly calling OP stupid and their project crappy is just not the way to get your point across and in general considered a dick move.

[–] doeknius_gloek@discuss.tchncs.de 12 points 3 weeks ago* (last edited 3 weeks ago)

Thanks for the write-up! I've settled on Immich but it's always interesting to hear about other peoples perspectives.

Regardless, though, my network setup usually consists of Factory Default Settings -> Assign a Static IP -> Configure port-based VLANs. It's not particularly advanced. Most likely I wouldn't even need to use anything other than the web-based management interface.

That's pretty much what I'm doing with my Mikrotik switches too and I never had to touch the cli.

[–] doeknius_gloek@discuss.tchncs.de 30 points 4 months ago (1 children)

Never thought I'd agree with Goldman Sachs.

Musk wrote that X "has no choice but to file suit against the perpetrators and collaborators" behind an advertiser boycott on his platform.

So he's going to sue himself then?

If somebody is going to try to blackmail me with advertising, blackmail me with money, go fuck yourself. Go fuck yourself. Is that clear? I hope it is.

Elon Musk, 2023

I guess it was pretty clear. What a clown.

Funny to seem him arguing against HibernateDelaySec because of possible data loss, yet if systemd-tmpfiles purges your fucking home directory it's "documented behaviour". The superiority complex of some people...

I use Wasabi S3, but only for my most critical data. For full backups including large media I setup a offsite NAS.

Regarding tooling I'm really happy with Restic (coming from Borg).

[–] doeknius_gloek@discuss.tchncs.de 8 points 6 months ago (2 children)

I'm currently having a good experience with MikroTik. I think their products provide a good combination of features and pricing. There are a "CRS317-1G-16S+" and a "CSS326-24G-2S+RM" in my rack and I have my eyes on the "CSS610-8P-2S+IN" as a efficient little POE switch.

I haven't used Ubiquity, so I can't compare these two brands.

For APs I'm currently using TP Link Omada with a selfhosted Omada Controller and for Routing, DNS, Firewall and stuff I use OPNsense.

view more: next ›