cozy
Always allow to update “static” applications
Always enabling the “update” action on static application would allow users to update a static website without having to deal with updating the version inside package.json.
It would make publishing static websites easier for users without a technical background.
Ping @lemelon
hum... maybe, we can propose same system than system used for application with server :
- If application is on master, update is available only if application has a new version.
- If application is on a branch different than master, update is always available.
What do think about that @clochix , @lemelon ?
We should find a system for really non tech savvy people, so I'm not a big fan of using branches.
IMHO, if the user know how to use git, it wont be an issue.
If he doesn't, he wont care if he has to copy/paste one more cabalistic formula in the mess below :
git init && git remote add xxxx && git add -A . && git push -u origin master
Joke aside, git is hard, and we could maybe spend our energy better by figuring a safe way to allow to use a cozy-files/folder as a website.
Another way to go would be to make the version field optional, and display an update button when the field is missing.
Maybe the real issue is that we don't have an update button, but a “an update is available” label, which isn't the same.
Another idea:
- Always have an update button for apps installed via git
- And install apps from market via npm.
It is a more complex way, but it'd have some benefits on the long term:
- no more build issue on github (the build is done only publishing to npm), thus no need for the development branch and a simpler workflow for contributions
- npm has a notion of prerelease, which can be helpful to have stable and unstable channels
- fast apps installation for cozys farm with a npm cache.
@nono installing apps from npm is out of scope here, you should probably open another ticket.