generated from coop-cloud/example
Remove nginx from recipe #17
Open
stevensting
wants to merge 1 commits from
remove-nginx into main
pull from: remove-nginx
merge into: :main
:main
:remove-nginx
:25.04.8.1.1
:add-timeout
Dismiss Review
Are you sure you want to dismiss this review?
Labels
No items
No labels
Milestone
No items
No Milestone
Assignees
3wordchant
aadil (Aadil Ayub)
abra-bot (Abra Bot)
ammaratef45
amras (Sarma)
Apfelwurm
appletalk
arjan
basebuilder
BornDeleuze (Born Deleuze)
Brooke
carla
cas (Cassowary)
codegod100
coopcloud
cyrnel
dannygroenewegen (Danny Groenewegen)
decentral1se (d1)
dede
devydave
fauno (fauno)
flancian
Frando
hex (Josh Dukes)
iexos
jade (Jade Ambrose)
javielico (Javielico)
jjsfunhouse
jmakdah2 (Jackie Makdah)
joe-irving (Joe Irving)
kawaiipunk (KawaiiPunk)
knoflook
kolaente
lambdabundesverband
linnealovespie (April)
marlon (marlon)
mayel
mirsal
moosemower
moritz
nicksellen (Nick Sellen)
notplants
oxaliq (sorrel)
p4u1 (p4u1)
pau
pharaohgraphy (Andrew 🐦🔥❤️🔥✴️)
PhiNatalie
renovate-bot (Comrade Renovate Bot)
ripclap
rix
rscmbbng
sef (sef)
simon
sixsmith (Sixsmith)
stevensting (stevensting)
tobias
trav (Trav Fryer)
val (val (he/him))
vaznasty
virtualboys
wolcen (Chris Thompson)
wykwit
xynosis
yksflip
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/collabora#17
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
abra.shIn my tests I had the feeling that this made collabora somewhat faster that with nginx.
@@ -57,4 +0,0 @@# Admin Console websocketlocation ^~ /cool/adminws {Do you know if there are any security considerations, by removing nginx?
@decentral1se you originally added nginx. Do you have an opinion here?
Can't remember why I even did this, proceed! Thanks for the maintenance work 🙏
from my point of view this should be fine, as collabora is intended to be run directly behind a reverse-proxy.
Maybe we could disable the admin console endpoint with the coolwsd directly or at least make it configureable with a disabled default. What do you think @moritz ?
I think it's an good idea to make the admin console configurable with a disabled default. But I'm not sure, what the other endpoints and proxy header options in the nginx configuration are doing exactly, and what would be the consequences without them.
Form my point of view all endpoints are non-critical and they should remain open for collabora to work.
^~ /browserstatic files like css^~ /hosting/discoveryWOPI discovery^~ /hosting/capabilitiesinfo about the server~ ^/cool/(.*)/ws$main WOPI endpoint for document editing~ ^/(c|l)ooldownloads etcThe config made ngnix drops everything but the defined endpoints. If we wanted to, we could do it the same for the traefik config, but I would assume that isn't really necessary as collabora is designed to run public facing.
All other config params are already handled by traefik in default config, so no need to add anything.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.