-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Still no up and running instance with new setup #4884
Comments
It seems that failed to install |
Awesome fast response -thx a lot. But still no luck (or did I miss or spoil something?):
|
I think you are using wrong user to execute command. first comment:
this is seems to second comment:
this is seems to my suggest: remove node_modules, and re-install npm packages (to fix some permission error).
|
I also ran into a lot of problems in the step |
Please run On my machine, it often occurs the similar problem. |
|
Maybe, when run |
Yes we can...?
Apparently one step in the right direction,and thank you for that. But still not there. 1. npm rebuild jpegtran-bin
2. node-gyp configure
3. NODE_ENV=production npm run build
Will this get up and running, and what is still missing?
|
The above sentence was wrong, I'm so sorry! But |
Does this break, because
|
you need to install GNU C++ compiler. |
Thank you. Hope your tip will end this "adventure". There are really many dependencies in this project, but I'll give it a (last) shot. Still I have no clue about this c++/gcc package. Is it a Linux or Node package? Any link to some advice would be much appreciated. |
g++ can get from your using linux distributions.
Tip: If you dont like this many dependencies, you can choose run on docker. |
For Ubuntu / Debian |
Not exactly a walk in the park to get Misskey up and running on Ubuntu 18.04 LTS with PostgreSQL. But at last it took off - thanks to all the guys and girls, who have offered support along the way in this thread. Now, I look forward to investigate and test the thing in action. And hopefully a danish Misskey-instance pops up soon. The instance runs like a charm on an internal IP-number. However I bumped into the following two errors just before take off. 1. A message on vulnerabilities during
|
npm says "found X vulnerabilities"some old npm packages, may have vulnerabilities. error
|
No, all of the Misskey instance owners have to fix these vulnerabilities manually (because some polluted packages used not only on building but also on hosting). |
My attempts to install and test a server instance of Misskey on my Ubuntu 18.04 LTS have all gone bad so far.
First attempt with Misskey 10.98.3, Node 10 LTS and MongoDB
https://github.com/syuilo/misskey/pull/3906
https://github.com/syuilo/misskey/issues/3921
Second attempt with Misskey 11.11.3, Node 11.13 and PostgreSQL and an swapfile increase from 2 GB to 4 GB
Have also done this:
Still no luck. Do I need to use crypto API and/or yarn?
Any input would be much appreciated.
My error-log for the brave
The text was updated successfully, but these errors were encountered: