Package Details: etherpad-lite 1:1.8.18-1

Git Clone URL: https://aur.archlinux.org/etherpad-lite.git (read-only, click to copy)
Package Base: etherpad-lite
Description: Lightweight fork of etherpad based on javascript
Upstream URL: https://etherpad.org
Licenses: Apache
Conflicts: etherpad-lite-git
Submitter: onny
Maintainer: None
Last Packager: dvzrv
Votes: 29
Popularity: 0.059072
First Submitted: 2013-03-15 15:10 (UTC)
Last Updated: 2022-05-12 19:28 (UTC)

Dependencies (11)

Required by (0)

Sources (4)

Pinned Comments

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 16 Next › Last »

dvzrv commented on 2019-02-10 17:17 (UTC)

The upgrade to 1.7.5 brought a lot of security fixes. Please upgrade! The custom directory in /etc/etherpad-lite was replaced by no-skin, introducing a new skin system. The credentials.json file was added and can be used to setup credentials as well.

RubenKelevra commented on 2018-10-11 19:09 (UTC)

@dvzrv thanks a lot for giving my old package new love! :)

dvzrv commented on 2018-06-18 22:50 (UTC)

@immae: Honestly, I would refrain from ever running npm as root.

That being said, I think, that the cleanest way would probably be to define a separate folder for the "user installed" packages, to not pollute the static set of packaged node packages, that come with the application. This directory for the user installed packages would need to be writable by the user running etherpad-lite (this should also never be root), ideally somewhere under /var/lib/etherpad-lite. Sadly, this has not yet been implemented upstream (which is barely keeping up with updating the security hole infested plugins, etherpad-lite is built from).

immae commented on 2018-06-18 06:57 (UTC)

I’ll answer my own question, maybe it can help other people with the same problem. So actually, etherpad tries to initialize each module, creating a .ep_initialized in each of them. This call hangs forever, thus making the whole thing hang too (for reference: src/static/js/pluginfw/plugins.js method callInit).

It turns out that most modules don’t have an initialization hook (I have 20 and none of them has it), so just touch-ing the .ep_initialized file of each module will unlock the process.

This permits at least to load a bunch of modules installed manually. It doesn’t solve every case, but it may help.

immae commented on 2018-06-18 05:40 (UTC)

Hello @dvzrv, Thanks for your packaging. The idea of making the /usr/share folder static is nice. However I tried to install plugins manually, doing npm install as root from the /usr/share/etherpad-lite, but the start of etherpad then stales waiting for something forever (and never listening).

Did you manage to do this kind of manual installation? You seem to suggest so in the github issue, but maybe I missed something. Modules installation seem to say it should work to just run this npm install (e.g. https://www.npmjs.com/package/ep_infopanel )

dvzrv commented on 2018-04-12 17:24 (UTC)

@schimicata: my bad, forgot to run updpkgsums. It's now fixed.

schimicata commented on 2018-04-12 11:10 (UTC) (edited on 2018-04-12 11:12 (UTC) by schimicata)

upgrave from v1.6.3 to v1.6.5 fails with:

==> Validating source files with sha512sums...

etherpad-lite-1.6.5.tar.gz ... Passed
jquery-1.9.1.js ... Passed
etherpad-lite-sysusers.conf ... Passed
etherpad-lite-tmpfiles.conf ... Passed
etherpad-lite.service ... FAILED

==> ERROR: One or more files did not pass the validity check!

:: failed to verify etherpad-lite integrity

dvzrv commented on 2018-03-13 11:20 (UTC)

@GFdevelop why do you flag this out-of-date? There is no new release!

If there are problems with etherpad-lite, report them upstream. This is not a development platform!

dvzrv commented on 2018-02-03 16:26 (UTC) (edited on 2018-02-03 16:27 (UTC) by dvzrv)

Upgraded to 1.6.3.

The move of {APIKEY,SESSIONKEY}.txt to /etc/etherpad-lite was not very straight forward though. Currently it is not possible to put these files in the backup array, as they would have to be created for that first. Using an empty file for them doesn't work though [1].

Adding them to the backup array without being created leads to them being renamed to a .pacsave file every time.

So, there's no real benefit of them being in /etc/etherpad-lite for the time being (apart from a more strict folder permission).

Additionally, I've unset the specific $HOME directory for the etherpad-lite user (via sysusers.d).

[1] https://github.com/ether/etherpad-lite/issues/3317