Continuing from Update 7,
I’ve getting behind on my posts again, so the next couple document the legs flown, but without much other detail.
PAHO Homer – UGB Ugashik Bay



Articles, notes and random thoughts on Software Development and Technology
Continuing from Update 7,
I’ve getting behind on my posts again, so the next couple document the legs flown, but without much other detail.
PAHO Homer – UGB Ugashik Bay


From my previous post I noticed that I couldn’t re-connect to the Pi using screen after I’d disconnected using Ctrl-A Ctrl-D. Reading additional suggestions here, Ctrl-D is just a disconnect, it doesn’t end the process that’s attached.
Instead, use Ctrl-A Ctrl-\ and it will ask if you want to terminate processes using screen.
If you do detach, from here you can use this command to list processes attached to the serial port:
fuser /dev/tty.usbserial-11240
This will show a pid that you can kill, and then you can reattach again.
Over the past couple of years I’ve been working on and off on a personal project to migrate and update a GitLab CI pipeline on my self-hosted GitLab for building and deploying this site. Unfortunately my self-hosted GitLab used to be on a e-waste HP DL380 G7 rack server that I no longer have after moving house, so I’ve gone back to using my old 2008 MacPro 3,1 as a Proxmox server, where I now run GitLab (which oddly is what I first used this Mac for several years ago).
As part of the update, I wanted to achieve a couple of goals:
I won’t share my completed pipeline because I don’t want to share specifics about how my WordPress site is configured, but I’ll give an overview of what I used to automate various parts of it:
While I’ve ended up with a working solution that meets my goals (I can run the pipeline to deploy to my test server or deploy latest to my new live server), I still have a few areas I could improve:
Although this effort was spread over a couple of years before I got to a point of completion, it was a great opportunity to gain some more experience across all these tools.
Running and exposing default MySQL port:
docker run -e MYSQL_ROOT_PASSWORD=mypassword -p 3306:3306 -d mysql
mysql -u root -p
Running with a different exposed port on the host:
docker run -e MYSQL_ROOT_PASSWORD=mypassword -p 3307:3306 -d mysql
Connecting to server on different port : -P option, but also requires -h for host, otherwise seems to connect to whatever is running on 3306 by default:
mysql -h 127.0.0.1 -P 3307 -u root -p