-
Notifications
You must be signed in to change notification settings - Fork 522
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question about docker image for document server community edition #625
Comments
With the help of this article, https://blog.viking-studios.net/collabora-libreoffice-als-docker-container-in-nextcloud-auf-der-synology-diskstation-integrieren/, I was able to get the docker image running and have now access to OnlyOffice. I deleted the parameter "PRODUCT_EDITION". And I don't know why the local port parameters are not mandatory in the Docker settings of Synology. I only saw "Local Port" and thought that the port number behind this is the local port. So I left them blank and there was no error message that these fields have to be filled. |
Hello @TineUser, sorry for the late reply, unfortunately we don't have a device with Docker on Synology. We will come back when we have it. |
Hello @TineUser, you have sloved your problem? |
Hello @Diggit1, no, I haven't. I stopped trying. |
ok, if you want to try again let me know. then i try to help |
@Diggit1: Do you have OnlyOffice running on Synology? |
@TineUser yes..... it is running |
I think it would be nice for the community how you got it running with the shared folders of the Synology. And which version of DSM do you have running? |
OK, i can tell this in a few steps.
|
When setting up a docker container on a Synology system I have to fill the parameter "PRODUCT_EDITION". It is a mandatory field so I can't left it blank. Which value is needed to get the community edition? I tried "community" and "ce" but nothing happened and I'm not able to connect to OnlyOffice. Even using "ee" OnlyOffice doesn't seem to work. I can't find any documenttation for filling this field with the right value.
The text was updated successfully, but these errors were encountered: