Cloudron App Packagers
In your documentation i found this
‘ SECRET=$(openssl rand -base64 64 | tr -d '\n')\ncloudron env set --app tymeslot.yourdomain.com \\n SECRET_KEY_BASE=$SECRET \\n PHX_HOST=tymeslot.yourdomain.com \\n PORT=4000’
Information like the domain are exposed by Cloudron already. https://docs.cloudron.io/packaging/cheat-sheet#environment-variables
Can't stop laughing
I got a little frustrated with one package.
AI error
I challenged it "robustly"
Its response ?
Very cheeky, since the login error was not creds, but paths set by AI.
My original Cloudron-Facilmap package has been re-packaged as a Community App, so available for installation through AppStore "Add a Custom App".
Prior to it being added in @community-apps, you can find it here :
https://communityapps.appx.uk
I'd personally really like FacilMap - I think @timconsidine has packaged it but none of his many packages have yet made it into the new Community Apps, but presumably it won't take too much more work to get them in there...
Facilmap has been re-packaged as a community app.
Small delay as I attempt to build a publishing process.
Other apps will follow.
I have messaged @James about getting it added to the category.
In the interim, for my own organisation, I will put all my community apps here : https://communityapps.appx.uk
Thanks @girish
TBH, most people don't read docs despite all this
Yep, true
Soon there won't be any docs. AI coding agent utility will produce some illegible binary asset "cloudron.aifood", which another agent will use. We humans won't need to know or read anything. 
Thanks @nebulon
maybe better some https://foo.bar/changelog link
nice idea, let me think about that.
testing my build script which makes it a mandatory input (to overcome my lack of discipline 
)
cli revoke only revokes the last entry, user might want to revoke previous ones
Good catch, added this now. cloudron versions update already had --version.
docs for CLI should explain more about 'cloudron build' and 'cloudron build build'
For the tutorial, we switched to using source builds as the default approach. The next "advanced" step is to build using a local or remote builder. https://docs.cloudron.io/packaging/tutorial#alternative-build-methods explains cloudron build and automatic tags.
TBH, most people don't read docs despite all this 
The longer the tutorial, the even lesser it will be read.
@timconsidine I just have a quickie script:
docker build -t tag . --no-cache
cloudron install --image=tag
@murgero I'm with you 
The bash build script I am building uses a parameter :
echo " -p 0 = install only, 1 = publish (revoke/add/push)"
If command has -p 0, it does cloudron install --image ....
If command has -p 1, it does cloudron versions add etc.
Not sure how it will work in practice, needs some real-world usage.
Yeah the build process I have I actually avoid using cloudronversion for testing the install until I see it work with cloudron install --image first. I dont mind it taking time but its a janky build process. CI/CD goes a long way but I can't be bothered atm lol
Trying to smooth my workflow for CommunityApps (w/o mentioning Safari ) ...
) :
Although I guess they are probably in a script so maybe it does not matter.
