Cloudron Forum

timconsidine

% cloudron versions add
Error: Bad changelog format or missing changelog for this version

'CHANGELOG' is present :

* 1.0.0
- Initial release

But I don't see any mention in cloudron docs what format is expected.

Maybe error is because this test community app has a CloudronManifest.json entry of :

"changelog": "file://CHANGELOG",

Does 'cloudron versions add' not recognise/support this way of doing it ?

EDIT : I changed CloudronManifest.json to read :

  "changelog": "v1.0.0 - Initial release",

Then 'cloudron versions add' worked

Not suggesting anything needs fixing as such. But potential mismatch of usage. Simple text string is easier - but it won't be practical for complex changelog descriptions.

And this cheat works :

 "changelog": "see CHANGELOG",

Not sure I should be cheating, but ...

girish

Update to 8.2.0 is blocked by https://github.com/rocketchat/rocket.chat/issues/39328 . Submitted a PR - https://github.com/RocketChat/Rocket.Chat/pull/39497

Package Updates

[3.0.0]

Update Rocket.Chat to 8.1.1
Full Changelog
This release introduces a wide set of breaking changes focused on removing deprecated, end-of-life, and legacy functionality.
Support for MongoDB 5.0 and 6.0 has been discontinued, and workspaces must upgrade to MongoDB 8.2 before moving to Rocket.Chat v8.0.0, with a full backup strongly recommended.
Several services, settings, and integrations have been removed, including Streamhub, database watchers, Tokenpass OAuth, Mobex and VoxTelesys SMS integrations, second-layer transport encryption, built-in logging tools, legacy Game Center and WebRTC Livechat calls, Off-the-Record messaging, Omnichannel Voice and Current Chats, and the old FreeSwitch-based VoIP architecture.
Twilio is now the only supported SMS provider, and admins are expected to rely on the official Prometheus and Grafana monitoring stack for observability.
On the API side, the /v1/users.createToken and /v1/e2e.updateGroupKey endpoints have been undeprecated, with added security requirements for token creation.
Overall, this release cleans up long-standing deprecated features and shifts workspaces toward modern, supported alternatives, with full details available in the Deprecated and phasing out features documentation.

Lanhild

@girish IMO, the version information wouldn't matter for a notification email. I'd just like to know when a manual updates required

girish

@lanhild I see.

The mysql multipleDatabase feature was written initially for phabricator, which is now long gone. AFAIK, no app uses multiple mysql databases. Same for postgres (though maybe synapse matrix + the user auth is a candidate, not sure).

girish

@Lanhild of course, the instances of the same app could all be on different versions.

girish

@andreasdueren There is now a cloudron sync push/pull which only uploads changed files . Work similar to rsync in the sense that it uses size+mtime to detect changes.

It's not possible to use rsync binary itself. That requires either ssh or rsync daemon - neither is available in app containers.

girish

[7.1.0]

Add cloudron sync push and cloudron sync pull subcommands
Merge all binaries into single cloudron command

Lanhild

@girish mostly private custom apps. Though, I can see this becoming useful for some apps that manage authentication or background jobs by using a different database from runtime. Apps with testing/lab environments also benefit from multiple databases

Lanhild

@girish great question. I think an email aggregating updates per app would be fitting

Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.

Cloudron Forum

AppDev

Posts

Member List