I've updated my .plan file yet again. The usual warnings apply.
I've updated my .plan file once more. The usual warnings apply.
UPDATE - 20170512 - More SQL surgery.
So, as you've no doubt noticed I've been running the Bolt CMS to power my website for a while now. I've also mentioned once or twice that I've found it to be something of a finicky beast and doing anything major to it can be something of an adventure. I tried to upgrade my site last week (tonight, by the datestamp on this post) and had to restore from backup yet again because something went sideways. That something was the upgrade process going wrong and throwing an exception because of something in the cache directory, where Bolt temporarily stores HTML files rendered from templates used to make pages that your web browser displays.
As it turned out, the upgrade process was choking on the old cache directories created and used by v2.x of the Bolt CMS. Here is the upgrade process that I used:
- BACK UP YOUR SITE.
- Log into your web hosting provider's server via SSH.
- Download the latest version of the flat file structure build of Bolt.
- If you didn't back up your website, BACK UP YOUR WEB SITE.
- cd ~/my.website.here
- If you didn't back up your website and things go pear-shaped, it's your fault. Don't say I didn't warn you.
- Uncompress the new version of Bolt you just downloaded: tar xvfz ~/bolt-latest-flat-structure.tar.gz --strip-components=1
- Try running the upgrade: php app/nut setup:sync
- If it throws an exception on you, erase the entire on-disk cache. Don't worry, it'll be rebuilt as people visit your site: rm -rf app/cache/*
- Try running the upgrade again: php app/nut setup:sync
- It should complete successfully. If it doesn't you may need to do the following two things before re-running the upgrade command again:
- mkdir -p app/cache/production/data/
- chmod -R 0775 app/cache/
- If you still have problems, jump into the Bolt CMS Slack chat and politely ask good questions: https://boltcms.slack.com/
- If the command finishes normally, try opening the frontpage of your website. It should be up and running.
- If you can see the frontpage of your website, try logging in. You should be able to.
- Try making a test post with a new entry. Be sure to test saving the post partway through. You do save your work every few minutes, don't you?
Special thanks to Bob and thisiseduardo in the Bolt CMS Slack chat for their assistance and hand-holding while I stumbled around trying to make this hapen.
It's the holidays. I'm pretty busy right now, and hoping I don't have a sinus infection. I haven't forgotten about anybody. I'll get to the time-sensitive stuff first, and rest as I can.
Nope. No GLaDOS references today.
As you may or may not be aware, certain parts of the world have come under fire, literally. This has hit me very hard in some very tender places, and I'm not handling it well. Dealing with it has, to a large extent, required staying offline so I don't fry my forebrain.
Work's running me pretty hard, with multiple late-nighters strung end to end.
I'm working on my slides for HOPE in my spare time. I might even get to practice them soon. After that comes more proof-of-concept code that you (yes, you!) can try at home.
Windbringer's power cell is on its way out; I just ordered a replacement, which also means that he's due for more major surgery to install it (because the Dell XPS 15 is very Macbook-like in its hardware layout).
I keep falling asleep before 2100 hours local time.
Don't think I'm sick, don't think any of my dental work is going bad. Just running hard to stay in place at the day job.
When I've got it in me to write coherent blog posts, I will do so.
Be good to each other out there. The world needs it.