NextCloudPi VS kuma

nextcloudpi.com

It works great and is reasonably fast if you connect it over ethernet. If you have a newer firmware, which has already enabled the boot from SSD on your pi it is super easy (otherwise just Google how to set up boot from ssd with a microSD). Afterwards you can use the raspberry pi flashing tool to flash the image of nextcloudpi on your ssd. This includes the 64bit raspberry pi OS, a running Nextcloud instance and some other handy tools (like help to set up security features). The first setup can be done with the IP adress of your Pi in an internet browser of a device in your network. Here is the link to the image of NextcloudPi https://github.com/nextcloud/nextcloudpi

Issue 2 still persists and after digging around found this issue reported on git https://github.com/nextcloud/nextcloudpi/issues/1752 but cant figure out how to sort it

Install nextcloudpi (https://github.com/nextcloud/nextcloudpi) Install Nextcloud app on your phone.

If you want to update faster than the docker image is published, you'll have to build the image locally: https://github.com/nextcloud/nextcloudpi

My best experience in out of the box comes from Nextcloudpi: https://nextcloudpi.com/

Nextcloud is functionally similar to Dropbox, Office 365 or Google Drive but is self-hosted so you are in control of your data. This version is a lightly-forked version of NextCloudPi, which was developed for SBCs like the Raspberry Pi. Only a few changes from upstream and some SysV initscripts were required to get this working nicely in Linux Deploy.

https://github.com/kumahq/kuma is an CNCF OSS service mesh for Kubernetes and VMs. We're a control plane on top of Envoy proxy. Very actively developed project, some big adopters in the community, and we've just refreshed all of our Good First Issues.

And not just "Kuma" : https://github.com/kumahq/kuma

Another important change to make is that when you create the cluster, change the Nodes in the "Default pool" to use the COS (not COS_CONTAINERD) image type. There are some underlying issues when using Kuma with GKE, as noted in this GitHub issue, and this is the currently recommended workaround. Otherwise, you will hit pod initializing issues that affect certificate provisioning.

Taking things to a broader level, Kuma is another platform agnostic-OSS solution for service mesh and microservice management – with control plane support of Kubernetes, virtual machines (VM), and even bare-metal environments. Kuma was donated to the Cloud Native Computing Foundation (CNCF) by Kong and still actively contributes to the evolving code base.

Kuma Kuma, from Kong, prides itself on being a usable service mesh alternative. Kuma is a platform-agnostic control plane built on Envoy. Kuma provides networking features to secure, observe, route, and enhance connectivity between services. Kuma supports Kubernetes in addition to virtual machines.