Server development outside of Zato service environment


I would like to develop and test some aspects of my services, for example accessing remote API or databases, without actually running under zato.

The problem I run into is that all my service code has import zato.server.service, which the always fails because it’s not part of the pip install.

Anyone know any relatively easy way to deal with this?


Hello @szmontsaroff,

to resolve imports, you can use the binaries that come with the installation.

For instance, if you install Zato to /opt/zato/current, you will have two commands:

  • /opt/zato/current/bin/pip
  • /opt/zato/current/bin/py

The former is pip and the latter is a wrapper around the python command that sets up PYTHONPATH.