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

Seafile and onlyoffice integration in kubernetes #2155

Open
frederic-loui opened this Issue Jan 8, 2019 · 0 comments

Comments

Projects
None yet
1 participant
@frederic-loui
Copy link

frederic-loui commented Jan 8, 2019

Hi,

We are currently evaluating Seafile in the following environment:
1- We are using kubernetes environment
2- We are running an ingress that is a reverse-proxy for K8s micro service.
Ingress is a TLS termination. So onlyoffice and seafile are in the cluster using plain 80 http port.
(no encryption)
3- We have a working ONLYOFFICE document server accessible via the private URL:
https://onlyoffice.my.domain.com from client outside the cluster
http://onlyoffice-documentserver from pod internal to the K8s cluster (call it onlyoffice internal URL)
4- We have a working SEAFILE server accessible via the private URL:
https://seafile.my.domain.com from the client outside the cluster
http://seafile from pod internal to the K8s cluster (call it seafile internal URL)
5- seafile has been hooked to our internal LDAP server using TLS (ldaps) and it is working well.

Everything is working well except that we can't edit docx/doc/xls using onlyoffice.
we have edited seahub_settings.py and added:

# Enable Only Office
ENABLE_ONLYOFFICE = True
VERIFY_ONLYOFFICE_CERTIFICATE = False
ONLYOFFICE_APIJS_URL = 'https://onlyoffice.my.domain.com/web-apps/apps/api/documents/api.js'
ONLYOFFICE_FILE_EXTENSION = ('doc', 'docx', 'ppt', 'pptx', 'xls', 'xlsx', 'odt', 'fodt', 'odp', 'fodp', 'ods', 'fods')
ONLYOFFICE_EDIT_FILE_EXTENSION = ('docx', 'pptx', 'xlsx')

caveats: for simplicity DNS has not been updated. We piut information on /etc/hosts file. So the question is how integration is working ? How do I make use of internal K8s URL in the config ?

The onlyoffice document server is accessible via https://onlyoffice.my.domain.com/welcome
(Side note: this document server already serve a nextcloud instance and is working properly)

Thanks for your help !

@frederic-loui frederic-loui changed the title Onlyoffice integration in kubernetes Seafile and onlyoffice integration in kubernetes Jan 8, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment