Newsfeed

My Docker, docker-compose & jenkins setup for working on wordpress themes and plugins

First published on 2022-12-02

Hello all! In this article, I outline my local docker setup for developing wordpress plugins and themes. I use docker to run local mysql (multiple versions) and php (multiple versions) as well as manage the wordpress installed plugins. Furthermore, I use the same setup for deploying to production, so it is particularly useful.

The majority of configuration resides in Dockerfile and docker-compose.yml, however, I also have a few scripts and naming formalisms that facilitate development and rational thinking.

202406 Site Updates (June 2024)

  • Wordpress has been decoupled from the Drupal website. See also: a summary of how we made sure to preserve all urls and links during the migration. 
  • Bugfixes and minor stylistic changes
  • Added section StacksScrollerv0.0.0

20230713 UIUX Dailies: Iron Warbler

First published on 2023-07-13.

Working on a UI for a data visualization tool.



 

This screen will present some derivatives position in a new and innovative way, allowing humans' excellent natural pattern recognition to kick in, when analyzing trading data. Preparing to roll to a next position:

Hosts File Not Working on Mac? Try This Fix

I've recently had to re-do this. This has happened too often for me, and it's just very annoying in general. There are many problems (and offered solutions) around /etc/hosts file, for chrome only as well as for the os x generally. I've noticed that the /etc/hosts file works just fine for curl, but does not work for chrome. This led me to believe that the problem was a chrome setting, but upon fixing it, I am less certain that Chrome is the culprit. My solution is below. Basically, the host file needs to be ASCII-compliant. I've had that file soft-linked and modified by a number of actors.

How to manually execute a SQL query in Ruby on Rails

I run into this just now. The wrong way: 

results = ActiveRecord::Base.connection.execute("select * from users limit 10")

The right way: 

results = ActiveRecord::Base.connection.exec_query("select * from users limit 10") 

Somehow the formet executes the query without returning a result. If you want to actually see the results of SELECT'ing something, use the latter query. (Which also means that you probably want to use the former for INSERT'ing, though I have not verified.)