exu/wiki-grav
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Notes on Onlyoffice

Browse Source 
Requires CSP and how I set it
    Podman command for Onlyoffice just sets the token
    Multiple links on Installation, integration and proxy configuration linked
This commit is contained in:
RealStickman 2023-05-12 18:26:08 +02:00
parent ecdc2de7e8
commit 32898d0bf3
1 changed files with 13 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
pages/02.linux/nextcloud/default.en.md
View File

@ -278,11 +278,19 @@ server {
## Onlyoffice Container ## Onlyoffice Container
> Unfinished Integrating onlyoffice, requires setting the correct Content Security Policy headers on the webserver. Using CSP also introduces blockages in Nextcloud that have to be fixed. The console view is your friend for finding every issue.
For my installation, the headers needed to be set like this.
```
Content-Security-Policy "default-src 'self' 'unsafe-inline' 'unsafe-eval' data: onlyoffice.exu.li;"
```
```sh ```sh
podman run -it -d --name onlyoffice -p 9480:80 \ sudo podman run -itd --name onlyoffice -p 8080:80 \
--restart always \ -e JWT_SECRET={secret key} \
--label "io.containers.autoupdate=image" \ docker.io/onlyoffice/documentserver
docker.io/onlyoffice/documentserver:latest
``` ```
> [Installing ONLYOFFICE Docs Community Edition for Docker on a local server](https://helpcenter.onlyoffice.com/installation/docs-community-install-docker.aspx)
> [About the ONLYOFFICE and Nextcloud integration](https://helpcenter.onlyoffice.com/integration/gettingstarted-nextcloud.aspx)
> [Using ONLYOFFICE Docs behind the proxy](https://helpcenter.onlyoffice.com/installation/docs-community-proxy.aspx)