Changes to Ghost support

justincox

Ghost has been running well, but over the weekend, I updated from 5.44.0 to 5.46.0 and everything broke. Working with the Ghost developer forum, it seems there are a few things amiss with the Opalstack install. I don't know if it's because I'm on a shared stack, or if it's a result of the install settings.

Essentially, the main content folder is not being respected. Files are uploaded and stored in the versions folder, which means upgrading breaks everything. I manually moved the images and files to the current versions folder, but that doesn't solve the problem longterm -- the next software update will just break all the images and links again. The development forum said there might be an issue with file permissions or the config file settings. I tried changing the config file path to the content folder, but it just seems to crash Ghost on the restart.

Any suggestions?

Here's the development forum thread: https://forum.ghost.org/t/upgrading-to-5-46-deleted-routes-and-redirects-and-broke-all-images/38152/7

nick

justincox I will need a bit of time to test this before updating the guide. But I'm wondering, did this happen with a ghost install from my older instructions or using the updated instructions I made on April 12th? In the mean time if your app structure is intact or if you can undo your manual changes, you can try using ghost update --rollback to go back to the working version (if you didn't make a backup beforehand). Then if you open a ticket we may be able to look at troubleshooting update issues.

justincox

nick I realized I misread the previous reply. My installation is working just fine, it's just placing content in the wrong place. Here's what I put in the Ghost forum that hopefully better explains what's going on:

The content path in the config is "paths": { "contentPath": "content/" }, which should point to /home/<user>/apps/ghost_app/instance/content/ since the config file is in /home/<user>/apps/ghost_app/instance/. When I changed it to read the full directory address, Ghost wouldn’t boot.

I manually moved the images, routes, and redirects files into their appropriate places from the /instance/versions/5.44.0/content/ directory. However, I know Ghost is still reading the information from the /instance/versions/5.44.0/content/ directory because I deleted the routes file from there and my routing rules broke when I rebooted Ghost despite them being in the appropriate /instance/content/settings/ directory.

nick

justincox I'm not sure why updating contentPath broke things for you when setting it in the config.production.json file. I just did that for your app and was able to restart it fine, which looks also to have fixed your broken links. The guide has been updated to include the full path here also. Hope this helps!

justincox

Nick, thank you. I'm unsure what I did originally, but it wouldn't boot when I changed the path. I appreciate your help here. This should hopefully keep things correct moving forward.

anjanesh

Any chance ghost will come back as a dropdown option in the applications section - atleast at the upcoming OS upgrade ?
I am a bit overwhelmed with this manual setup.

nick

anjanesh I suspect whenever we push the new OS release that it probably will support MySQL 8+ but I can't confirm that for sure. The instructions I supplied can be mostly copy/paste to completion. Using a find/replace feature of your favorite text editor could easily replace the variables for you in the guide.

justincox

Oooh, what are these coming OS upgrades you speak of??

nick

justincox Nothing official, but eventually we'd like to upgrade our web server operating system.

anjanesh

Any ballpark estimate on time-line for new OS upgrade - I have to decide on VPS now or later.

peter

anjanesh We hope to have our new OS setup ready later this year, but we don't have a set date or month yet.

justincox

Hi OS team! I'm running into trouble upgrading Ghost today. There is a new version of NPM available, but it won't let me install due to the an "unsupported engine." Since NPM won't update, neither will Ghost. I've included the log below for reference.

0 verbose cli /home/spaceghost/apps/ghost_app/bin/node /home/spaceghost/apps/ghost_app/bin/npm
1 info using npm@9.6.4
2 info using node@v16.20.0
3 timing npm:load:whichnode Completed in 1ms
4 timing config:load:defaults Completed in 4ms
5 timing config:load:file:/home/spaceghost/apps/ghost_app/lib/node_modules/npm/npmrc Completed in 2ms
6 timing config:load:builtin Completed in 3ms
7 timing config:load:cli Completed in 5ms
8 timing config:load:env Completed in 1ms
9 timing config:load:project Completed in 1ms
10 timing config:load:file:/home/spaceghost/.npmrc Completed in 0ms
11 timing config:load:user Completed in 0ms
12 timing config:load:file:/home/spaceghost/apps/ghost_app/etc/npmrc Completed in 0ms
13 timing config:load:global Completed in 0ms
14 timing config:load:setEnvs Completed in 1ms
15 timing config:load Completed in 15ms
16 timing npm:load:configload Completed in 16ms
17 timing npm:load:mkdirpcache Completed in 0ms
18 timing npm:load:mkdirplogs Completed in 1ms
19 verbose title npm install npm@10.0.0
20 verbose argv "install" "--global" "npm@10.0.0"
21 timing npm:load:setTitle Completed in 1ms
22 timing config:load:flatten Completed in 2ms
23 timing npm:load:display Completed in 3ms
24 verbose logfile logs-max:10 dir:/home/spaceghost/.npm/_logs/2023-09-03T14_50_02_029Z-
25 verbose logfile /home/spaceghost/.npm/_logs/2023-09-03T14_50_02_029Z-debug-0.log
26 timing npm:load:logFile Completed in 7ms
27 timing npm:load:timers Completed in 0ms
28 timing npm:load:configScope Completed in 0ms
29 timing npm:load Completed in 29ms
30 timing config:load:flatten Completed in 0ms
31 silly logfile done cleaning log files
32 http fetch GET 200 https://registry.npmjs.org/npm 23ms (cache hit)
33 timing command:install Completed in 53ms
34 verbose stack Error: Unsupported engine
34 verbose stack     at Object.checkEngine (/home/spaceghost/apps/ghost_app/lib/node_modules/npm/node_modules/npm-install-checks/lib/index.js:14:25)
34 verbose stack     at Install.exec (/home/spaceghost/apps/ghost_app/lib/node_modules/npm/lib/commands/install.js:110:16)
34 verbose stack     at async module.exports (/home/spaceghost/apps/ghost_app/lib/node_modules/npm/lib/cli.js:89:5)
35 verbose pkgid npm@10.0.0
36 verbose cwd /home/spaceghost/apps/ghost_app/instance
37 verbose Linux 3.10.0-1160.49.1.el7.x86_64
38 verbose node v16.20.0
39 verbose npm  v9.6.4
40 error code EBADENGINE
41 error engine Unsupported engine
42 error engine Not compatible with your version of node/npm: npm@10.0.0
43 error notsup Not compatible with your version of node/npm: npm@10.0.0
43 error notsup Required: {"node":"^18.17.0 || >=20.5.0"}
43 error notsup Actual:   {"npm":"9.6.4","node":"v16.20.0"}
44 verbose exit 1
45 timing npm Completed in 98ms
46 verbose code 1
47 error A complete log of this run can be found in: /home/spaceghost/.npm/_logs/2023-09-03T14_50_02_029Z-debug-0.log

sean

justincox I suspect the key error is here:

43 error notsup Required: {"node":"^18.17.0 || >=20.5.0"}

The latest version of NodeJS which is both compatible with Ghost and compatible with CentOS 7 is v16.20.2, so the npm that you use will need to be compatible with that version. The newest npm you can use is 9.8.1 which you can install as follows:

cd ~/apps/ghost_app
export PATH=$HOME/apps/GHOSTAPP/bin:$HOME/apps/GHOSTAPP/node_modules/.bin:$PATH
scl enable devtoolset-10 -- npm install -g npm@9.8.1

I've updated the procedure to use that version.

justincox

sean There's another npm update today that I'm unable to update. I tried following this path, just updating the npm version to the current requirement, but it didn't work. See the error report:

npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: npm@10.2.1
npm ERR! notsup Not compatible with your version of node/npm: npm@10.2.1
npm ERR! notsup Required: {"node":"^18.17.0 || >=20.5.0"}
npm ERR! notsup Actual:   {"npm":"9.8.1","node":"v16.20.0"}

Any suggestions?

justincox

You are amazing! I'm updating again as I hit this reply button. Thank you for the support.

sean

An updated version of Nick's procedure is available at: HOWTO run the latest Ghost with a private MySQL instance

justincox

sean Am I right to assume this is only for new installs and ones that followed the previous guide and all the updates above don't need to be reinstalled?

nick

justincox Right, you don't need to re-install. We just wanted a guide that was more accessible than mine, to avoid it becoming some buried reply to an ongoing issue.

sean

justincox according to your error message the software you're trying to update needs a version of node newer than the one that you are running.

If you need a node newer than v16 (ie something at 18.17.0 or newer) then you'll need to build it from source. There's an example build procedure at https://community.opalstack.com/d/1076-unable-to-install-node-18121-lts/9. Those instructions are for a slightly older version but if you bump the version numbers to what you need.

If you have trouble building Node from that procedure, please start a new post about it instead of adding to this one. Thanks!

irrgardless

Just read the entirety of this thread and I'm left with…questions. First off, I was able to install Ghost from the Applications dropdowns, yet the thread suggests that it still hasn't been added back?

However…I'm running into other issues. Specifically, /ghost's constant desire to have links pointing to localhost, probably because it's a proxied app. I hardcoded my main nav for now, but, I feel like there's got to be a better way.

…Should I not be using the dropdown install?

peter

irrgardless Our Ghost installer is fully functional, but there are some important post-install steps that you should take to finalize your setup and configure the URL that you want to use (instead of "localhost") - see https://docs.opalstack.com/topic-guides/ghost/#post-install-steps-important. That should be sufficient to resolve the issue for you, and there will be no need to hardcode anything in your nav.

kylotan

irrgardless This is a relatively old thread; a new one was posted recently which announced its return.

I used the installer last week, and it worked fine, once I'd applied the post-install instructions. Maybe the installer could do with highlighting the need to do that, but that's all I'd ask for.

« Previous Page Next Page »