For me at least Collabora is a heck of a lot slower and clunkier to use whereas OO seems just a lot more zippy. In terms of OO vs Collabora, OO has client/server processing whereas with Collabora its strictly server side. If you need some more information, I'd be happy to supply you with some, since overall I think it would make your guide a heck of a lot better. In addition - the part of your guide which you referenced about needing to log into the container to edit the loolwsd.xml file - you definitely don't need to do that when working with a docker-compose file. It's a heck of a lot easier to save configurations with the compose file rather than as a command line argument. Containers will automatically be pulled with the latest updates and started on system startup. I've since moved on to using docker-compose files which are a lot better and easier to work with. I believe I made those a few years ago and for all intensive purposes that setup method works, but it's not very robust. I think you may have referenced some of my posts from the Nextcloud Forums. My blog, which includes some stuff about how I use FreeNAS Ubuntu VMs running Onlyoffice, Crashplan, Mattermost, Pi-hole and some things via Docker Unbound 1.8.3 replaced with Pi-hole 5.11.4 running in a VM NGINX reverse proxy 1.16.1_11 with Certbot 0.38.0_1 replaced with NGINX Proxy Manager 2.9.18 running on Hass.io Pi Nextcloud 25.0.1 (PHP 8.0.25) with Onlyoffice (via VM) ![]() Home Assistant 0.106.6 Hass.io now running on a Raspberry Pi 4 2x120GB Crucial BX500 SSD (Mirror) for bootĨx8TB WD80E(Z/M)AZ (RAIDZ2) (1 RMA'ed after 12 months)Ģx1TB Samsung 860 EVO SSD (Mirror) running the following jails and VMs:Ĭalibre 4.7.0 and replaced with Calibre-Web 0.6.19 running in a Docker container
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |