Chrome and Safari began forcing https for the .dev domain because someone apparently thought it was a good idea to register as a public TLD. Laravel Valet only produces self-signed SSL certificates though, so I want to keep my local installations served as http. Guess it's time to switch TLDs!
Oh, and don't try to use .local on a Mac because it conflicts with Bonjour local networking. I discovered this with 30 minutes of wasted effort. .test is the way to go.
valet domain test
Switch Valet to using the .test domain, which will also update dnsmasq accordingly. Don't try to edit dnsmasq configuration on your own — there are too many ways to go wrong.
wp package install wp-cli/find-command
Install wp-cli/find-command to find all WordPress installs in your Laravel project directory. It's convenient for running one WP-CLI command against all WordPress installs.
Run wp search-replace against all WordPress installs to replace instances of '.dev' with '.test'. ~/projects is my Valet project directory, and --all-tables ensures the procedure is run against all database tables.
Et voila! You've switched Laravel Valet from .dev to .test in three easy steps.
Facebook is essentially running a payola scam where you have to pay them if you want your own fans to see your content. If you run a large publishing company and you make a big piece of content that you feel proud of, you put it up on Facebook. From there, their algorithm takes over, with no transparency. So, not only is the website not getting ad revenue they used to get, they have to pay Facebook to push it out to their own subscribers.
Bylines is a modern rewrite of Co-Authors Plus that I started last April. It hasn't been anywhere near my primary focus for quite a while, so I finally called a spade a spade and started looking for a new owner. Fortunately, it's a perfect fit for the developers behind PublishPress — I'm glad my customers ended up in good hands.
Open source is one of the most powerful, and underappreciated, ideas of our generation. Modern open source is about building and collaborating in public, not about the license. Most importantly, open source isn't conceptually limited to software development; it's most prevalent here because we have the correct tooling.
The other day, I was reading Tualatin City Council's work session materials for January 22nd (PDF warning). It's actually pretty interesting. Tualatin is considering a "Local Congestion Relief and Neighborhood Safety" bond measure, and the packet provides much of the background. But it's a PDF packet and I was only reading it because someone emailed it to me.
Which brings me to the three realizations I had:
Open source is Good™ because it increases collaboration. Increased collaboration means increased value creation. Ergo, civic engagement (and pretty much everything) would benefit from open source methodologies.
City data is really hard to come by. It needs to be manually collected and it's often out of date as soon as it's collected. Nowadays, any effort put into collection should result in a real-time, persistent data stream.
Cities should be learning from one another. Meaning, Tualatin must have a data profile similar to dozens of other cities in the US. If city A tries experiment B and it works, then we should use that knowledge as the basis of our evolution, infrastructure investments and otherwise.