@LoudLemur very good ... now that I can read it
A little "opinionated" in places, but that's fine if that's how you want to manage your AI. I prefer a little looser. Some things have to be told (e.g, RO/RW), others can be more guided.
| S3 Storage | minio |
Hmm, should we be saying this ?
I don't recall the issues exactly about minio, just decided to stop using it as unreliable in terms of the future, so closed my mind to it. And I don't recall what is Cloudron official stance
In any case 'minio' is not listed in Addons in Cloudron docs, so this should not be in the same section as the other elements.
But plenty of S3 options, Hetzner, Scaleway, others. And I packaged GarageS3 with UI, which is working nicely for me (still a custom app)
cloudron/base:4.2.0
I am packaging everything with 5.0 now
Application expects: /app/code/config/settings.json → READ-ONLY at runtime
You must provide: /app/data/config/settings.json → Actually writable
Solution: Symlink /app/code/config → /app/data/config
I think some AI can mis-understand this, that the emphasis is not only that it should be in /app/data, but that it must be called settings.json
Better as :
/app/code/[config/][settings.json|config.json|.env]
AI will understand the point better.
Control your AI agent, but empower it - it has knowledge and experience which you don't have. If you're too dictatorial, you'll get what you have always got. A little bit of permissioning, and you might find some nice new more efficient ways of doing something.
