I've used the following script to do this:

This article will outline how I deal with managing my own data, tasks, hardware, people, etc. This is the latest of many versions - continuous iteration across many revisions has been done!

As Wasya Co offers one-click deployments of several applications and stacks, it makes sense for us to track our competitors. Nothing is new under the sun, and turn-key web applications (appliances) have existed for quite some time. There are many, many solutions for deploying infrastructure as a service (IaaS, SaaS). Multiple industries support the general Installation & Provisioning specialization. Of note, Docker, which we use extensively in-house, provides "one-click" deployments at scale, and more.

Coming soon...

This one is pretty easy. Between suffixes (namespaces), roots (what a thing actually is), and suffixes and all that, I like to use a suffix (a word-final thing, something that goes at the end of the word) that denotes the type of the thing (name, variable) being used. It probably sounds more complicated than it really is so here are some clarifying examples.

The following examples are either variable names, or properties of an object, or fields of a model, or methods in a class, or keys in a hash. Hopefully you get the idea.

If visual code opinionates about what you are typing, and you want it to stop, then perhaps you are looking for this setting:

"editor.acceptSuggestionOnCommitCharacter": false

Don't forget to backup your configuration file ~/.config/Code/User/setttings.json to be able to load it from backup later!

And while I have your attention, let's talk about configuring this text editor.

tl;dr: I decided not to do it.

Since Enzyme is obsolete as of React 18, you would use <render /> and not <mount />. Therefore, you don't have a wrapper to manipulate and observe the state of the component being tested.

Furthermore, I'm really only testing the component because it's a best practice, and because of the expectation of future complexity. The state change itself is trivial:

The solution for me was to clear Jest cache:

./node_modules/jest/bin/jest.js --clearCache

Seeing this ^ error and currently don't know how to fix it. It happens only on some of my (presumably identically configured) websites. This is happening when a user attempts to post any comment.

Turns out, this was due to a workflow rule that attempted to email the author of a parent-comment and notify them that their comment has been replied to. Since there is no parent comment, there is no email to send a message to, which was causing the error.

This is a non-obvious error I've observed in my docker containers running symfony on debian 11.

Found the solution on stack overflow. Re-installing the gpg key solved it:

wget https://packages.sury.org/php/apt.gpg 
apt-key add apt.gpg