Part of the process of having a new desktop is moving my Debian VM over, and by virtue of getting off the Windows Insider programme, being able to use VirtualBox again (for desktop purposes, Hyper-V is really substandard, it has a bunch of features that seem pretty great for enterprise use though).
Midway through, I noted that I haven’t documented the process of building out my toolchain for this blog, so here it is:
# apt-get install git python3-pip python-dateutil apache2 $ pip3 install --user setuptools pelican Markdown webassets jsmin cssmin
Note that my installation of
s3cmd is still using Python 2.7, so installing
python3-dateutil was ineffective. I’ll have to fix that at some point, as where possible I’m trying to move everything I write to Python3.
Next, to use Pelican from my local binary directory, I had to add the following to
$ cat >> ~/.profile # set PATH so it includes user's private PIP bin if it exists if [ -d "$HOME/.local/bin" ] ; then PATH="$HOME/.local/bin:$PATH" fi
Finally, point Apache (via
DocumentRoot) to my output directory so I can view changes on localhost before pushing them to S3. Don’t forget the
Directory entry so the permissions aren’t missing.
I also had to do some hackery to the
render_math plugin, in order to get it to place nice with the newer version of Pelican. I can probably undo this once the changes are merged but for now I’ll leave it.
Edit: Whoops, last commit wasn’t signed. Forgot to add the git configuration:
git config --global user.name 'James Fraser' git config --global user.email "email@example.com" git config --global commit.gpgsign true
Edit: About a week ago that pull request was accepted, so I upgraded my
render_math plugin and now I’m all sort for Python3 and Pelican.