When installing a module keep the dependencies file on the pi. This will allow the main Allsky installer to add the dependencies when doing an upgrade with a venv.
Currently since the venv is created each time an upgrade is done there are no module dependencies in the venv which causes the flow upgrader to fail when attempting to load a module with dependencies.
I have added a short term 'fix' to the main Allsky installer so that it copies over the old venv folder when doing an upgrade, this is done without overwrite so as not to break any updated code !
Also add additional functions to the installer
1) An option to display module information
2) A system check
two new folders will be created in the /opt/allsky/modules folder
dependencies - This will hold the apt and pip files
info - Any readme.txt file available for a module
When installing a module keep the dependencies file on the pi. This will allow the main Allsky installer to add the dependencies when doing an upgrade with a venv.
Currently since the venv is created each time an upgrade is done there are no module dependencies in the venv which causes the flow upgrader to fail when attempting to load a module with dependencies.
I have added a short term 'fix' to the main Allsky installer so that it copies over the old venv folder when doing an upgrade, this is done without overwrite so as not to break any updated code !
Also add additional functions to the installer
1) An option to display module information 2) A system check
two new folders will be created in the /opt/allsky/modules folder
dependencies - This will hold the apt and pip files info - Any readme.txt file available for a module