Closed kyrofa closed 4 years ago
@kyrofa: Implemented now: https://gerrit.libreoffice.org/c/online/+/96197
With export SNAP_INSTANCE_NAME=nextcloud this now leads to:
lsof | grep 'loolwsd.*unix' | head -n 3 loolwsd 20951 kendy 16u unix 0xffff8802b1e1ec00 0t0 774945 @snap.nextcloud.loolwsd-JelzOF1i@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ type=STREAM loolwsd 20951 kendy 17u unix 0xffff88033ebc5c00 0t0 774946 @snap.nextcloud.loolwsd-JelzOF1i@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ type=STREAM loolwsd 20951 kendy 18u unix 0xffff8802b20ab800 0t0 774947 @snap.nextcloud.loolwsd-JelzOF1i@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ type=STREAM
Hope this is what you need! :-)
@kendy heey, check this out, nice work!
I've never used this before, does that look right? See any issues we need to investigate further? I get a huge log when I run it manually that doesn't mean much to me, but I'll put it here just in case:
```
# ./collabora-online-snapshot-LATEST.AppImage --appimage-extract-and-run
File exists and file size matches, skipping
In "normal" release those warn messages from core are suppressed by default. It's controlled by an environment variable.
@kyrofa: Great news, looks perfect :-) Let's close this issue then, if you find any problem please do file a new one.
Awesome, thank you both! Let me know when this is contained in an official release and we'll cut a release of our own.
Any update on when this will be contained in a release?
In "normal" release those warn messages from core are suppressed by default. It's controlled by an environment variable.
so it is okay that these messages appear? how to surpress them?
In "normal" release those warn messages from core are suppressed by default. It's controlled by an environment variable.
so it is okay that these messages appear? how to surpress them?
In current 4.2.405 release these messages are supressed by default.
Sorry to bother, I'd like to get the Collabora CODE built in server in my nextcloud snap instance. I'm running the snap version 19-2020-06-27
. I understand there's an environment variable I have to set, but where?
Thanks and sorry for the noob question.
This still doesn't work with the snap install of NC 20.0.7snap1.
Extracting the snap-specific discussion from #26. Thanks to @kendy we've made some significant progress in getting this running in the Nextcloud snap. We're not quite there yet, so I wanted to make this issue to track it.
At the moment, the issue is that an abstract unix socket is being created, but abstract sockets need to follow a specific naming pattern in snaps in order to be allowed under confinement (in our case,
@snap.nextcloud.whatever-you-want
). I see two ways to make that happen:$SNAP_INSTANCE_NAME
environment variable is defined (this is part of the snap standard, and is thus defined for all snaps) and then use@snap.$SNAP_INSTANCE_NAME.
as the socket prefix(2) makes for a more generic feature, but I doubt it would be widely-used. As a result, I'm not sure it's worth the effort to make it a generic feature, making (1) perhaps the more attractive option. Any other ideas?