First of all, I just want to say, writing posts is really neat.
You have this clean editor with nothing to disturb you, and you pretty much have the WYSIWYG-editor, a word counter. That's it! And that's about all you need to get started.
And whenever you start a new paragraph, you can select if you want to add something extra there, like importing a video from YouTube, an image from Instagram or anything.
Anyway, this is not an ad for Ghost, more about my first impressions about it.
I started using Ghost since it looked really neat, and from the demo webpage, had lot of promise, I had high hopes for it.
Setup was a breeze, just installed a Docker-image, did some few tweaks and set it up through a reverse proxy in nginx. (Actual config below)
Now, the real reason why I wanted to try out Ghost, was both for my normal dayjob at MultiNet Interactive AB, so we could build a developer portal, that was easily extendable, but still powerful while retaining performance. And as a replacement for the CMS used for handling the less static pages that we have on The Fuel Rats Mischief website, because we don't like the current one, but haven't found a good replacement for it, as of yet.
Here I noticed the first thing missing.. when I read Ghost website about features and everything, it all looked really good. I mean, it still is really good. But I'm missing what I feel is a key feature, and that's the easy way to build plugins/apps for it.
Since I'm a content creator (Twitch Streamer), I thought that I would love to have some easy way for me to just add a module that runs behind the scenes and fetches my online status on Twitch, to see if I'm live or not. Sounds easy, right? So I started reading all the documentation and found that the apps-support suddenly seemed to have vanished (at least the information on how to create them have).
But since, I'm also a developer, I decided not to give up, because I don't want to sully my reputation as a developer.
And then I went to type in
crontab -e, just to see that
cron is in fact not installed, so we head off to install that as well. (I can tell you this, things like
uptime are missing too), and then we just figured out what user we should run this script as (for correct permissions and all) by looking into the
/home-folder, so that we can run the cron job as that user.
And when I feel advanced enough, I might change this into a websocket-thing instead, so that I add a websocket that serves the above JSON-file, so I can act on "live" updates. But for now, we will have to do with polling.