how to update etherpad-lite properly? - node.js

I keep totally failing to update an etherpad-lite server. The problem: Even a Google search for the update procedure brings up hardly any information, only that one should run "git pull origin".
I have now tried this in many different ways. The update usually works, but afterwards one of these errors occurs:
Plugins can no longer be installed
The service can no longer be started (TypeError: log4js.replaceConsole is not a function)
The entire admin panel no longer works.
I tried uninstalling or updating all plug-ins before, but both hardly brought any improvements, only other errors. The update of the plugins in the admin console fails, I tried it via the updatePlugins.sh script. Here a message appears that at least etherpad-lite 1.8,6 must be installed. I am currently at version 1.8.4 and would like to update to the latest version 1.8.12. However, some of the plug-ins are still updated. A very strange behaviour.
I would be happy if someone could tell me how to properly update the etherpad-lite instance step by step. (ubuntu 20)
Thank you!

I have recently updated Etherpad-lite from version 1.8.6 to 1.8.13.
For me, executing git pull origin and then checking out the 1.8.13 release tag, with git checkout 1.8.13, made the work.
It is important, despite having Etherpad configured as a service, to run it for the first time using:
src/bin/run.sh.
Node v12.22.1
npm 6.14.12
Ubuntu 20.04.2
I hope it has been useful to you.

Related

Security issues installing nodejs

I used different versions of nodejs for years and never had the problems, but now I got one. So I had to uninstall some nodejs version and then I've tried to install the latest stable one and after that, out of sudden I got:
the rights to the nodejs folder are assigned to SYSTEM (not sure whether previously it was the same, but previously I had no problems deleting the folder, uninstalling it, etc. Now I do! I have to change the permissions before deleting it although I am logged as a user who has admin rights)
most weird thing: if I type npm or ng I get error message: access denied! Even if I run cmd as admin! Never had such the problem before! I googled, the only thing I found suggested to kill nodejs process...well, there is no nodejs process running, at least Task Scheduler does not show it.
Please advise.

Squarespace local development server install gets hung up in middle of installation

I have spent hours trying to fix this problem on my own but am getting nowhere and can't seem to see any other questions/solutions regarding my specific problem.
I successfully installed nodist via chocalatey via Powershell admin.
I used the following script in attempting to install the Squarespace development server per Squarespace documentation:
npm install -g #squarespace/server -y
Please noted I added the -y parameter to for yes to accept license agreement but previously didn't add this parameter but still received same result.
When trying to install the local Squarespace development server via Powershell admin, the script keeps getting hung up at the following:
Using this software requires accepting the Squarespace Developer Terms
of Use and Oracle Binary Code License Agreement . See LICENSE.txt.
The following is a screenshot of all the scripts that ran beginning from my install script:
I have done everything from reinstalling nodist several times to rebooting machine and everything else to troubleshoot.
Please note that I have also waited for more than an hour to see if the script fully executes but remains hung at the above noted line.
Why is this happening and how can I fix this?
Regards.

Node isn't recognized

Referring to the above picture, can someone please tell my why my NPM script would continually fail saying that node is not recognized.
nodejs is clearly in my $PATH and it correctly identifies where it is on my computer outside of an npm script.
I am using Git Bash inside ConEMU on Windows Version 10.0.17134 Build 17134.
I wouldn't be surprised if the issue is with Windows, as the problem seems to have popped up since the latest OS update, installed just over a week ago (I've been having this issue for around that same amount of time)
I have finally got it working! It is, unsurprisingly, a Windows issue.. Because I had a few entries in my $PATH, and the nodejs one was at the end, Windows would silently fail when reading the entire path, and not get as far as the nodejs entry. The fix was to move the nodejs in the Environment Variables control panel to the very top

Error while running gnome-music using jhbuild

I'm using jhbuild to build and run gnome-music.
I'm having a successful build but when I run the command
jhbuild run gnome-music
I get the following error
One of the errors is
1.GstTag was imported without specifying a version first
The rest are in the link above.
I'm not sure how to proceed further,can someone help me out?(I'm using Ubuntu 17.04).
I'm following the steps given on:
https://github.com/GNOME/gnome-music
Gst just warns you against not mentioning a version number. Hence, that's not the error.
The error you are facing is regarding Tracker. As you are on Ubuntu distribution, you should know that Ubuntu disables Tracker by default. Hence jhbuild run gnome-music refuses to start. Tracker is a file-indexing service based on file's metadata.
However, Ubuntu is deciding to enable Tracker by default as many GNOME's core apps relies on it. Read here.
Enable Tracker and jhbuild will pick it up from the host system.

CouchDB install multiple versions side-by-side

I attempt to install multiple versions of CouchDB databases, say 1.1.0 along side with 0.10.0.
By using build-couchdb I was able to get the latest version up and running with no problems, now I am trying with installing a second version (0.10.0) but with no success so far. Following with the instructions, I've tried:
rake git="git://git.apache.org/couchdb.git tags/0.10.0" install=/full/path/to/couchdb/dir
It does a bunch of installs but fails at the end with "rake aborted!".
Have anyone successfully done this ?
Build CouchDB can be slightly brittle. In production, what I've seen is a lot of complete wipes and complete rebuilds. Since people tend to build only once, the build time is not a huge pain-point.
Next, try to use the Erlang shortcut for installing side-by-side CouchDB builds. (Search for couchdb_build in the README).
rake git="git://git.apache.org/couchdb.git tags/0.10.0" \
install=/full/path/to/couch/dependencies \
couchdb_build=/full/path/to/couch/0.10.0
rake git="git://git.apache.org/couchdb.git tags/1.1.0" \
install=/full/path/to/couch/dependencies \
couchdb_build=/full/path/to/couch/1.1.0
With the install locations identical, Build CouchDB should skip the entire process to build and install dependencies when it builds 1.1.0. This includes:
Erlang
OTP
Javascript
I believe this technique is used more often than the simpler one for side-by-side builds. Therefore it is possible this workaround will fix your error.
If you still have issues, it is probably a bug. Would you please submit a Build CouchDB issue indicating your operating system version and also attach your rake.log file?

Resources