What's coming in Cloudron 3.4
-
wrote on Nov 24, 2018, 11:51 AM last edited by
Regarding backup, please also have a look at https://forum.cloudron.io/topic/1575/backup-improvements-restic-as-backend. Thanks.
-
Any roadmap plan for running your own docker containers, even via command line? Hate spinning up another VPS just for bitwarde_rs
-
@FTLAUDMAN We had added some support for running private apps. The doc pages are not ready yet, expect it sometime this week.
-
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.
-
wrote on Nov 28, 2018, 10:31 PM last edited by
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:
Inside which, there are services list. You can monitor and configure the services:
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:
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.
-
Staffwrote on Dec 9, 2018, 2:32 AM last edited by girish Dec 9, 2018, 2:34 AM
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:
-
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.
-
wrote on Dec 14, 2018, 6:20 AM last edited by
@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)
-
@FTLAUDMAN We had added some support for running private apps. The doc pages are not ready yet, expect it sometime this week.
-
wrote on Dec 17, 2018, 7:45 PM last edited by
@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.