Skip to content
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

ocis full deployment example WOPISERVER_DOMAIN(s) #9810

Closed
mmattel opened this issue Aug 14, 2024 · 2 comments
Closed

ocis full deployment example WOPISERVER_DOMAIN(s) #9810

mmattel opened this issue Aug 14, 2024 · 2 comments

Comments

@mmattel
Copy link
Contributor

mmattel commented Aug 14, 2024

In the deployment example valid for v5, we only have one WOPISERVER_DOMAIN valid for both office products which are onlyoffice and collabora.

With v6 (rolling) we now have:

  • WOPISERVER_DOMAIN which is valid for collabora only, see the collabora.yml file
  • WOPISERVER_ONLYOFFICE_DOMAIN which is valid for onlyoffice only, see the onlyoffice.yml file.

Q1: is there a particular reason splitting that up?
Q2: what is planned when integrating office 365? (see PR: #9686) will there be an additional envvar in .env?

The background of the question is, that we have deployment examples in the admin docs where we need do document if wopiserver domains need to be considered in the setup when using valid certificates with letsencrypt.

@micbar
@tbsbdr fyi

@micbar
Copy link
Contributor

micbar commented Aug 14, 2024

Please wait after my vacation

@micbar
Copy link
Contributor

micbar commented Dec 13, 2024

Simple explanation: The collaboration service needs a wopiserver domain for every single web office.

@micbar micbar closed this as completed Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants