Onlyoffice vs Collabora in Nextcloud
-
@scottalanmiller said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
Last time I looked at them, the Collabora open source version needed compiled.
It's never needed that as long as I've known about it. It's a Docker instance, which is the real pain of it.
Hrm, I'll have to take another look. Docker would make it somewhat easier.
-
I have never used Docker. I'd have to figure that out first.
This https://helpcenter.onlyoffice.com/server/linux/document/linux-installation-centos.aspx?_ga=2.255928712.2049076129.1559669474-423780045.1559669474 makes no mention of Docker but I'm assuming it is NOT the community edition. -
@brandon220 said in Onlyoffice vs Collabora in Nextcloud:
I have never used Docker. I'd have to figure that out first.
This https://helpcenter.onlyoffice.com/server/linux/document/linux-installation-centos.aspx?_ga=2.255928712.2049076129.1559669474-423780045.1559669474 makes no mention of Docker but I'm assuming it is NOT the community edition.Yeah, not only do you have to figure out the basics (easy), but you have to figure out how to modify it to work unless you have no proxy in front of your NextCloud setup (unlikely.) The default Docker setup doesn't work for a production style expected install. So you have to go into the Docker instance and manage it like a traditional container, breaking what is sold as the purpose of using something like Docker. You have to manage the networking.
-
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
@scottalanmiller said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
Last time I looked at them, the Collabora open source version needed compiled.
It's never needed that as long as I've known about it. It's a Docker instance, which is the real pain of it.
Hrm, I'll have to take another look. Docker would make it somewhat easier.
No, makes it ridiculously harder.
-
https://helpcenter.onlyoffice.com/server/linux/community/linux-installation-centos.aspx?_ga=2.97092124.2049076129.1559669474-423780045.1559669474
is for the Community Version and is definitely different than the link posted above. It too makes no mention of Docker. The Docker option is there but not what I would choose. To me, Docker would just add a layer of complexity and more things to break
Yes, I have Nginx in front of all NC installs. -
@brandon220 said in Onlyoffice vs Collabora in Nextcloud:
https://helpcenter.onlyoffice.com/server/linux/community/linux-installation-centos.aspx?_ga=2.97092124.2049076129.1559669474-423780045.1559669474
is for the Community Version and is definitely different than the link posted above. It too makes no mention of Docker. The Docker option is there but not what I would choose. To me, Docker would just add a layer of complexity and more things to break
Yes, I have Nginx in front of all NC installs.
-
@scottalanmiller said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
@scottalanmiller said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
Last time I looked at them, the Collabora open source version needed compiled.
It's never needed that as long as I've known about it. It's a Docker instance, which is the real pain of it.
Hrm, I'll have to take another look. Docker would make it somewhat easier.
No, makes it ridiculously harder.
Keep in mind that the somewhat easier is in comparison to compiling from source with all the proper compiler settings. To me it is easier, I know it's still a pain in the neck!
-
@travisdh1 we can help you on GitHub https://github.com/ONLYOFFICE/onlyoffice-nextcloud/issues
there are a lot of requests concerning reverse proxy. we promised to post the official instructions
-
@brandon220 this link is about Community Server installation. Community Server contains doc management, project management, CRM, Calendar, etc
Document Server (doc editors) + Community Server (collaboration platform) = Community Edition.
If you are planning to use ONLYOFFICE editors integrated with Nextcloud, you need Document Server only.
https://helpcenter.onlyoffice.com/server/linux/document/index.aspx
-
@hellonadya I have it installed and running now. Working on connecting to NC.
-
@scottalanmiller said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
@scottalanmiller said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
Last time I looked at them, the Collabora open source version needed compiled.
It's never needed that as long as I've known about it. It's a Docker instance, which is the real pain of it.
Hrm, I'll have to take another look. Docker would make it somewhat easier.
No, makes it ridiculously harder.
The Collabora documentation is really straightforward on the container and looks very easy. What isn't "production" about the setup?
-
@stacksofplates said in Onlyoffice vs Collabora in Nextcloud:
@scottalanmiller said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
@scottalanmiller said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
Last time I looked at them, the Collabora open source version needed compiled.
It's never needed that as long as I've known about it. It's a Docker instance, which is the real pain of it.
Hrm, I'll have to take another look. Docker would make it somewhat easier.
No, makes it ridiculously harder.
The Collabora documentation is really straightforward on the container and looks very easy. What isn't "production" about the setup?
I mean I ran this
podman run -t -d --name collabora -p 9980:9980 -e "domain=test.com" -e "username=admin" -e "password=password" collabora/codeand it's up and running. Either run it on your NextCloud host and point to localhost:9980 or just point to the host the container is running on.
If you don't want to run Docker-Compose you can just use a systemd unit to start the process at boot with either straight Docker or Podman (or whatever container engine).
The advantage to Podman is it's daemonless and unprivileged nature.
-
@stacksofplates said in Onlyoffice vs Collabora in Nextcloud:
@scottalanmiller said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
@scottalanmiller said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
Last time I looked at them, the Collabora open source version needed compiled.
It's never needed that as long as I've known about it. It's a Docker instance, which is the real pain of it.
Hrm, I'll have to take another look. Docker would make it somewhat easier.
No, makes it ridiculously harder.
The Collabora documentation is really straightforward on the container and looks very easy. What isn't "production" about the setup?
With Docker, you have to be running the exact same version of OS and kernel that the devs who built the container. Docker specifically isn't portable like so many people claim.
-
@stacksofplates Nextcloud 16 is will only allow you to use https to connect to OnlyOffice. Have not tried to install Collabora yet. I guess I'll be trying that next. I have zero Docker experience.
-
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
@stacksofplates said in Onlyoffice vs Collabora in Nextcloud:
@scottalanmiller said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
@scottalanmiller said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
Last time I looked at them, the Collabora open source version needed compiled.
It's never needed that as long as I've known about it. It's a Docker instance, which is the real pain of it.
Hrm, I'll have to take another look. Docker would make it somewhat easier.
No, makes it ridiculously harder.
The Collabora documentation is really straightforward on the container and looks very easy. What isn't "production" about the setup?
With Docker, you have to be running the exact same version of OS and kernel that the devs who built the container. Docker specifically isn't portable like so many people claim.
No you don't. That's not true at all.
Yes you can create an app that uses a syscall that may be deprecated or uses a very new kernel hook that isn't available in older kernels. So you would be limited to kernels that support those, but it is in no way a requirement to have the exact same kernel and certainly not the exact same OS.
-
@stacksofplates said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
@stacksofplates said in Onlyoffice vs Collabora in Nextcloud:
@scottalanmiller said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
@scottalanmiller said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
Last time I looked at them, the Collabora open source version needed compiled.
It's never needed that as long as I've known about it. It's a Docker instance, which is the real pain of it.
Hrm, I'll have to take another look. Docker would make it somewhat easier.
No, makes it ridiculously harder.
The Collabora documentation is really straightforward on the container and looks very easy. What isn't "production" about the setup?
With Docker, you have to be running the exact same version of OS and kernel that the devs who built the container. Docker specifically isn't portable like so many people claim.
No you don't. That's not true at all.
Yes you can create an app that uses a syscall that may be deprecated or uses a very new kernel hook that isn't available in older kernels. So you would be limited to kernels that support those, but it is in no way a requirement to have the exact same kernel and certainly not the exact same OS.
Yes, that's what everyone claims, but I have very rarely had a Docker container work when deployed to a different distribution that it was created on, and sometimes even different kernel versions break things.
Yes, they are supposed to be portable, but every distribution has a slightly different compiled kernel. Because the kernel is shared, random things are just broken and/or don't work. I've seen it happen so often that I just assume anyone claiming Docker containers works with it in a monolithic environment. In which case, of course they just work.
-
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
@stacksofplates said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
@stacksofplates said in Onlyoffice vs Collabora in Nextcloud:
@scottalanmiller said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
@scottalanmiller said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
Last time I looked at them, the Collabora open source version needed compiled.
It's never needed that as long as I've known about it. It's a Docker instance, which is the real pain of it.
Hrm, I'll have to take another look. Docker would make it somewhat easier.
No, makes it ridiculously harder.
The Collabora documentation is really straightforward on the container and looks very easy. What isn't "production" about the setup?
With Docker, you have to be running the exact same version of OS and kernel that the devs who built the container. Docker specifically isn't portable like so many people claim.
No you don't. That's not true at all.
Yes you can create an app that uses a syscall that may be deprecated or uses a very new kernel hook that isn't available in older kernels. So you would be limited to kernels that support those, but it is in no way a requirement to have the exact same kernel and certainly not the exact same OS.
Yes, that's what everyone claims, but I have very rarely had a Docker container work when deployed to a different distribution that it was created on, and sometimes even different kernel versions break things.
Yes, they are supposed to be portable, but every distribution has a slightly different compiled kernel. Because the kernel is shared, random things are just broken and/or don't work. I've seen it happen so often that I just assume anyone claiming Docker containers works with it in a monolithic environment. In which case, of course they just work.
I've literally never had it happen and I use it all of the time. Build on Fedora, deploy to either RHEL/CentOS or Fedora. And pull images from Ubuntu and use those all of the time.
-
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
@stacksofplates said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
@stacksofplates said in Onlyoffice vs Collabora in Nextcloud:
@scottalanmiller said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
@scottalanmiller said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
Last time I looked at them, the Collabora open source version needed compiled.
It's never needed that as long as I've known about it. It's a Docker instance, which is the real pain of it.
Hrm, I'll have to take another look. Docker would make it somewhat easier.
No, makes it ridiculously harder.
The Collabora documentation is really straightforward on the container and looks very easy. What isn't "production" about the setup?
With Docker, you have to be running the exact same version of OS and kernel that the devs who built the container. Docker specifically isn't portable like so many people claim.
No you don't. That's not true at all.
Yes you can create an app that uses a syscall that may be deprecated or uses a very new kernel hook that isn't available in older kernels. So you would be limited to kernels that support those, but it is in no way a requirement to have the exact same kernel and certainly not the exact same OS.
Yes, that's what everyone claims, but I have very rarely had a Docker container work when deployed to a different distribution that it was created on, and sometimes even different kernel versions break things.
Yes, they are supposed to be portable, but every distribution has a slightly different compiled kernel. Because the kernel is shared, random things are just broken and/or don't work. I've seen it happen so often that I just assume anyone claiming Docker containers works with it in a monolithic environment. In which case, of course they just work.
Any examples of what broke in what apps on what distros?
-
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
Yes, that's what everyone claims, but I have very rarely had a Docker container work when deployed to a different distribution that it was created on, and sometimes even different kernel versions break things.
You are wrong. See my own guide, here in the community, to installing the Ubiquiti UNMS controller on Debian.
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
Yes, they are supposed to be portable, but every distribution has a slightly different compiled kernel. Because the kernel is shared, random things are just broken and/or don't work. I've seen it happen so often that I just assume anyone claiming Docker containers works with it in a monolithic environment. In which case, of course they just work.
Docker containers are not portable once installed. They are not designed to be moved around. Stop saying shit and give real examples.
-
@JaredBusch said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
Yes, that's what everyone claims, but I have very rarely had a Docker container work when deployed to a different distribution that it was created on, and sometimes even different kernel versions break things.
You are wrong. See my own guide, here in the community, to installing the Ubiquiti UNMS controller on Debian.
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
Yes, they are supposed to be portable, but every distribution has a slightly different compiled kernel. Because the kernel is shared, random things are just broken and/or don't work. I've seen it happen so often that I just assume anyone claiming Docker containers works with it in a monolithic environment. In which case, of course they just work.
Docker containers are not portable once installed. They are not designed to be moved around. Stop saying shit and give real examples.
Oh, if that's what he means by portable. Yeah you don't put an image on a system and move it to another. You just spin up the image on another system.
