Reader

Base Setup

Follow the instructions at:

https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+/refs/heads/master/DEVELOPERS.md

nota bene: supplemental dev env set up

Though this is covered in the documentation, to sum up the important parts

1. add xdebug configuration to .env

make sure .env includes

XDEBUG_CONFIG='mode=debug start_with_request=trigger client_host=host.docker.internal client_port=9003 idekey=vscode'
XDEBUG_MODE=debug

2. make sure host.docker.internal is routed to the host

make sure docker-compose.override.yml contains this:

services:
  mediawiki:
    # For Linux: This extra_hosts section enables Xdebug-IDE communication:
    extra_hosts:
      - "host.docker.internal:host-gateway"

vscode setup

3. install PHP Debug extension

install the PHP Debug extension to VSCode

4. add debug launch configuration

Open the launch.json configuration. Find this in the menu under “Run > Open Configurations”. Add the following:

        {
            "name": "mediawiki debug",
            "type": "php",
            "request": "launch",
            "port": 9003,
            "pathMappings": {
                "/var/www/html/w": "${workspaceFolder}",
            }
        }

Conclusion

You should now be able to run the “mediawiki debug” launch configuration, add a breakpoint, and step through an execution.

k3s agent with a data-dir

main node

curl -sfL https://get.k3s.io | sh -s - --data-dir /mnt

follower node

find the token one the main node at

sudo cat /var/lib/rancher/k3s/server/token

curl -sfL https://get.k3s.io | INSTALL_K3S_EXEC="agent --server https://<main-server>:6443 --token <token> --data-dir /mnt
" sh -s -

pumpkin pie latte

pumpkin pie latte have I been here before I'm not sure

the more things change the more they slip away I'm here now I'm here now

Dundas West where three trains meet I've come to know you But you'll forget me

fuck around

I'm getting a degree in fuck around and find out you won't see me when the curtains are drawn I make magnets do strange things high ands lows in stereo oddly pleasing

we won't be be coming back this place is going nowhere fast if we we stop, we gotta charge or we'll miss the band a donut and a pizza playing cards from Japan

Development Environments Running in Kubernetes

Primarily for simpler set up and developer experience. Our product has two services, and it helps if everyone can have their own development environment with the services wired up.

We also want this to be a CLI first tool, because our dev environments want to run on CloudVPS running an instance of k3s

• some of our engineers use Apple Silicone which has trouble running a kubernetes instance ** though perhaps we should have explored running a kubernetes in a VM

Either way we want

It has long been understood that personality types could be separated into two mutually exclusive groups: type A and type B. As far as I understand it, type A personalities are dominant leader types and type B are submissive follower types. Despite being mutually exclusive, I do not believe they partition the population. It follows that there must be more “types”, and I submit two more:

Type B+

A B+ type of person is the “lead from behind” kind person. While they're not dominant, they may be assertive. They're confident but humble, leaders when a leader is needed, and a worker-among-workers other times.

Type C

A C type of person dances to the beat of their own drum. They try to neither lead or be led. They are often confident, sometimes assertive, and never boring.

I believe there are more types, and I'm curious to know other's thoughts.

This is the blog.

This is the blog.