The scenario describes one or more developers committing their changes of code for a serverless Azure Function App ("Function-as-a-Service") and managing the required Azure environment resources only by a declaration in Terraform scheme in the code repository to remain the Single Point of Truth (SPOT).
Whilst preparing and testing our Docusarus instance, I realized that the RSS feed URL used by our old blog system did not work anymore because Docusaurus generates the content in a different way.
While migrating a Magento module to make use of the declarative db schema, I ran into the following MySQL error:
MySQL error code 121: Duplicate key on write or update
Meet Magento UK went virtual for the past two years as most conferences did, but in 2022 they are back with an in-person, all-day conference again. YEAH!
When we introduced our chapters as part of our circle based structure, we had the idea to publicly announce what our chapters are doing, what technologies they are using and how they are working. When it came to the tooling decision, Docusaurus came up pretty quickly as it comes with multiple features that fit our technology stack out-of-the-box:
Since 2013 we have been using Silverstripe and the Silverstripe blog module as our blogging engine. After all those years, it is time to revisit and improve our toolchain as our requirements have changed over the years.
We decided to settle with Docusaurus for now. We'll share the "why" in one of our next blog posts, so stay tuned ;)
A few weeks ago, whilst applying the latest security patches for Magento, I ran into a problem in our build pipeline. The patches could be applied locally without any issues, but in our build pipeline applying the patches failed.
After migrating our old LDAP Server to a new instance, we realized that the EntryUUID attribute had changed. One of our internal applications relies on that attribute so we had to modify it to not break things.