D
D
Denis2013-11-24 13:33:24
Node.js
Denis, 2013-11-24 13:33:24

Ghost on Raspberry Pi

Did everything according to this manual.
After sudo npm install --production
I get:

[sqlite3]: Checking for http://node-sqlite3.s3.amazonaws.com/Release/node_sqlite3-v2.1.a-node-v11-linux-arm.tar.gz
[sqlite3]: http://node-sqlite3.s3.amazonaws.com/Release/node_sqlite3-v2.1.a-node-v11-linux-arm.tar.gz not found, falling back to source compile (Error: Server returned 404)
Build failed
[sqlite3]: 1
npm ERR! [email protected] install: `node build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the sqlite3 package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node build.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls sqlite3
npm ERR! There is likely additional logging output above.

npm ERR! System Linux 3.6.11+
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "install" "--production" "--sqlite=/usr/local"
npm ERR! cwd /var/www/ghost
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.14
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /var/www/ghost/npm-debug.log
npm ERR! not ok code 0

I posted the log: https://dl.dropboxusercontent.com/u/19919278/npm-debug.log
As I understand it, all because the link does not work: http://node-sqlite3.s3.amazonaws.com/Release /node_sqlite3-v2.1.a-node-v11-linux-arm.tar.gz
Is there any way to fix the situation? I understand that you need to find this package, and compile it yourself. or somewhere to change the link and it will pick up another working link during installation.
How to fix everything?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
O
ofstudio, 2015-01-20
@WolFman

A little personal experience, because it was a very specific case. The current version of Ghost (0.5.8) is up and running on the Raspberry Pi without any problems.
But happiness continues exactly until the first re-login - after entering the login-password, Ghost will gobble up 100% of the CPU and the connection will timeout (a red blurr with a server error will pop up in the browser in the login form).
The reason is in the package bcrypyjs, which is unrealistically slow on the ARM architecture. The good news is that there is a similar package for node that is written in C and is fast. It's called simply bcrypt.
1. In the directory with Ghost npm install bcrypt --save
2. In the core/server/models/user.js file, change the top
to
3. Restart Ghost. Viola :-)

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question