owncloud-complete-20231213.zip <=== html/js/php , components for a web server? 26,851 files
They're so wrapped up in what they're doing, they don't even point out the obvious.
They're not bringing this thing up from "nothing". An install procedure should
go into some amount of detail.
https://doc.owncloud.com/server/latest/admin_manual/installation/
phpenmod smbclient
systemctl restart apache2 <=== they're "restarting" software they didn't even install.
The keyword "apache" means "a web server" is present
on the machine.
*******
latest--nextcloud.zip 22,897 Files <=== php files mostly
Name: Nextcloud Manual.pdf 189 pages (This seems to be a client manual for using the web interface as a user)
Size: 16,051,189 bytes (15 MiB)
Name: Reasons to use Nextcloud.pdf "Groupware"
Size: 976,625 bytes (953 KiB)
The two seem to have a slightly different focus.
I haven't seen the word "Apache" quite yet.
OK, now I see the Apache keyword. There is mention of packages
for servers here, things you would load into Linux in one step perhaps.
https://docs.nextcloud.com/server/latest/admin_manual/installation/source_installation.html
This means you will be responsible for web server security (CVE related to Apache),
plus all the packages that install as helpers (presumably some version of PHP).
And so on. That's why using a Ubuntu VM and their Snap package, might
be a "one and done" from a "what software do I need" perspective.
However, there will be a firstrun behavior, configuration questions,
and you'll need to define a "server.local" at 192.168.1.2 , and of course
if there's a reverse DNS lookup, combined with your certificate, some
authentication processes aren't going to be happy. You know the drill.
That's why my hmailserver today, is broken, and it won't even work
on vanilla ports either.
With a Snap, there will be Snap Updates. If there is an Apache server
in there, it will be kept up to date. One of the disadvantages of
Snap, is access to files outside the snap environment (which is where
your NextCloud will keep the user files). There might be limits on where
the server can "point". It won't be allowed to write just anywhere.
The first time I ran into a Snap, it seemed... un-debuggable. I hope
that has changed since early times. For example, Firefox Browser on
Ubuntu desktop, is a Snap, but that usually isn't broken. I haven't
tested that extensively for "reach". Like, whether it can download
a file into other than ~/Downloads.
Paul