What's coming in Cloudron 3.4



  • In an effort to build better monitoring, it would be good to look at supporting existing tooling as well. For example, a Prometheus exporter would allow users to take advantage of the robust feature set offered by Prometheus and Grafana. Or, if Cloudron already stores persisted metrics in a graphite database or something, a way to connect to that from an external server running a monitoring suite would suffice.



  • 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.



  • A Prometheus-compatible ,or even better an OpenMetrics endpoint would be fantastic for a much improved monitoring system.



  • Time for some progress updates!

    There is now a system menu:

    system-menu.png

    Inside which, there are services list. You can monitor and configure the services:
    services.png

    Backups can now be cancelled. Updates can also be cancelled. Yes, the layout is bit off here but it will be fixed before the release:
    backup-cancel.png

    Also, we have reworked the email handling for apps a bit to support some use cases. Currently, apps are create a mailbox of their own and one cannot easily access these mailboxes (if someone replied to the email). We have fixed this so that apps can now be associated with any existing mailbox. By default, an address is auto-generated for the app. You can then change this to an existing mailbox which you can access using your credentials. It's also possible now to share the mailbox name across apps.



  • this looks awesome, good job guys!



  • It was also requested to have an option to enable/disable automatic updates on a per-app basis. This was because for some apps like the LAMP app, the code in question might be tightly tied to the PHP version. So, people want to check the changelog before the update. We have added this flag now:

    enable-automatic-updates.png



  • Those changes really added up! We decided to roll out what we have as 3.4. The 'big data' issue is moved to 3.5 now.



  • @girish Great work guys!



  • Just a heads up for those who update manually by clicking the update button: the progress bar will get stuck at "Installing ..." at some point. This is normal. This is because of an API change between versions. Just go to my.<domain> directly and it will work.

    (also, most people won't hit the above issue since cloudron will auto-update)



  • @girish Curious if the docs about running private apps are available?



  • @girish @FTLAUDMAN
    Probably have your hands full with 3.4, but I'd love this as well. It allows us to expand the functionality of Cloudron to fill any holes in our deployment requirements, and eases the pressure on you guys to get apps out.


Log in to reply