Cloudron App Packagers
The new sidebar layout introduced in the recent versions is great. More and more apps are shifting towards this kind of layout, which is arguably much better for UI navigation.
Even though I've used Cloudron for years, I sometimes find myself scrambling in the documentation to search for a very specific information.
Having an external link button next to the heading, that points to the appropriate section in the documentation would be helpful.
As a sysadmin, I'd like to be able to receive email notifications when an app with automatic updates disabled requires a manual update.
What I meant is maybe the manifest can use "postgreSQL": { "prefixCount": 10 } and it creates 10 databases or something like that.
I like this approach. How would you handle changes with this count though, say it's 10 today but lowered to 5 tomorrow? Surely that'd be a breaking change. Otherwise, I think it'd be the easiest solution
@james I understand, I was suggesting a change for situations like Case 2 - a little more transparent but still a short message as to not confuse users/admins. 
This version is currently being rolled out gradually during testing.
We recommend waiting for the automatic update instead of installing it manually.
?
Spread the word
Post about new packages in the App Packaging & Development category of the forum.
Personally I think that category should remain more technical, devs needing assistance / having questions.
You published a different category : https://forum.cloudron.io/category/220/community-apps
I think that is where the word should be spread.
Just my 2p.
So, feeling stupid (more than normal) for starting with ZNC (Zeronet Conservancy), ZNX (ZeronetX) is now packaged.
Ignoring the vagaries of P2P and Tor, this does seem to be viable.
Git repo : https://git.cloudron.io/timconsidine/cloudron-zeronet (same) has been refactored into 2 folders, ZNC just in case someone feels they want to take it over / use as a base, and ZNX.
Docker image: tcmbp132021/cloudron-zeronet:v3.0.0
ZNX actually allows an ID to be created and ZNX-leaning sites seem to be alive.
I absolutely see the value of Zeronet for different uses, including hiding in plain sight (for legitimate reasons), and it seems usable enough. Old/abandoned/un-peered sites can be ignored. Set up active sites.
Haven't yet found a site to promote relocation of No.10 / Millbank PHQ to central Tehran, but I will keep looking. 
Sorry, maybe a stupid question, but I didn't find the answer anywhere. Don't we have any "Guide" on how to create the new Community Apps for Cloudron? How do I know how the CloudronVersions.json have to be configured. What are the requirements? Are there limitations? When I look at existing CloudronVersions.json it seems that Community Apps do not need to use the Cloudron Base Image anymore? Questions over questions
@jdaviescoates that's the correct behavior. it's being rolled out in phases. are you expecting something else?
the alternate message here would be "This update is being rolled out." but given our small team size, we want something deterring people from all updating at once.
I've come to the conclusion that, (my bad) out of ignorance of the history and status of Zeronet, packaging 'Zeronet Conservancy' was a huge mistake. I thought 'Conservancy' was a good concept. Seems it should have been called "preserve in aspic and never update it". Too much old history, broken/dead sites, embedded dependencies on defunct ZeroID (unless you're an old timer lucky to have one). So I am abandoning it, but work to date will be preserved in a separate folder in the git repo.
Instead, I will have a time-limited bash at packaging ZeroNetX ZNX.
Zeronet is a great concept, but it needs to work viably and realistically in 2026 and onwards.
