@james said:
If you find something unclear of lacking in the documentation ...
Just getting my head around the workflow, and I like to "spell things out" :
build the Community App (previously known as a Custom App)
(my 'old fashioned' approach : docker build, docker push, cloudron install, probably keep doing that because my build script does it, don't fix what ain't broke)
make a CloudronVersions.json file
same folder as project dev folder (Dockerfile, start.sh, CloudronManifest.json, README.md, POSTINSTALL.md etc.)
cloudron versions init
cloudron versions add
maybe add to my build script
why "CloudronVersions" in the plural ?
I guess Cloudron thinking is that a Community App might have v1.0.0, v1.0.1, v2.0.0
Very complete approach, lovely
but with cloudron versions revoke I wonder if this will ever be in true in practice (I would likely revoke every old version).
upload CloudronVersions.json to static hosting
gotcha
but if I have 10 Custom oops Community Apps, what is Cloudron team envisioning :
that I will have 10 Surfer apps (app1.tim.uk, app2.tim.uk, etc) ?
Or 1 sectioned Surfer app (communityapps.tim.uk) ?
Or no Surfer apps and just stick CloudronVersions.json in the relevant git repo (urls to files from git are not always clear) ?
I guess you probably don't care, but I'm intrigued what your expectations are
Cloudron CLI help typo ?
% cloudron versions --help
Usage: cloudron-versions [options] [command]
Hyphenated ?