![]() ![]() The re-name where they kept the branding the same for both but decided to append a SCALE/CORE suffix also screwed everybody over because the years of forums/community guides/blogs and the SEO for it all. If you're just going to lock away 95% of the knobs, why did you pick something so complicated for your platform!? Given the absolute complextixy of the k8s ecosystem, any attempt to dumb-down it's management and then shoe-horn it into a storage appliance mgmt interface does nobody any good. I am a very happy CORE user because I believe that storage and routing are things you just don't virtualize unless you're a masochist. proxy-body-size: 256mīut I've found it to be a huge pain in the ass on TNAS Scale. # For big file uploads to Nextcloud make sure pod resource limits permit at least this much ram usage! I run nextcloud on vanilla k8s with the normal nginx ingress and was able to overcome the file upload limits with these annotations: apiVersion: /v1 I believe your approach of modifying the php.ini file and the nginx config would have been correct for the old/CORE based approach where jails were used but that's not going to be sufficient here.Ī quick google didn't really turn up any details about how the "official" apps are implement or where the configuration(s) for them live so you'll have to figure that out or find docs that explain how things are set up. but i'm going to assume that they are doing it that way for consistency. I don't know if k8s is used internally for the "built in/official" apps though. at least that's the case for all the truecharts stuff. ![]() The SCALE product is a bastardization of abstraction on top of kubernetes which is what powers the additional apps. Could you provide more information on that? Maybe an example? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |