It could simplify the setup and deployment of the entire web app if LyProX as a whole was an installable Python package.
We are actually not far away from that: Currently, we make an editable install from the cloned repository when we deploy the app to the host. However, having it published on PyPI would make version management much easier: I could change the settings and the functionality separately!
That would actually be a huge advantage, in my opinion! Right now, we make a new version of LyProX every time something in the nginx or gunicorn or systemd configuration must be updated. But it doesn't actually do anything to the logic. Likewise, why would I want to redeploy the entire thing when I just fixed a bug in the code?
Having the logic in a published package would allow us to simply run pip install --upgrade lyprox without changing the settings.
It could simplify the setup and deployment of the entire web app if LyProX as a whole was an installable Python package.
We are actually not far away from that: Currently, we make an editable install from the cloned repository when we deploy the app to the host. However, having it published on PyPI would make version management much easier: I could change the settings and the functionality separately!
That would actually be a huge advantage, in my opinion! Right now, we make a new version of LyProX every time something in the nginx or gunicorn or systemd configuration must be updated. But it doesn't actually do anything to the logic. Likewise, why would I want to redeploy the entire thing when I just fixed a bug in the code?
Having the logic in a published package would allow us to simply run
pip install --upgrade lyproxwithout changing the settings.