Depending on which web framework you’re using, there might be better options than exactly reproducing the Toolforge environment. (Unless you’re debugging issues specific to that environment, I suppose.) For instance, Flask https://wikitech.wikimedia.org/wiki/Help:Toolforge/My_first_Flask_OAuth_tool has a development mode which automatically reloads source files as soon as they change on disk, and offers you an in-browser debugger when an error occurs. It’s amazing, I can’t recommend it enough.
Cheers, Lucas
Am Di., 2. Juni 2020 um 15:28 Uhr schrieb Arthur Smith < arthurpsmith@gmail.com>:
I've found it very useful with php tools to use the instructions here:
https://wikitech.wikimedia.org/wiki/Help:Toolforge/Kubernetes#PHP
where it says "You may run the container on your *local* computer (not on Toolforge servers) by executing a command like this: ..."
which allows testing changes locally in a nice way before deploying them.
However there doesn't seem to be anything equivalent for the python images
- I can see what's available here:
https://wikitech.wikimedia.org/wiki/Help:Toolforge/Web#Python_(uWSGI)
and I can see I should use the image docker-registry.tools.wmflabs.org/toolforge-python37-web (by the way, docker-registry.toolforge.org does NOT work right now when fetching images!)
but I can't figure out how to tell the image where to find the python app in the docker start command. Any hints out there?
Arthur _______________________________________________ Wikimedia Cloud Services mailing list Cloud@lists.wikimedia.org (formerly labs-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/cloud