The ;install REPL command can be used in conjunction with the update button next to each project listed on the installed page within maiden.
Apologies for the table, maybe it will make the behavior more clear or maybe not!
| action |
source |
result |
;install <url> |
git |
git clone <url> |
;install <url> |
zip |
download, unzip |
install button from catalog |
git |
git clone <url> |
install button from catalog |
zip |
download, unzip, rename based on catalog entry |
update button from catalog |
git |
git pull (regardless of how the repository was installed) |
update button from catalog |
zip |
(re)download, unzip, rename only if installed from the catalog
|
At the end of the day maiden is trying to provide as uniform an experience regardless of whether the source of the script/project is a git repository or a zip file. It has some heuristics to name/rename the project folders correctly if the zip/git files are coming from github.com, gitlab.com, or bitbucket.com.
Yes this - prior to this version of maiden the web application contained logic which tried to maintain a cached copy of the code local to the browser for fast initial page load. This cache meant that it took 2x refreshes before the latest version would load (at times). In practice maiden is so tiny the cache was more trouble than it was worth and thus removed in this release. I would expect from this point forward the need to refresh will go away.
If there is any doubt which version you are seeing, the version number can be found at the bottom of the configuration dialog (click the gear button).