Okay, it's coming back to me: I remember now that I need to use toolforge jobs. But trying to do so, and running bundle (Ruby equivalent of pip), it still fails due to missing *-dev packages. The first one is libyaml-dev. (for building the Psych gem, for pasing YAML.)

So, yeah, this page has all the clues.

I made progress: I ran "toolforge build start" on my repo, and the bundle finished installing, but then it couldn't run an intermediary step requiring loading the app, because a config file (not checked into git) was not there. It does exist in the tool's project directory. What can I do to get it copied over?

(I undersanding refactoring to use envvars would ultimately be better. Is there a way to make it work with the config file, though?)

Okay, I'm all set. For the benefit of anyone stumbling across this ticket: switching to envvars was simple enough, and the page I linked above gives the right recipe.

For my convenience (and because I keep forgetting the toolforge commands because I don't work on my tools very regularly), I made this simple script to remind me of the way to deploy updates to my tool (from within toolforge, after "becoming" my tool, "luthor", of course) --

$ cat update_and_deploy.sh
toolforge build clean
toolforge build start https://gitlab.wikimedia.org/toolforge-repos/luthor
toolforge webservice buildservice start --mount all
toolforge webservice logs