Command to update on each run all scripts, extensions, embeddings, etc. ?

[illtellyoulater]

Is there a command we can put in web-ui.bat or web-ui.sh to update on each run all extensions, scripts, embeddings and anything else which was pulled from a repository?

[ResleyZ]

I'm not extremely knowledgable about Git stuff, but you should be able to use these commands with Git Bash;

ls | xargs -I{} git -C {} pull to go through the folders one by one,
ls | xargs -P10 -I{} git -C {} pull to update the folders in parallel of each other.

I personally have all my scripts, extensions, etc. in their seperate folder, outside of the WebUI folder, and have it set up like this for example.

• Scripts
• • Git Repo's
• • • repo1, repo2, repo3, update file
• • Loose files

[illtellyoulater]

@ResleyZ yes, I actually do something similar for embeddings, which I have in dir outside of WebUI.
In that dir I have a text file listing all the embedding repos URLs and a shell script like this

while read p; do
	echo "$p";
	git clone "$p";
done < $1

which I call with: update-all-repos.sh repos.txt

but, the downside of it is that I have to manually update repos.txt every time I add a new repo, so your solution is more powerful and I think I'll start using that :)

However it would also be cool to be able to update all repos in place inside the WebUI dir (of course only for embeddings, scripts, extensions, not touching anything on which WebUI is built on, and that could break it).
But of course for this to work WebUI should support searching for scripts, embeddings, etc. placed in subdirectories of ./scripts, ./embeddings, etc. and this currently only works for extensions.

If this behaviour was standardized then by tweaking your script above a little we could have a simple and robust way to update every non-default WebUI component in place, along with the main git pull in web-ui.sh used to update WebUI itself.

[MrKuenning]

#3600

[illtellyoulater]

@MrKuenning in your solution at #3600 you have to specify the extensions you want to be updated manually while we are discussing of a way to make this automatic for any extension (scripts, and probably embeddings, etc.) present in their respective folder.