username/action@v1
way of versioning Actions work with that.
]]>
]]>
Redis
, PostgreSQL
, and MySQL
servers from hosting it inside my Kubernetes
cluster to managed hosted at DigitalOcean
.
At $15 each, I would have to save at least $45 on Kubernetes
cluster resources (nodes and volumes) by moving them. In the end, I succeeded at that and probably will end up saving even more as I’m
moving some Prometheus
exporters for certain things into my home Kubernetes
cluster. (Less expensive per month to run and not super important to have a high uptime/availability, to be honest.) Plus I’ve
been cutting down on services. On the plus side it comes with shiny graphs to look inside how the managed databases are doing
]]>The post is probably the most boring one as it is the table of contents. However, it will be updated every time a new post is published. Also, posts won't be written in a logical order but more in order of the things that are already done. As such the "Home Assistant" post will come before the "Node Software set up" post because the former can be done again without changes or data loss due to the "Terraform" and "Storage" posts.
]]>fibers
RFC went into vote.
Nor did it in 2019 when I started working on what would become React Parallel
,
a set of packages to me working with threads in ReactPHP
quick and easy. (A goal which I managed to hit IMHO.)
It started when I joined the ReactPHP
team to create the filesystem component and all we had where promises.
]]>
]]>
psr/log
all 3 versions can be used as you don't have to build classes on them.
However, for packages implementing PSR-3 this suddenly became more complex. All of a sudden you need 3 major versions
if you want to support all PSR-3 versions. For a package that only implements PSR-3 this isn't so much of an issue, but
when the implementation is embedded inside another package you all of a sudden reach dependency hell. And one thing I
learned while upgrading my packages is how deep our dependency on psr/log
goes these days.
The mistake I've made with at least one PR in the past few weeks is miss that a consumer of psr/log
is also an
implementer, and I missed that. So now I get to get back and make a new PR resolving that mess I introduced.
]]>
]]>