While setting up the system on a new server, I discovered that my make_credentials makefile recipe required commands that were not available. As it was developed on a system that already had conda installed, there was already a python distro accessible via the command python (rather than python3), and that python distro already had it came with pip and the ability to make venvs. It appears Ubuntu/Debian don't come with venvpython functionality, so either a new user would have to sudo apt install python3.1X-venv or install conda (if they didn't have sudo privileges). This feels like a rather irritating requirement, so maybe I'll want to return to having a separate python container to run startup processes.
I'll also want to update the makefile to check for command python3 if python doesn't work.
While setting up the system on a new server, I discovered that my
make_credentialsmakefile recipe required commands that were not available. As it was developed on a system that already had conda installed, there was already a python distro accessible via the commandpython(rather thanpython3), and that python distro already had it came withpipand the ability to makevenvs. It appears Ubuntu/Debian don't come withvenvpython functionality, so either a new user would have tosudo apt install python3.1X-venvor install conda (if they didn't havesudoprivileges). This feels like a rather irritating requirement, so maybe I'll want to return to having a separate python container to run startup processes.I'll also want to update the makefile to check for command
python3ifpythondoesn't work.