Deprecating MySQL

I migrated my main personal website from WordPress to Grav over two years ago. I found that I did not need the overhead of WordPress and MySQL for my low traffic websites. Since then, I have been gradually migrating all of my personal site over to Grav, and I have been reclaiming valuable compute resources with each migration. I have just two WordPress sites left, and when they are gone, the majority of my MySQL workloads will be gone as well.

I have been really happy with Grav's performance, and the extra compute resources have allowed me to put some of my personal projects on my public site. I could stop there and be in a really good spot, but why stop there? After all my little virtual server has more than enough resources to handle the remaining workloads that are MySQL dependent. From a professional standpoint, I encounter Postgres more frequently than MySQL so I decided to take the additional stop of migrating my last few workloads over to Postgres. The biggest workload to move will be my [digital twin])https://twin.peterwoods.online/) service.

In any case, I still have a bit more work to do before I can start on those Postgres efforts.