Skip to main content

Architect, former CTO, consultant, author, editor, and industry/web standards expert that still enjoys writing code. Opinions are mine alone.

John Evdemon

Quick reminder to myself if my domain isn't resolving as I expect:

My site has been down for a few days. I couldn't figure out why - all the DNS zones looked fine yet the domain still wouldn't resolve.

My hoster (GoDaddy) apparently updated my nameservers without telling me. Once I corrected them to use Reclaim's nameservers everything started working again.

John Evdemon

Movin' on up

1 min read

I'm in the process of moving into a new blog instance.

I've got lots of older content here and on this blog that I'm in the process of porting over to the new instance.

John Evdemon

Upgrade Time!

3 min read

I love Known - it's an elegant blogging tool that supports most Indieweb standards right out of the box. The biggest challenge I've had with Known is getting it upgraded.  I host my blog with Reclaim - a great little hosting service with excellent customer support.  The challenge I had is Reclaim only supported an older version of Known (0.92 - the latest version as of this writing is 1.0.0-rc.2+2019100601).  Upgrading Know shouldn't be that difficult except the documentation for installing and upgrading it is terrible.  I was finally able to get upgraded to the latest version of Known thanks to some help from Greg McVerry.  Listed below are the steps I followed:

Note: these steps are fairly generic and should work with virtually any hoster capable of running Known 0.92.

1. Create a subdomain under your domain

2. Enable Lets Encrypt for your new subdomain

3. Use Installatron to install the old version of Known into your subdomain - do NOT install Known into a cms folder (blank this default option out)

4. go to Terminal and change to the directory that corresponds to your subdomain

5. install Composer:
    php -r "copy('', 'composer-setup.php');"
    php -r "if (hash_file('sha384', 'composer-setup.php') === 'a5c698ffe4b8e849a443b120cd5ba38043260d5c4023dbf93e1558871f1f07f58274fc6f4c93bcfd858c6bd0775cd8d1') { echo 'Installer verified'; } else { echo 'Installer corrupt'; unlink('composer-setup.php'); } echo PHP_EOL;"
    php composer-setup.php
    php -r "unlink('composer-setup.php');"

6. run the following Composer command to install Known into a Known folder within your subdomain folder:

   Install latest stable version:
   composer create-project ido/known

    Install bleeding edge version:
    composer create-project idno/known -s dev
7. cd into the known directory

8. update the Known files using the Composer command:
    composer update
9. copy the updated Known files up over the older Known files that were installed by the Installatron:
    cp -R * ../
10. Go to https://your-subdomain.your-domain to login and start setting up the latest version of Known


  • The Twitter plugin wasn't working - it was causing server 500 errors when I tried to enable it.  I fixed it by starting up Terminal, going to the subdomain folder and entering the following Composer command.  I assume I could also use this command to install/refresh other misbehaving components:

           composer require idno/twitter

Update 2:


John Evdemon

OAM separates dev and ops concerns, enabling applications to be described once and deployed to multiple platforms.

John Evdemon

Nice overview of Azure Services

John Evdemon

Container Orchestration Learning Cliff

John Evdemon

Interesting. I need to better understand this. Anyone using Dapr out there?

John Evdemon

John Evdemon

I think I'm going to back this.

John Evdemon

Better yet, choose not to be offended. Just move on from stuff that might offend you. Taking offense is a choice because most people do not deliberately set out to offend others.