Hexo in Win10 took me way too long

I really tried hard

It was my own fault, really…

I though it would be a fine time to start a blog, so I said “I know, I’ll use one of those cool static blog generators.”

I also thought it might be a good idea to use my creaky old Windows laptop, which was feeling pretty okay with Windows 10. Let’s do it!

  • Install Git!
  • Install Node!
  • Uh.. upgrade npm
  • Atom, because of course.
  • Terminal-plus for Atom… Or, uh, 30 minutes later PlatformIO ide terminal plugin because it actually works.
    • Don’t forget to set the shell to C:\Program Files\Git\bin\sh.exe and the login options to --login -i
  • I need Visual Studio 2015 CE? Okay. Okay. I can do that (for hours, apparently).
  • Python? Really? Sure. Yes. Yes, I also love Python.
  • Ctrl-s doesn’t work? Are you kidding? No hope? Ctrl-shift-s, enter, ‘y’ isn’t quite as convenient.
  • Did you know that Skype in Windows will take over your CTRL-S completely?
  • let’s get some ssh keys going for this machine.
  • eval $(ssh-agent) in .bashrc because that’s how I roll.
  • github repo, let’s keep it rolling
  • scrape a little space out of my old web hosting that’s normally doing other things.

What with all the downloading, installing, restarting, troubleshooting stupid problems (some Windows, some mine), this took 6 hours. Granted, most of that time was spent figuring out how to get Atom to open git bash (and install dependencies) so that I didn’t have to open two windows on my creaky old laptop. That’s why I wrote it down. JUST IN CASE.

It feels pretty rickety, frankly. But I’m blogging. Poorly. It isn’t Hexo’s fault, not at all. I quite like it, and I’m sticking with it. I’m just not good at blogging. Also, Windows 10 as a development environment for a Unix guy feels uncomfortable.

Share