Ftp

Recently I have been playing with rsync a lot. In the process of synching source A to B, as well as synching between machines I have grown familiar with how it works. It is for this reason that the move from using ftp for rsync to update the static part of the website began to make sense.

When I write a blog post I update wordpress with the markdown from the static blog post and then I run hugo to prepare the static site. I then used Filezilla to upload the changed files.

Last night I started to install wordpress on the Pi5 and I got it to work. I then started to install ClassicPress via the ClassicPress switchtoclassicpress plugin and got blocked. I was blocked because in order for WordPress to update plugins, themes and wordpress it needs to have access to itself via FTP. That’s when I stopped for the night.

VSFTPD

This morning I installed vsftpd and the first part went well. Within a few minutes I had access to the Pi via FTP, and then changed from the default tutorial directory to the wordpress directory where apt install wordpress places WordPress. I was able to navigate the directories and see the files.

From the way people write about Github you would believe that everything has to pass through it, for anything to work but after some trial and error I found this to be a misconception.

I found that with GIT-FTP on Github I could upload and download files to a website after each git update. I learned this through following instructions for another workflow. I followed these instructions but because I use disroot rather than github the workflow didn’t work for me. I considered migrating my repository to github but chose not to.

This post has been updated, along with a few tags. Does this work as planned?

I like blogging with Hugo. I like writing my daily article in VIM and then exporting it to WordPress, before publishing it both with Hugo and WordPress. The build time for this build was 14 seconds but it can take up to 20 seconds. Although this i slow this isn’t the bottle neck.

New Files and Hugo

Every time you create a blog post, and every time you use a keyword that’s tag page has to be regenerated. If you use two, three or more tags then three or four pages need to be updated. As well as these pages needing to be regenerated so does the site’s index page, and others. If you include related pages at the bottom of the page, then every article with the tag also needs to be updated. The result is that tens, or even hundreds of pages need to updated at a time.