-
-
Notifications
You must be signed in to change notification settings - Fork 787
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
fresh installed ubuntu 20.10 has numerous gotchas #222
Comments
Without doing this much, you can just download the app image from https://github.com/baryon/medis #235 |
Thanks @ssi-anik AppImage is also working fine with Ubuntu 22.04 after installing fuse |
Hello 👋 Our development focus has now shifted to the next generation of Medis: Medis 2. Compared to its predecessor, Medis 2 offers enhanced performance, more powerful features, and a more delightful interface. If you encounter any problems with Medis 2, feel free to reopen this issue, and together, we can explore possible solutions. Download Medis 2 for free: https://getmedis.com/. Thanks for using and supporting Medis 1! |
my OS got nuked, so I'm having to go through this again, but on a very clean install, so might be helpful to others/maintainer(s):
Pop_OS 20.10 (ubuntu 20.10 variant)
clone
npm install
get errors
npm install
no errors?
npm install again
errors again?
weird...
npm run pack
webpack not installed
sigh
check here
npm run build?
webpack not installed...
check errors, first one is:
"[email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies."
Looks like I need to downgrade node for this to work. :/
nvm install 14
node -v
-> 14.16.0
npm install
much better this time, but hit error. First error I see:
gyp verb check python checking for Python executable "python2" in the PATH
I only have python3, guess I need to go get python2
sudo apt install python2
npm install
seems to work this time
npm run pack
hmm... no error, but seems to hang. last lines I see:
I run it again, but then I notice this seems to start a local server that shows a tree of its packages or something, so... probably when it 'hangs' I can just kill and move on...?
indeed,
npm start
now works.
cool. Anyways, just sharing. Hope it helps others.
The text was updated successfully, but these errors were encountered: