Bare metal updating master and handling frontend-build

[AlfBaz]

I do a git fetch and log often, you guys don't mess about and couldn't thank you enough for the amount of work you guys do

Once I've backed up off-server, recorded changes etc and pulled the latest changes I invoke update

When it's finished I scroll up to get the url for the latest frontend-build from the text that gets spat out about Github not allowing artifact downloads.
I download it on the local pc I'm on, scp it over to the server, then sudo mv it to inventree's src directory, sudo chown it, switch back to inventree user and invoke frontend-download --file frontend-build.zip
I then do another invoke update.

A couple of quick questions

• Is `invoke update' and the ensuing msg the only way to get access to the latest frontend-build?
• After carrying out invoke frontend-download is another invoke update necassary?
• Another, probably misguided step I do (in case there are python or tool updates that have happened) is after a git pull but prior to source ./env/bin/activate is I delete directory env and recreate it with python3 -m venv env Is this step a waste of time?

No problem at all just curious

[matmair]

Running invoke frontend-download and invoke static should be enough to get the frontend. If you deploy tags of releases, the downloader should be possible and done automatically by the frontend-download job (or can be triggered by invoke frontend-download --tag 0.13.0).

• You could also install node and yarn on your system - then the frontend would be built on the system during the update cycle
• Only a invoke static is needed after frontend-download
• you do not need to delete the venv every time, only when the python version on your server changes (3.9 to 3.10 for example). Not doing that will speed up things by a lot probably

[AlfBaz]

Thanks heaps, I'll check all of that out