> It did take a _lot_ of effort to migrating my existing data to the docker container
Or you could just use some external storage. Like SMB or something. And then you would learn what updates aren't 'a breeze'. And there is no built-in SMB support in the default container.
Since I'm running it since OwnCloud days too, I have an opinion on it and it's Not. Good.
Desktop client for Windows is miserable and sucks:
a) you have something with a name longer than 30 symbols? You know need to guess what the full path of that file in the error log
b) this is like 4th year when you have an option to see the errors in a separate window, except it's... empty. Not an empty error log, it' empty window
c) Oh, best part: if the client decided to update it would kill your Explorer first (like -9), install the it's shit and then... force reboot your machine without any questions
d) when you click on the client icon in the notification area it shows multiple icons what you would thing would do something. Except it's just opens the web-interface of the instance
For years mobile client couldn't work properly with a self-signed certs, which is quite ludicrous for a solution boasted as the pinnacle of self-hosting.
UI overall is shit, it's a legacy of early 2010 concepts with Googlisation on every not needed aspect. And just outright stupid ideas, which 2.5 developers at NextCloud couldn't test, like littering EVERY (sorry for caps) folder you navigate through the web interface with README.md. And shitting bricks on non case sensitive mounts, because yes, it's hard.
Server side is always running to pump out new versions, while abandoning and deprecating addons. Oh, addon you are using is now deprecated, besides being made a mere year ago? Tough luck. Stay on the supported NC version. Except it's not supported anymore because it's a year old now version.
Oh, since 2016 it's no longer a file syncing solution, it's collaboration software or even groupware. That means there are now office suite, chat, contact lists and whatever else, including an email client. This also explains why did NC 'bought' RC. Except all those parts are not integrated good.
And finally it's a PHP app with a tons of legacy code. As soon as something breaks you are drowning in multiple screen heights of errors of PHP code. And consequently all performance troubles are solved by throwing RAM and CPU at the instance.
5 years if things are not updated will have vulnerabilities. It might be that framework updates will fix them, or code changes needed, or code changes because newer versions of libraries are not backward compatible. Getting old NPM projects updates is hellish. Breaking changes are very common.
This is definitely true, but PHP is a special nightmare of a beast. I think overall PHP is underrated, and is a much better language and platform than people give credit, but damn two weeks without updating dependencies in PHP is rolling the dice. Keeping up with all of the cve's is a significant chunk of a full-time job.
Or you could just use some external storage. Like SMB or something. And then you would learn what updates aren't 'a breeze'. And there is no built-in SMB support in the default container.
Since I'm running it since OwnCloud days too, I have an opinion on it and it's Not. Good.
Desktop client for Windows is miserable and sucks:
a) you have something with a name longer than 30 symbols? You know need to guess what the full path of that file in the error log
b) this is like 4th year when you have an option to see the errors in a separate window, except it's... empty. Not an empty error log, it' empty window
c) Oh, best part: if the client decided to update it would kill your Explorer first (like -9), install the it's shit and then... force reboot your machine without any questions
d) when you click on the client icon in the notification area it shows multiple icons what you would thing would do something. Except it's just opens the web-interface of the instance
For years mobile client couldn't work properly with a self-signed certs, which is quite ludicrous for a solution boasted as the pinnacle of self-hosting.
UI overall is shit, it's a legacy of early 2010 concepts with Googlisation on every not needed aspect. And just outright stupid ideas, which 2.5 developers at NextCloud couldn't test, like littering EVERY (sorry for caps) folder you navigate through the web interface with README.md. And shitting bricks on non case sensitive mounts, because yes, it's hard.
Server side is always running to pump out new versions, while abandoning and deprecating addons. Oh, addon you are using is now deprecated, besides being made a mere year ago? Tough luck. Stay on the supported NC version. Except it's not supported anymore because it's a year old now version.
Oh, since 2016 it's no longer a file syncing solution, it's collaboration software or even groupware. That means there are now office suite, chat, contact lists and whatever else, including an email client. This also explains why did NC 'bought' RC. Except all those parts are not integrated good.
And finally it's a PHP app with a tons of legacy code. As soon as something breaks you are drowning in multiple screen heights of errors of PHP code. And consequently all performance troubles are solved by throwing RAM and CPU at the instance.
/rant