Search Criteria
Package Details: cryptpad 2024.3.0-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/cryptpad.git (read-only, click to copy) |
---|---|
Package Base: | cryptpad |
Description: | Realtime collaborative visual editor with zero knowlege server |
Upstream URL: | https://github.com/cryptpad/cryptpad |
Keywords: | collaborative |
Licenses: | AGPL3 |
Submitter: | anonfunc |
Maintainer: | buzo |
Last Packager: | buzo |
Votes: | 10 |
Popularity: | 0.75 |
First Submitted: | 2019-06-08 16:40 (UTC) |
Last Updated: | 2024-04-16 08:25 (UTC) |
Dependencies (6)
- nodejs (nodejs-gitAUR, nodejs-lts-fermiumAUR, nodejs-sharedAUR, nodejs-lts-hydrogen, nodejs-lts-iron)
- git (git-gitAUR) (make)
- npm (corepackerAUR) (make)
- certbot (certbot-gitAUR) (optional) – Let’s Encrypt – automatically receive and install X.509 certificates to enable TLS
- certbot-nginx (certbot-nginx-gitAUR) (optional) – Nginx plugin for Let’s Encrypt client
- nginx (nginx-nchan-gitAUR, nginx-nchanAUR, nginx-rtmp-sergey-gitAUR, nginx-mainline-boringsslAUR, nginx-quic-openssl-hgAUR, nginx-mainline-pushstreamAUR, tengineAUR, tengine-extraAUR, freenginx-mainline-hgAUR, angieAUR, nginx-quic-libresslAUR, freenginx-mainlineAUR, nginx-mainline) (optional) – HTTP server providing TLS
Latest Comments
« First ‹ Previous 1 2 3 Next › Last »
qawsedrftgzh commented on 2021-05-13 15:56 (UTC)
Uhmm... I'm quite unfamiliar with webapps, but i think I really need to try this out, because this is a thing i have long searched for (good self hosted, online office). But when I have intalled the package, how do I run it. I am a noob, btw.
buzo commented on 2021-04-05 19:26 (UTC)
Many thanks for your detailed explanation and patch, ChrisTX! (I noticed it a bit late though.)
I have just applied your patch as-is and will test myself later when I have the time.
ChrisTX commented on 2021-04-05 03:59 (UTC) (edited on 2021-04-05 04:00 (UTC) by ChrisTX)
Thanks a lot for the hard work, buzo. I've tried your latest build, and noticed the following issues now:
node_modules
folder isn't populated as intended, so it doesn't start up once again. This is because--prefix
only really works with-g
, see the npm docs here. To explain, with--prefix
or-g
and a local path (and just executing it without any further parameter is like executing it with path./
), npm creates a symlink to a global directory with the binaries populated (cryptpad has none set). The model of installing as we want it to work only works if you usenpm install -g
against a.tgz
created bynpm pack
. It's possible to use the tar file that way, but the resulting directory structure is a gigantic mess and it's only really reasonable for applications that have a populated binary array. I believe having the build step and then copying over the needed files is less messy than trying to do that since cryptpad is not designed for that installation model..service
file needs updating to the new (correct) path in/webapps
(thanks by the way, I on the other hand was not aware of the Web App packaging guidelines! :D ) It also lacks any sort of hardening.$pkgdir/var/lib/$pkgname"/{blob,block,data{,store},logs}
folders differ from the package towards the tmpfiles.d values, 755 vs 750, so it complains upon installation. I'm not sure if it's "cleaner" to use tmpfiles to create the files, or this way, but relying on tmpfiles makes namcap complain, so it's probably fine.In total, the patch below is what I've come up with, including hardening. I'm also running an instance of cryptpad myself with this package, and I can confirm with those it works fine using a minimally adjusted nginx configuration. As an added extra, it would be conceivable correcting the path to cryptpad in the example file installed as documentation (this line here).
buzo commented on 2021-04-04 17:33 (UTC)
Thanks ChrisTX, I wasn't aware of the Node.js packaging guidelines. I hope it works better now.
ChrisTX commented on 2021-03-27 23:45 (UTC)
Sorry, I was really busy and couldn't do anything.
The build process wasn't really that weird, it was inspired by the Node.js packaging guidelines but this isn't quite right in this case. You should use the production dependencies, and the node cache folder is important so it doesn't pollute the
.npm
folder of the build user, as described in the guidelines. In the same way, thefind ...
line and--user root
commands are explained there and why they're needed.Furthermore, the package still makes
/usr
writeable for the Cryptpad data, which is obviously not wanted. I've updated my previous patch to match the latest version:buzo commented on 2021-03-27 18:17 (UTC)
Okay, it should be fixed now. The build process was a bit weird before.
buzo commented on 2021-03-15 13:20 (UTC)
ChrisTX: Please go ahead and fix this package. I don't have enough time currently.
ChrisTX commented on 2021-03-13 23:51 (UTC) (edited on 2021-03-13 23:56 (UTC) by ChrisTX)
No, the
node_modules
folder is critical, that's where the dependencies go into. Without the folder, the app cannot run.Cryptpad doesn't support global installation seemingly, and that's what's breaking. The PKGBUILD is inconsistent in how it wants to do this, that's what caused the error.
Furthermore, don't use
tmpfiles
to change permissions in/usr
! It's not necessary, all that's missing are symlinks to/var/lib/cryptpad/...
folders and these are writable and have correct permission. Don't make/usr/share/cryptpad
actually writable and the data storage location for the pads. It should also not be world-readable.The following should fix the package, although people who already installed the last version will need to fix permissions in
/usr/share/cryptpad
now.buzo commented on 2021-03-13 10:37 (UTC)
spychodelics: I have removed node_modules, but I don't have time to test it now. Hope it still works …
satcom886: done (finally :)
spychodelics commented on 2021-03-09 15:07 (UTC) (edited on 2021-03-09 15:35 (UTC) by spychodelics)
4.1.0 fails with
removing node_modules fixes building process but breakes the functionality
« First ‹ Previous 1 2 3 Next › Last »