Go to content Go to menu

I’ve been trying to ramp up quickly on a number of projects, which all use similar yet different stacks. Some of them have documented/established practices for setting up a dev workspace, but, I’ve always wanted to try using Lando to set up a dev environment, and now that I have to set up a few of them, it feels like now’s the time to get my hands dirty: use a tool built to rapidly iterate until I have a workspace. Learning as I go.

I didn’t really grasp that’s what I was doing, but several hours into writing my first lando.yml file, and asking for help in resolving the error messages I was seeing, someone over in the Lando Slack kindly suggested that I start smaller… after I get something working, then build up from that success. Seems obvious, right? It was quite an aha moment for me.

I commented out most of my work, and focussed on getting a database working. I defined success as having an environment in which I could load a copy of some production data, run some queries, destroy the workspace, start over, reimport the same data, and try other things. And, this turned out to be a great place to start.

In case you’d like a head start on learning how to use Lando to write your own dev workspace, here are two different seed projects:

In the spirit of learning as I go, I will update this post as I finish up different dev workspaces. I’ll define “finish up” as making a pull request for the project, and having the PR accepted. I have two in the works so far, with more surely to come.

UPDATE: Two Pull Requests Accepted

I think I’ll turn this into a series. My next article will be on using Lando with Django. Any web application framework that relies on scaffolding is a good fit for this “learn as you go” approach. More later.

UPDATE: Well, Part 2 turned out to be even easier, a live coding demo I did with some colleagues, setting up a dev environment for Omeka-S.


First Day

Mar 9, 12:56 PM

Today is my first day working as a Publishing Systems Developer at California Digital Library. I’m still settling in and meeting people, but I really like the people I have met so far. I am really glad to be moving back into the realm of repository work. As a Publishing Systems Developer, I’ll be working with journal publishing systems, and since the tech stack is a bit in flux, I don’t really feel comfortable naming names just yet, but, if you’re familiar with that field, you can probably guess what I’ll be working with. Here’s the job description (I don’t know how long that will stay up). The short version is: I’m going to be working for CDL as a remote developer. My new boss is based in Chicago, so we share a time zone, which will be very convenient. Since CDL is part of UCOP, which is part of UC, all my benefits and accrued vacation and sick leave transfer over from UCLA. I’m looking forward to learning more about my new work, and possibly keeping this blog up to date with the things I learn. No promises, but, here’s hoping I follow through on that.

Now I have to update a ton of profiles all over the internet.