-
Notifications
You must be signed in to change notification settings - Fork 269
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
deploy.sh script fails in fresh install of Ubuntu Server 20.04.1 #1564
Comments
I am having this same issue when trying to deploy LL from the script to Ubuntu 20.04.01. Would be interested in what the fix would be. |
On ubuntu 20.x node js is recoginzed by |
Once you get past this, there is also a problem compiling grpc:
|
did you resolve this? |
nope. We abandoned this project completely. As far as I can tell, this project is unmaintained. |
I am sorry. Anyway, thank you 😅 |
@fMoro1999 I agree with the rest of the comments that this repo is an abandoned dumpster fire of code, but here's a Dockerfile snippet with which I managed to build v6.4.0 of LearningLocker as cleanly as possible. It follows the current state of the deploy script to base everything off of Node v10, which of course is EOL in just a few weeks. I seems like they only maintain their enterprise edition now; you can see from the deploy script and elsewhere that their internal code is probably on Node v12 and updated dependencies, and with extra fixes, too. The build should be easily translatable to Focal; essentially, you need to undo the -Werror flag for the C++ compiler that gyp is using; the set of warnings which might get emitted depends on the compiler version. The Dockerfile below is for a Debian Buster node v10 image, which has g++ v8. So, the trick here is all in the CXXFLAGS... FROM node:10.24.0-buster AS NodeBuildEnv
ARG RELEASE=https://github.com/LearningLocker/learninglocker/archive/refs/tags/v6.4.0.tar.gz
ARG RELEASESHA256=ac1b86b57a69d1c8cbfad896e2d3387537287f88367b49dcf7ba1879a5a69cc5
SHELL [ "/bin/bash", "-c" ]
WORKDIR /usr/src
RUN chown node:node -R /usr/src
USER node
RUN curl -L -o /tmp/source.tar.gz "${RELEASE}" && \
<<<"${RELEASESHA256} /tmp/source.tar.gz" sha256sum -c && \
tar --strip-components=1 -xvf /tmp/source.tar.gz && \
env \
CXXFLAGS="-Wno-error=cast-function-type -Wno-error=ignored-qualifiers -Wno-error=stringop-truncation" \
npm_config_build_from_source="true" \
yarn --ignore-engines --frozen-lockfile install && \
touch .env && \
yarn build-all && \
yarn cache clean |
@yetanotherbug thank you! For now I just installed Ubuntu 18.04 and I confirm that the script worked fine. Anyway, I will give it a try 😉 |
Hello everyone 😉😉😉😉😉 !!! it is running successfully now !!! here is or story : then we got many issue but when we switched back to the Ubuntu 16 at the end got mongo DB problem which solved by changing the .env file 👍 usr/local/learninglocker/current/xapi$ vi .env from now it works every thing !!! |
What version were you using?
Open Source
What steps can we follow to reproduce the behaviour?
wget -qO deployll.sh https://raw.githubusercontent.com/LearningLocker/deploy/master/deployll.sh && bash deployll.sh
What is the actual behaviour?
Script fails since it cannot find nodejs executable
What is the expected behavior?
Installation continues since nodejs is installed correctly.
Is there any additional information that will help us replicate/understand the problem?
Culprit is the deployll.sh script, please see from line 740:
First if-statement assumes nodejs executable to be named nodejs - latest installed version v10.23.0 has only executable node.
The text was updated successfully, but these errors were encountered: