Just to follow up, I did get this working. The main thing seems to be
setting up a uwsgi.ini file that works, then the docker run command just
needs to call something like "sh -c "/usr/bin/uwsgi --ini "; setting up the virtualenv is also needed as a preceding step, which
can be done with similar
>
> 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
>
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
On Tue, Jun 2, 2020 at 7:28 AM Arthur Smith wrote:
>
> 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!)
docker-registry.toolforge.org is a tool for
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
Hello!
Next week we'll be rebuilding and upgrading the hardware that provides
DNS service to cloud-vps and toolforge. These rebuilds will start at
14:00 UTC and the whole process may take 2-3 hours. It's likely that DNS
lookups will be somewhat slower as clients fail over between the
Hello!
Next week we'll be rebuilding and upgrading the hardware that provides
DNS service to cloud-vps and toolforge. These rebuilds will start at
14:00 UTC and the whole process may take 2-3 hours. It's likely that DNS
lookups will be somewhat slower as clients fail over between the
Hi there!
The soft deadline for migrating to the toolforge.org domain was two days ago, on
2020-05-31.
For adopting the change in a controlled way you only need to run the webservice
command with the --canonical argument. Please review the documentation here:
Hi there!
The soft deadline for migrating to the toolforge.org domain was two days ago, on
2020-05-31.
For adopting the change in a controlled way you only need to run the webservice
command with the --canonical argument. Please review the documentation here:
