Klever

Storing large amount of data in the Klever repository is strongly discouraged. If it is necessary, however, then the only possible way to avoid copying of said data is to use "editable" mode during pip install (-e option). This solution is currently recommended by pip developers.

pip 20.1, that you use in CI, contained another, experimental solution to this problem: building of local Python packages in place, without copying them to the temporary folder. Unfortunately, this experimental solution had a number of issues and was quickly reverted in pip 20.1.1. These issues are still not solved 8 months later, so it is probably a very bad idea to keep using pip 20.1.

• The first one is build bases. To avoid it I think that we can add a special option, say, "--klever-data-directory" to klever-deploy-local, so that users will be able to provide custom locations of build bases rather than to use deployment scripts to install them. In fact, I guess that this is relevant just for CI.
• The Bridge media directory. This stems from the fact that in the development mode Bridge is configured and launched directly from sources. I think that here it is possible to follow almost the same way as for the production mode but instead of using "/var/www" deployment scripts should use the Klever deployment directory.

BTW, note "This additional command, however, should be skipped if Klever Python package was installed in editable mode (with -e flag)." is not correct when it is necessary to update dependencies (Python packages) of Klever.