<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
  <channel>
    <atom:link href="https://alaskalinuxuser.ddns.net/rss.xml" rel="self" type="application/rss+xml"/>
    <title>Alaskalinuxuser's Scratchpad</title>
    <link>https://alaskalinuxuser.ddns.net</link>
    <description>Commit thy works unto the LORD, and thy thoughts shall be established. - Proverbs 16:3</description>
    <lastBuildDate>Tue, 03 Nov 2026 10:55:51 -0900</lastBuildDate>
    <item>
      <title>Changing the control board on a Harman Iron Accentra pellet stove</title>
      <link>https://alaskalinuxuser.ddns.net/changing-the-control-board-on-a-harman-iron-accentra-pellet-stove</link>
      <image/>
      <description>&lt;p&gt;&lt;img src="https://alaskalinuxuser.ddns.net/bl-content/uploads/pages/f405c8448f09df0fb7c3190b11a3b53c/photo-2026-11-03-10-11-14-jpg.jpg"&gt;&lt;/p&gt;
&lt;p&gt;Yesterday, my wonderful wife had some unfortunate news for me: the Harman Iron Accentra pellet stove was on the fritz. For some reason, all of the lights started chaotically flickering on and off, not all together, but individually. Not only that, turning the pellet stove on lead to strange activity, as it would constantly turn on and off the various blower and feed motors, and failed to light the pellets. I had a feeling that the control board had finally given up.&lt;/p&gt;
&lt;p&gt;Having had the pellet stove for several winters now, I really have grown to like it. Yes, it is not a perfect backup heat source, as it still requires electricity to run, but it is so much easier to use than a wood stove. For one, you have a tiny exhaust, rather than a big stack. You can set and forget a temperature, or just turn a dial to have it light a fire automatically. The unit itself is very aesthetically pleasing to look at, and the glass front makes for a great ambiance when the fire is lit.&lt;/p&gt;
&lt;p&gt;I originally received this unit when I purchased a different pellet stove from a fellow church member who was leaving the state. Since I bought his other pellet stove, he offered me this broken one for free as well. Taking both home, I originally intended to use the other stove, but my wife fell in love with the look of this Accentra, and so I set about fixing it. It didn't take much to restore it to working order, though I did have to purchase two new sensors for it. I think one was an EDS (Exhaust Sensor) and a temperature sensor. After last winter, I did have to replace the heating unit, which gets hot and lights the pellets on fire, but overall, it's been a good unit.&lt;/p&gt;
&lt;p&gt;Over time, though, I had suspected something might be wrong with the control board, as occasionally the Accentra would do something unexpected. Nothing dangerous, of course, but confusing. It would fail to light on multiple occasions, or when being turned off, it would crank in more pellets with the feed motor. So, months ago, I purchased a new control board, just in case. This was very fortunate, because when I came home to the "bad news" yesterday, I already had the part I figured I'd need to get it back to working order.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://alaskalinuxuser.ddns.net/bl-content/uploads/pages/f405c8448f09df0fb7c3190b11a3b53c/Screenshot-20261103-100604-png.png" style="display: block; margin-left: auto; margin-right: auto;"&gt;&lt;/p&gt;
&lt;p style="text-align: center;"&gt;&lt;em&gt;A picture of the old/removed board.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The first thing I did was to check the wiring and fuse to make sure it wasn't something else. Everything else seemed to be in order, so a simple operation began of removing two screws, popping off the various knobs, unhooking the connectors, and swapping the board. It was pretty quick overall. Start to finish took less than 30 minutes, though I spent a good deal of time testing the unit afterwards.&lt;/p&gt;
&lt;p&gt;The only thing that was "odd" was that the new board fit several models. On the bottom of the board was a row of dip switches that you set for your particular model. For some reason, my model was not listed on the paperwork with pictures of dip switch settings. Fortunately, the old board also had this dip switch block, so I set the new board to match the old board, and drove on. The pattern was 00000001, if you need it for your board.&lt;/p&gt;
&lt;p&gt;Either way, glory be to God, the unit worked right off the bat and we are back to having a cozy and warm living room!&lt;/p&gt;
&lt;p&gt;Linux - keep it simple.&lt;/p&gt;</description>
      <pubDate>Tue, 03 Nov 2026 10:06:31 -0900</pubDate>
      <guid isPermaLink="false">f405c8448f09df0fb7c3190b11a3b53c</guid>
    </item>
    <item>
      <title>Fix the stars, and then a snow plow...</title>
      <link>https://alaskalinuxuser.ddns.net/fix-the-stars-and-then-a-snow-plow</link>
      <image/>
      <description>&lt;p&gt;&lt;img src="https://alaskalinuxuser.ddns.net/bl-content/uploads/pages/ecce1c8a1bd7e4ddf4b6d1f38356b1ce/photo-2026-10-27-08-02-09-jpg.jpg"&gt;&lt;/p&gt;
&lt;p&gt;Okay, not exactly fixing &lt;em&gt;real&lt;/em&gt; stars, but rather fixing a little planetarium.&lt;/p&gt;
&lt;p&gt;For school, one of my sons got a planetarium to look at the star formations, and it even has some slides with pictures of different planets that you place in a led/lamp style projector. Unfortunately, it arrived broken, but more unfortunate is that we didn't know it until a month later when we went to use it. By then it was past the point of return, so there was no hope of getting a replacement. Let's put it mildly that he was bummed.&lt;/p&gt;
&lt;p&gt;Aside from a nasty rattle of some broken part rolling around inside, it didn't look damaged, but I ended up taking the entire assembly apart to get to the insides. Essentially it is a control board, a motor, and two LED lamps with lots of plastic around them.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://alaskalinuxuser.ddns.net/bl-content/uploads/pages/ecce1c8a1bd7e4ddf4b6d1f38356b1ce/photo-2026-10-27-08-02-06-jpg.jpg"&gt;&lt;/p&gt;
&lt;p&gt;It didn't take long to figure out the problem, as the broken part inside (which turned out to be a plastic post that broke off), had rattled around and tore off the wiring which went to the USB-C connector for power. About 30 seconds with the soldering iron and it was back to functional, and then I spent some 20 minutes figuring out how to overcome the broken plastic part. But, a spring and a screw and a little bit of luck provided a solution, and, for all intents and purposes, it works as good as new.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://alaskalinuxuser.ddns.net/bl-content/uploads/pages/ecce1c8a1bd7e4ddf4b6d1f38356b1ce/oldplug-jpg.jpg"&gt;&lt;/p&gt;
&lt;p&gt;Next on the "needs fixed" to-do list was the plug in for my snow plow. You can't tell much from this picture, but the old connector for my snow plow had multiple pins that were busted, or wouldn't stay in place, or just didn't make good connections anymore. While this part is a straight plug, the other side is a 90 degree plug, and the wiring was pretty well beaten and torn. So, I replace the plugs with a 7 blade trailer lamp plug for all the controls, and a power plug that I took off of an old UPS battery backup system. It turned out rather nice, I think:&lt;/p&gt;
&lt;p&gt;&lt;img src="https://alaskalinuxuser.ddns.net/bl-content/uploads/pages/ecce1c8a1bd7e4ddf4b6d1f38356b1ce/photo-2026-10-27-08-40-58-jpg.jpg"&gt;&lt;/p&gt;
&lt;p&gt;Of course, I still need to mount them in some fashion. I was thinking of making a custom plate that they mount to, which is then bolted to the plow mount itself, but we'll see. Either way, it was a huge blessing that the wiring worked the first time I used it, and I feel like the plow moved better than it ever had before!&lt;/p&gt;
&lt;p&gt;Linux - keep it simple.&lt;/p&gt;</description>
      <pubDate>Tue, 27 Oct 2026 08:41:22 -0800</pubDate>
      <guid isPermaLink="false">ecce1c8a1bd7e4ddf4b6d1f38356b1ce</guid>
    </item>
    <item>
      <title>2026 Nextcloud Upgrade</title>
      <link>https://alaskalinuxuser.ddns.net/2026-nextcloud-upgrade</link>
      <image/>
      <description>&lt;p&gt;&lt;img src="https://alaskalinuxuser.ddns.net/bl-content/uploads/pages/d53c6b1e1c9c3686be971a44b971281b/apluss-png.png"&gt;&lt;/p&gt;
&lt;p&gt;In the continuing saga of upgrading my servers, I also needed to upgrade my Nextcloud instance. There were several hurdles and pitfalls for me here, and a lot of time was wasted trying to figure out exactly what to do. I had already decided not to upgrade my instance through the built in upgrade system within NC, but instead to build a new NC instance from scratch and then move my data over.&lt;/p&gt;
&lt;p&gt;That might seem odd, but several reasons led to this decision, the first being that the current NC instance had some sort of problem with the built in updater and was "stuck" on the previous version. Even when I could update, along the way something broke in the update software which forced me to do my upgrades from the command line instead of from the web interface. Less than ideal, for sure. It also helped that I only have a couple of family members using my NC instance, so I didn't need to move/create a ton of accounts.&lt;/p&gt;
&lt;p&gt;I also really wanted to try using the "AIO" (All-In-One) docker solution. In the past, I had to constantly fight with my server configuration and dependency problems to get a working solution for NC. I will be the first to admit, it probably was due to something I was doing wrong, but in either event, it was a headache keeping everything working and up to date. Often when updating, I would have to drop a feature or changed so many dependencies that some of the other uses of my server, such as serving other websites, would stop working. So this time I wanted a drop in solution that had all the features and 'just worked'. the AIO docker sounded like a win to me.&lt;/p&gt;
&lt;p&gt;Of course, with docker comes some new security issues, but hopefully I read up on that enough and implemented the proper precautions enough to make sure that is a very small, if not impossible attack surface. I won't go into too many details of that here, partly because I just followed other guides, and partly because I am concerned with sharing too much information on that point, for the safety of my server.&lt;/p&gt;
&lt;p&gt;But, one thing that really hung me up was how to configure the AIO NC on a server that serves other websites. Normally, I use Apache2, with reverse proxy, choosing different web root folders for the different domain names and internet addresses. Due to my lack of knowledge about docker, it took me a long time to figure out how to do this with the AIO instance. The AIO includes it's own Apache2 server, which is configured to be the sole service thereof, not leaving any room or options for my other websites that I serve.&lt;/p&gt;
&lt;p&gt;At first, I was erroneously trying to look into how do I run the AIO, and edit it's Apache configuration to include my other websites. This was backwards, I just didn't realize it at the time, and a lot of hours were wasted on that fruitless pursuit. After much research, and a little trial and error, I eventually came to this conclusion, run the AIO stand alone, but behind the reverse proxy of my Apache2 for the OS/server itself. But, I couldn't figure out what document root to use with the docker AIO on my Apache2 configuration. So I wasted a few more hours trying various methods of that. Eventually, I came to understand that when I run the docker, I could choose a different port number for it, and then used my reverse proxy to point incoming http/s requests on 80/443 that were for the NC instance to be passed to the new port number assigned to the NC instance! I didn't come up with this, I read it online [1] and I think this is actually the proper way it should be done, and it just took me several days of monkeying around to get there.&lt;/p&gt;
&lt;p&gt;So, my apache2 configuration looked like this:&lt;/p&gt;
&lt;pre class="language-markup"&gt;&lt;code&gt;$ cat nextclouddocker.conf 
&amp;lt;VirtualHost *:80&amp;gt;
    ServerName REDACTED.SOMEPLACE
    ServerAlias REDACTED.SOMEPLACE
&lt;pre&gt;&lt;code&gt;RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}
RewriteCond %{SERVER_NAME} =REDACTED.SOMEPLACE
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&amp;lt;/VirtualHost&amp;gt;&lt;/p&gt;
&lt;p&gt;&amp;lt;VirtualHost *:443&amp;gt;
ServerName REDACTED.SOMEPLACE&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;RewriteEngine On
ProxyPreserveHost On
RequestHeader set X-Real-IP %{REMOTE_ADDR}s
# Added to support Euro-office
RequestHeader set X-Forwarded-Proto "https"
AllowEncodedSlashes NoDecode

# Adjust the two lines below to match APACHE_PORT and APACHE_IP_BINDING. See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md#adapting-the-sample-web-server-configurations-below
ProxyPass / http://localhost:11000/ nocanon upgrade=websocket
ProxyPassReverse / http://localhost:11000/

# Enable h2, h2c and http1.1
Protocols h2 h2c http/1.1

# Solves slow upload speeds caused by http2
H2WindowSize 5242880

# TLS
SSLEngine               on
SSLProtocol             -all +TLSv1.2 +TLSv1.3
SSLCipherSuite          ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-CHACHA20-POLY1305
SSLHonorCipherOrder     off
SSLSessionTickets       off

# If running apache on a subdomain (eg. nextcloud.example.com) of a domain that already has a wildcard ssl certificate from certbot on this machine,
# the &amp;amp;lt;your-nc-domain&amp;amp;gt; in the below lines should be replaced with just the domain (eg. example.com), not the subdomain.
# In this case the subdomain should already be secured without additional actions

# Disable HTTP TRACE method.
TraceEnable off
&amp;amp;lt;Files ".ht*"&amp;amp;gt;
    Require all denied
&amp;amp;lt;/Files&amp;amp;gt;

# Support big file uploads
LimitRequestBody 0

# The default NEXTCLOUD_MAX_TIME value is 3600 seconds. 
# By setting it 10 seconds higher than that, we make sure that always Nextcloud times out and not Apache.
# If you increased NEXTCLOUD_MAX_TIME, increase the timeout below accordingly.
Timeout 3610
ProxyTimeout 3610
Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateFile /etc/letsencrypt/live/REDACTED.SOMEPLACE/fullchain.pem&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;SSLCertificateKeyFile /etc/letsencrypt/live/REDACTED.SOMEPLACE/privkey.pem
&amp;lt;/VirtualHost&amp;gt;&lt;/code&gt;&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;Thus my server's Apache2 config accepted requests on 80/443 bound for my NC instance, and passed them over to port 11000 instead, leaving all of the heavy lifting to the AIO's built in Apache server, with PHP, etc., and my OS/server doing all of the SSL encryption. Of course, to get the docker running, I had to edit the usual launch command to make sure it listened on that port instead:&lt;/p&gt;
&lt;pre class="language-markup"&gt;&lt;code&gt;docker run --init --sig-proxy=false --name nextcloud-aio-mastercontainer --restart always --publish 8080:8080 --env APACHE_PORT=11000 --env APACHE_IP_BINDING=0.0.0.0 --env APACHE_ADDITIONAL_NETWORK="" --env SKIP_DOMAIN_VALIDATION=false --env NEXTCLOUD_DATADIR="/data/ncdata" --volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config --volume /var/run/docker.sock:/var/run/docker.sock:ro ghcr.io/nextcloud-releases/all-in-one:latest&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Note that the APACHE_PORT is set for 11000, meaning the docker AIO Apache is listening on 11000. Also important to note is that I set --env NEXTCLOUD_DATADIR to a real place on my server, so I could easily move files in and out of the NC instance. It also makes backups easier.&lt;/p&gt;
&lt;p&gt;Speaking of moving files, I then needed to move 1.1 TBs of family photos, home videos, and audio recordings from the old server onto the new server and import them into NC. To facilitate this, I created a user named "OldServer" and in the OldServer NC folder, I digitally put all 1.1 TBs of data. To import it into my Nextcloud, I ran this command within the folder on the /data drive:&lt;/p&gt;
&lt;pre class="language-markup"&gt;&lt;code&gt;docker exec --user www-data -it nextcloud-aio-nextcloud php occ files:scan OldServer&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;And NC did the rest to import all the files. It took a while, because of all the data, but it was a lot faster than importing it through a web gui or app. Once the data was in, I shared the appropriate user folder with the appropriate user. I wouldn't recommend this for everyone, but since it was for my own family members, where we already shared all of the photos and videos and such, there wasn't really a security concern, nor any "sensitive" data. I could have put the appropriate files into the appropriate user's individual folders and then ran the scan for all or each user instead, if that had been a concern.&lt;/p&gt;
&lt;p&gt;Either way, it was a slow process, but I am really glad I did it this way because I learned a lot about using docker! I also really hope this will make future upgrades simpler and seamless, without the hassle of changing dependencies, since they are all built into the AIO docker instance. I did run a security scan of my server, and came out with an A+ certification for the NC instance, which was encouraging.&lt;/p&gt;
&lt;p&gt;Linux - keep it simple.&lt;/p&gt;
&lt;p&gt;[1] https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md&lt;/p&gt;</description>
      <pubDate>Mon, 28 Sep 2026 05:50:00 -0800</pubDate>
      <guid isPermaLink="false">d53c6b1e1c9c3686be971a44b971281b</guid>
    </item>
    <item>
      <title>2026 Server Upgrade</title>
      <link>https://alaskalinuxuser.ddns.net/2026-server-upgrade</link>
      <image/>
      <description>&lt;p style="text-align: center;"&gt;&lt;img src="https://alaskalinuxuser.ddns.net/bl-content/uploads/pages/eb944041486c3bbaa0bc1a9ebbbb28ee/rr-png.png"&gt;&lt;/p&gt;
&lt;p&gt;Well, it's that time of year again.... Well, more like that time of every other year again, where I upgrade my servers. Typically, I follow along with Ubuntu LTS releases, and the latest version available is 26.04, the "Resolute Racoon". This is particularly funny to me, since I have a friend of mine who refers to himself as the "Purple Racoon". Jokes will abound. I hope to chronicle some of the various changes, problem, and hurdles that I had to overcome in the coming articles, but I would like to discuss the overall plan and then the hardware portion of the upgrade in today's post.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The Plan:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Hardware upgrade - new and bigger hard drives&lt;/li&gt;
&lt;li&gt;OS upgrade - from 24.04 to 26.04&lt;/li&gt;
&lt;li&gt;Nextcloud upgrade - move to docker&lt;/li&gt;
&lt;li&gt;Website changes - changing CMS&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;I don't think that every item will get it's own post, but I will break them down and try to point out some of the interesting parts.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Hardware Upgrade:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This was actually the simplest part of the process this time around. I had an opportunity to pick up some new servers for free, but they were rather loud. I really like my old school rack mounted Dell Power Edge R520 servers, so I decided to stick with those. They are in really good condition, and I've put 128GB of ram in them already. With 2 six core processors, there really is no shortage of muscle for any of the really light lifting I do, which is running a half dozen websites and a Nextcloud server.&lt;/p&gt;
&lt;p&gt;I use two servers, one as the primary, and one as the backup. I keep the data synced between the two machines, so the backup is at most a day behind if the primary machine fails. I then take the backup machine offline and do a full backup of that machine to physical media which I keep off site. E.g., if my house burns down, I still have all of my family photos and documents.&lt;/p&gt;
&lt;p&gt;The only hardware change this go around, though, was the hard drives. My work threw out some servers that had several raid arrays in them, consisting of 12 TB hard drives. I managed to pull the drives and wipe them, then put them into my own raid arrays in the R520s. I think 36 TB of hard drive space will suffice for the time being! Each R520 has 5 of them, with one as the hot spare, and the other four as a Raid 5 array. I also have two 8 TB drives in a mirror (raid 1) for the OS, and one 8 TB drive as the dedicated hot spare for that. The OS itself really doesn't take up that much space, so the 8 TB mirror might be overkill, but it was what I had available.&lt;/p&gt;
&lt;p&gt;I also took the opportunity to "deep clean" the servers while I had the drives out. I keep them in a short rack on wheels, so I can easily move them around, slide them out, etc., for times like this.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;OS Upgrade:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;One of my goals with this upgrade was to move from Ubuntu 24.04 to Ubuntu 26.04, which was pretty painless. What helped make it painless is I opted not to upgrade from 24.04 to 26.04, but rather to do a clean install. Often when upgrading things can get wonky, and I find I spend less time configuring things from scratch than if I have to troubleshoot through why things don't work after an upgrade. So, a simple format, then USB thumbstick install of 26.04 and I was up with a fresh system in no time.&lt;/p&gt;
&lt;p&gt;A big change for me is that I didn't want to go the usual route of a LAMP stack like I've always done in the past. If you recall from my older blog posts, I often ran into problems where one of my blogging websites needs a certain version of PHP, and Nextcloud needs a different version, and then you have to configure apache mods to supply a different version for each, download PHP versions that are not in the repository, etc., etc., etc..... Didn't want to do that this time. Instead, I wanted to use the Nextcloud AIO (All-In-One) docker image, and flat file CMS (content management system), so I didn't need the M of LAMP, which is the MariaDB, and to simplify my P of LAMP, which is the PHP, to just be the normal system default. Kind of hoping for a 'no fuss' approach this time.&lt;/p&gt;
&lt;p&gt;So, that said, all I really had to install for the OS itself was the Apache2 and default version of PHP. I almost decided to do Nginx, mainly because I've never used it and wanted to learn new things, but I'm so familiar with the Apache2 web server that I decided to stick with it. Overall, this portion of the upgrade was very simple, and I completed it in no time.&lt;/p&gt;
&lt;p&gt;Then the real work started.... which I'll try to put into the next post.&lt;/p&gt;
&lt;p&gt;Linux - keep it simple.&lt;/p&gt;</description>
      <pubDate>Fri, 25 Sep 2026 10:34:48 -0800</pubDate>
      <guid isPermaLink="false">eb944041486c3bbaa0bc1a9ebbbb28ee</guid>
    </item>
    <item>
      <title>A New Blog CMS and a New Address</title>
      <link>https://alaskalinuxuser.ddns.net/a-new-blog-cms-and-a-new-address</link>
      <image/>
      <description>&lt;p&gt;&lt;img src="https://alaskalinuxuser.ddns.net/bl-content/uploads/pages/c7a1820a17e85af2cf6b9ac65d76e306/Screenshot-20260924-110229-png.png"&gt;&lt;/p&gt;
&lt;p&gt;Recently, I upgraded my server (posts to follow on that adventure). As well as updating the server, I also changed my blog software and setup. The short and the sweet of it is this, the old blog, &lt;a href="https://alaskalinuxuser3.ddns.net"&gt;alaskalinuxuser3.ddns.net&lt;/a&gt; is still up and running my Pelican generated static site. My plan is to leave it up for the time being, perhaps for as long as I blog, as a historic record of previous projects. However, going forward, I will be using the web address of &lt;a href="https://alaskalinuxuser.ddns.net"&gt;alaskalinuxuser.ddns.net&lt;/a&gt; for future blog posts.&lt;/p&gt;
&lt;p&gt;I decided to switch to Bludit CMS, a flat file site generator, rather than continue with Pelican for blogging. Both allow building posts in markdown, and both create a flat file website. However, Pelican has no admin panel or interface for plugins, which made the ability to create posts a little more tedious. Granted, for Pelican I had automated most of the process, with bash scripts and such, but it became a bit tiresome to have to transfer my posts files and media from whichever computer I wrote on to the server, then change the permissions, and rebuild the website for each post. With Bludit, there is an admin panel, and I can log in from any browser, upload media, make posts, save drafts, etc.&lt;/p&gt;
&lt;p&gt;Don't get me wrong, I love/d Pelican, but I just needed to simplify my life by making it easier to make posts. Why Bludit? Well, I wanted to stick with a flat file website system, so I tried several. I almost went for HTMLy, but decided on Bludit after trying them both on a local server. The interface for Bludit is very simple and easy to use. You can use markdown, or a WYSIWYG text editor instead. Bludit also has a Disqus plugin for handling comments. While I have not enabled it yet, I have had several requests from my (few) readers that they would like to be able to leave a note or thought on my articles, and that may be an avenue I go down in the future. We'll see.&lt;/p&gt;
&lt;p&gt;Either way, be sure to bookmark the new website, and also feel free to subscribe to the RSS feed!&lt;/p&gt;
&lt;p&gt;And remember, if you are looking for older posts (before January 2026), head over to &lt;a href="https://alaskalinuxuser3.ddns.net"&gt;alaskalinuxuser3.ddns.net&lt;/a&gt; to read them.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Linux - keep it simple.&lt;/p&gt;</description>
      <pubDate>Thu, 24 Sep 2026 11:38:10 -0800</pubDate>
      <guid isPermaLink="false">c7a1820a17e85af2cf6b9ac65d76e306</guid>
    </item>
  </channel>
</rss>
