I will now certainly, though i am pretty excited.. But i only have 1 Home Server atm, and spending time of restoring my setup if stuff goes wrong is nothing i now have time for anyway. Better to be patient ;)
There will be an upgrade path from TrueNAS Core to TrueNAS SCALE (initial prototype for which is already in production), so it might be worth getting to know TrueNAS Core 12 already... to get familiar with the core systems like ZFS, Shares and the GUI ^^
As K8s seems to be the industry standard now, i am sure that work pays off and the experience you gain with this. Thats what i like about home labbing, i learned so much in the last maybe 1-2 years of moving from Windows to FOSS... Amazing.
Preciesly, thats why i'm taking the time. I never would've if it was "just for moving to scale", but it helps me get more into the mindset of devops and how ZFS (which I also am active in the community for) is actually used.
That sounds encouraging! Will definetly try this when i have some free time to tinker!
Have fun,shout out of you need a hand :)
It is because of (percived) security, but likely also because i am still new to docker and homelabbing in general and used KVM exclusively. Like the guy who comes to the party when it already moved on (to K8s in this case) ;)
Yeah k8s has a learning curve, thats why it hasn't been widely adopted in the amateur-homelab scene (the homelab scene with people that aren't working with containerisation on a professional basis). A shame really.
Learning about K8s and more about containers in general is on my todo list, and then i think i am more open about moving more stuff from VMs.
But with my current setup running stable and comfortably and without perf issues on my budget Ryzen 1700, and with not much free time, it will be some months anyway to take that step..
My test VM with SCALE is a 8 threads from a 1700, don't underestimate the good 'ol 1700!
Yeah, Nextcloud IMHO is sadly plagued by quality issues. Security, performance.. Dont leave a good impression, even to a observing noob like me from the bug reports i read and forum posts.
Well, the general impression isn't nice. What I find more worrysome is the fact they actually sell "support" for features that are totally broken by design. See for example:
https://github.com/nextcloud/user_saml/issues/455
Combined with continuesly adding all sorts of features (how many office suits are integrated by now? 4?), it creates some questions:
- Where do their priorities lay, which users? Enterprise? Free Users? Indirect users (via enterprise)? Contracts with integration partners?
- Who is paying for this? Is it really the support contracts that bring in the money, or are they actually getting more money out of all these integrations? (why else integrate all those office suits...)
The reason I rant on about this a bit is the contrast with IX systems:
IX is clear where they get their money from, is clear where their priorities lay, is clear about what free users can expect and doesn't hide manuals behind a paywall.
I'm not against the "Free/FOSS with prenmium support and/or hardware"-model, but there is a good way and a bad way about doing this. Big compliment for the way IX is doing things, even though i don't always agree with every choice they make either :)
I moved my personal files into Syncthing for this matter, only use it now as CalDAV/CardDAV server.
I currently use their sync, I think it's pretty decent. But big shoutout to syncthing too, I love that tool :)
Really not sure which I would rather use.
And even there i am looking to move to EteSync, which is end to end encrypted, while self hosting is also possible and FOSS ofc.
I have end-to-"50kg-inhouse-server"-to-end encryption, I find that sufficient personally. But that's also because I'm quite literally sitting on (below) the actual server(s). :')
Anyway, did any tests with EteSync yet?
Lack of documentation sound not good. I will try to set it up when i have some free days; Thanks for the offer, that setup of yours could come in handy then!
Well there is great documentation, but a lot if not k8s specific... which you need to translate to the (quite different) syntax used with K8S.
Docker setup is pretty easy, i've a swarm example too if you need one :)
So long for my off-topic on this thread, thanks again and looking forward for SCALE! :)
Well, offtopic isn't a problem as long as it adds something to the thread. Educating eachother off-topic really never some something a moderator would bother with here, don't worry :)
(my nextcloud comments however are a bit of a bad-boy comment though O:) )