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

Update instructions for Onlyoffice

Browse Source
This commit is contained in:
exu 2023-11-24 10:25:48 +01:00
parent bab35787da
commit ec03c1d4c3
1 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -5,6 +5,8 @@ visible: true
[toc]
Last modified: 2023-11-24
## Installation
Nextcloud will be using apache
@ -376,6 +378,11 @@ server {
## Onlyoffice Container
> This procedure is incomplete. See these links for the additional configurations necessary.
> [jiriks74 Docker-DocumentServer](https://gitea.stefka.eu/jiriks74/Docker-DocumentServer#setting-up-secret-key-with-nextcloud)
> [Onlyoffice-Nextcloud issue 601](https://github.com/ONLYOFFICE/onlyoffice-nextcloud/issues/601#issuecomment-1089929204)
> [Onlyoffice-Nextcloud issue 153](https://github.com/ONLYOFFICE/onlyoffice-nextcloud/issues/153#issuecomment-544900501)
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.
@ -387,7 +394,9 @@ Content-Security-Policy "default-src 'self' 'unsafe-inline' 'unsafe-eval' data:
```sh
podman run -itd --name onlyoffice -p 8080:80 \
-e JWT_SECRET=[SECRET KEY] \
-e JWT_ENABLED="true" \
-e JWT_SECRET="[SECRET KEY]" \
-e JWT_HEADER="AuthorizationJwt" \
docker.io/onlyoffice/documentserver
```