Hi Alexander,
Thank you for raising this. I have just made a change in the repository. Please "git pull" and run the setup.py install again.
Then, in your configuration.yml, wherever you have a process that you want to be listening in one IP address, add the "bind" next to it:
protocols:
port: 65432
bind: 10.30.150.61
What receives is a string that is provided as bind() to the flask server. If you leave it empty, it will be listening only in localhost. If you put 10.30.150.61, only in that interface, and you might optionally want to put "10.30.150.61 127.0.0.1" or whatever (I don't think you need it in your setup, however).
On the other hand, I see in your configuration.yml that you might be programming your own experiments using the managed approach. We highly recommend using weblablib:
In the future, we are going to replace WebLab-Deusto for something else that will also be open source, but easier to maintain and using a more modern approach (and Python 3, etc.). That future new version will not support managed laboratories, and will rely on weblablib or in your own unmanaged library if you prefer as long as it is compatible with the unmanaged protocol that you can find in the documentation.
In the meantime, WebLab-Deusto is compatible with weblablib, and you can use weblablib with Python 3, etc. In LabsLand,
all our laboratories are using weblablib.
Just in case it helps, in all our (LabsLand) real-time labs, where we internally use WebLab-Deusto, our configuration is basically a single host, with a set of core servers (e.g., 4), each in their own process, a single laboratory server (in its own process), and then as many experiments as needed using weblablib (which you can have in multiple RPi or wherever, and more than one). I can share an example if you want.
Best,