We were building releases for it from master since last package, but then we probably need clarification for why there are still being releases tagged now https://git.tt-rss.org/fox/tt-rss/releases

We will only package releases, ideally not directly from a master branch, so we will update the app with a new release once that is done upstream.

@Hillside502 any contributions to releasebell are welcome, it is developed by us anyways https://git.cloudron.io/cloudron/releasebell

@necrevistonnezr the package just got updated now to latest upstream release.

Unfortunately SOGo does not support this feature, as far as I am aware.

Yes, Cloudron already runs graphite and collects a lot of metrics, however those are currently only exposed as the graphs view in the dashboard. All this is not exposed directly. There is a rather generic graphs REST API available though, to run queries against graphite, but that is not currently documented. As a matter of fact, I am currently trying to bring back the graphite-web UI for inspection. I will check if there is a possibility on how to maybe expose more in that area.

@saglagla not really related to those, we are adding a view where one can see the addon status, logs, adjust memory limits and be able to restart them if needed. This should allow users to better understand what is happening if something goes wrong and the restart often times resolves issues if an addon gets stuck for whatever reason.

We used to have that button in the UI but we do not have an explicit "stopped by user" state, the platform would attempt to start all apps on reboot or such, in case an app was down for some reason. Maybe we should be adding a new explicit state for this archive feature? Generally we try to avoid cluttering the UI with such advanced features, but I think it makes sense for self-servicing the Cloudron better.

@necrevistonnezr not yet. We will create one, once we are confident enough that it works well. Currently it is only supported for new installations and we are collecting feedback on those now. Generally there is no risk in staying with 16.04 for the moment, so a dist upgrade is more risky than worth it right now. We are pushing out new Cloudron versions also for 16.04 of course.

Thanks for the reply! Definitely a great start, we will take it from there and refine it to put in our documentation to get more people started.