Install from source fail at yarn setup

Hi,

I’m trying to install ghost from source using this link: https://ghost.org/docs/install/source/

It works fine until the yarn setup which failed with this error:
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! ghost-admin@2.31.0 build: ember build
npm ERR! Exit status 1
npm ERR! Failed at the ghost-admin@2.31.0 build script.
Warning: Command failed: npm run build
ENOENT: no such file or directory, open ‘symbols-loader.html’
Warning: Failed running “grunt shell:ember:dev” in “core/client”. Use --force to continue.

Thanks for your help.

Hi @phantoms08! Can I ask what you’re intending on doing? Are you wanting to contribute to Ghost or customise Ghost to your needs?

Hi @DavidDarnes. Thanks for your answer. I’d like to customise Ghost.

To what degree? I’m wondering whether it’s possible to achieve what you want without having to delve deep into the Ghost codebase :slightly_smiling_face:

I’d like to change some colors in the admin UI, and change Posts page in the admin UI too.

Ah I see, interesting. Is this a personal preference? If so then you could use a browser extension to add user styles specifically for when you’re using the Ghost admin. There’s a related thread about doing just that:

I could use that for the colors. As for the changes on Posts page, there are a little more tricky (I guess). I’d like to change the length of each post snippet and show each post image.

I might also make further changes in the future, so installing from source would be the best way.

Thanks.

In that case can I ask if you’ve got everything setup as shown in the Prerequisites section? Looking at the errors you’re getting it appears you might not have npm / node setup right https://ghost.org/docs/install/source/#prerequisites

I have node js v10.16.0 (installed via nvm-windows) and yarn on windows 10.
I’ve tried on an ubuntu 18.04 server and I get the same errror.

So, I went back and tried again to have a better look at the error. And it was coming from ember-svg-jar.
A good sir solved my problem with his github issue here.

Thanks for your help, @DavidDarnes.

1 Like

Great job! Glad you solved it