I hope I have found the right place for my question(s), because everything I try to find related to “NextCloudPi” is mostly connected to Raspberry…but I want to install NextCloudPi on a PC with an installed and running Ubuntu 22.04.3 LTS.
The reason why don’t choose NextCloud is because I like the NextcloudPi-extra features, like Dynamic DNS support, etc…
And please, I don’t want to install it via docker…
So here my question: Is there a noob-proof step by step guide for what I am looking for? That would be wonderful!
The Hardware ist an icore5, 16GB Ram, 500GB SSD for the running system/Ubuntu, and a 4TB HDD which should contain all the data that will be used by NextCloudPi.
There’s also a curl install script that you can use on bare metal, in Linux containers or in a VM. But I think this has only been tested in Debian environments, so it probably won’t work on bare metal Ubuntu, in which case you could run a Debian VM or a Debian LXD container on Ubuntu, and run in there: https://github.com/nextcloud/nextcloudpi#curl-install-scripts
Well, it provides the application, in this case Nextcloud, with most of its bells and whistles, but it doesn’t mess with the underlying system, which is one of the advantages of Docker. And if you’re only running Docker applications on a particular box or VM, there’s not much to do on the underlying system, apart from the occasional apt update && apt full upgrade.
Not really an issue, imho. DynDNS can be done almost anywhere, and almost all DynDNS providers offer a variety of documented ways to update the IP, and in the worst case you can create a cronjob on your toaster that triggers the API of your DynDNS provider every 5 minutes
Apart from that, there will always be a user who uses DynDNS service XYZ, which is not supported by the built-in DynDNS client, just like with the DNS challenges for Let’s Encrypt, and so I can understand that software maintainers don’t want to deal with this, otherwise they also become supporters for the various DNS services used by their users
You don’t really want to upgrade Nextcloud automatically, trust me.
Great, then it obviously doesn’t contradict with automatic backups, so what was your question again?
Sorry if that sounds a bit harsh. But Docker doesn’t contradict these things per se, the AIO maintainers just implement certain things and others they don’t. And in particular, DynDNS and reverse proxy functionality is better done separately from the application appliance because it increases the flexibility and possible use cases for such an appliance. It also relieves the maintainers of the appliance from having to cover hundreds of use cases and support just as many DNS providers, which can never be enough anyway, because someone will always come along whose use case or DNS provider isn’t covered
Ah, now I get it… That was an answer or suggestion to @cmburns3 to use AIO…
But why not ask something like, you could also use AIO, which covers most of the features of NextcloudPi, except for DynDNS and Reverse Proxy, the latter of which is not covered by NCP either, but of course both can run behind a Reverse Proxy, except for the fact that it uses Docker, which you don’t want to run for some reason I don’t understand, and so I concluded that you don’t want to run it because you think it contradicts all sorts of things.
Also, @cmburns3 didn’t explicitly mention AIO, which was automatically ruled out anyway because, well, it runs on Docker, only Nextcloud, and that they don’t want to run Docker.
Still, I should have seen the quote in your post, although the thread now probably contains more useful information than would have come from your rather defensive question
I think not wanting to use a particular thing like Docker is a perfectly valid reason to ask for alternatives. That’s one of the reasons why I choose a manual installation, but unfortunately there are some things you are almost forced to run in Docker these days, like Imaginary or Collabora if you want the best experience
I agree, but that’s kind of besides the point now, because I missunderstood your reply to cmburns3 as general question, so my replys to you were given under false premises, so to speak, which was due to my lack of attention while reading your post. Sorry for that.
So from my side there is no reason to continue this discussion, unless OP has further questions…
However, I still think NextcloudPi is a nice all-in-one solution, and things like DynDNS built right into it can definitely be a nice thing to have for home users who just want to run Nextcloud. I just don’t think it makes sense to integrate things like that into an official appliance like Nextcloud-AIO, which also has (small) business customers in mind.
It was meant as a hint, your resources are capable doing much more than one server.
First try to understand NextcloudPi, and how it differs from nextcloud.
