Hi GHOST Team,
I have had a bit of a frustrating go at upgrading GHOST this morning, so I’ll quickly explain what could be a bit better on the upgrade path.
Apologies if some of the stuff I want is very possible already, but it wasn’t obvious to me when I was upgrading, maybe I’m not the only one.
my 0.x setup
- pm2 runs ghost on VPN
- git hook restarts pm2 process when theme is pushed
- ssl is handled through letsencrypt and nginx (set up myself)
I have described a pm2 deploy with a git hook to restart ghost when I push my theme here: https://jonathanmh.com/node-js-ghost-theme-development-and-deployment/
This really didn’t seem very exotic to me until the upgrade.
Improvements for GHOST / ghost-cli
Overall I like the ghost-cli, but it’s painfully conservative and doesn’t allow a lot of
--force when one dabbles with trying stuff out.
- assume less about the stack, don’t force “required” setup steps
- allow easy specification of an alternative linux system username (I had one)
- detail instructions for setting config path of knex-migrator when upgrading (and that ghost migrate must be run afterwards)
- do care about nvm, it’s become a bit of a must-have for running GHOST in the past (long engine update cycles, other deployment systems have fine support for it)
Improvements for Theme upgrade
- possibly specify that
imagewill turn into
img_url featuredsince the helper name looks like a replacement for
These are the things I’ve run into and I’m excited for the upgraded theme API. Depending on how many 0.x GHOSTs are still out there, it might not be very relevant to apply all of this, but improving on the installation indstructions will benefit every new user as well I assume.
We’re running a blog for our photo side-business at gegenwind.dk with a custom theme, so it’s actually awesome to have multiple authors and better custom querying with
Thanks for listening on twitter and for generally being awesome!