I’ve been working on setting up a Docker container environment allowing to test the RuneStone Interactive server.
That’s the part which I wanted to be able to operate for test purposes. As it is a
web2py application, it’s not exactly obvious to gather all dependencies and run locally. Well, in fact it is, but I want to understand the architecture of the tool to be able to understand the deployment constraints, so making a docker image will help in this purpose.
The result is the following :
- a container image which allows to test web2py over Apache (with mod_wsgi) on Debian (see it on github : olberger/docker-web2py-debian)
- a container image (reusing the previous one) which allows to test runestone (see it on github : olberger/runestone-web2py)
Now, it’s easier to test the writing of a new course (yet another container above the latter one), and directly test for real.