What's coming in Cloudron 9.0 (was 8.0)
-
@girish said in What's coming in Cloudron 7.0:
Multihost support. i.e you can have many servers and have a single dashboard to manage users, apps and domains - https://git.cloudron.io/cloudron/box/-/issues/142
Great!
-
@girish said in What's coming in Cloudron 7.0:
Make it possible to restore without updating DNS. This is useful if you want to test out cloudron backups.
Also this is a very interesting feature! Hours saved waiting DNS propagation ...
-
@girish said in What's coming in Cloudron 7.0:
Features planned for 7.0:
Sounds like another wonderful release you're cooking up!
It's all great, but these are the big two for me:
- Multihost support. i.e you can have many servers and have a single dashboard to manage users, apps and domains - https://git.cloudron.io/cloudron/box/-/issues/142
- Add a way to manage apps <-> groups better. Currently, it's hard to get a grip on what apps a user/group has access to easily (maybe add filters as well).
Multihost support will be awesome - as will a way to easily see who has access to what apps!
Thanks!
-
@girish said in What's coming in Cloudron 7.0:
Multihost support. i.e you can have many servers and have a single dashboard to manage users, apps and domains - https://git.cloudron.io/cloudron/box/-/issues/142
This is huge. Since Version 6.2 is next, is 7.0 coming after 6.2?
Also, this will likely also be in 7.0 as of today:
https://git.cloudron.io/cloudron/box/-/issues/773 (reference:
https://forum.cloudron.io/topic/4473/event-to-webhooks) -
Yes, so the changes in master have already piled up and we have completed all the database migration related code changes. The database migration is kinda massive because we also have to pretty much test every app on the app store with the latest frameworks and databases. So, far I think we only have freescout which seems to have some issues with PHP 7.4 but we are only half way through our apps
I remember last time around we did this owncloud and wallabag was holding us back (both related to postgresql upgrade).I won't create a separate thread as such for 6.2 because we only see it as an intermediate release for Cloudron 7.
-
@girish said in What's coming in Cloudron 7.0:
I won't create a separate thread as such for 6.2 because we only see it as an intermediate release for Cloudron 7.
Any ETA on when 6.2 will be out, will that start later this week or will it be a while yet? No rush, just curious as I'm trying to plan some of my testing around that Backups behaviour fix for cleaning out missing backups.
-
-
Sounds awesome! You guys rock.
I've had an interest in multi-host support forever, but haven't been following the discussions as of late. Curious about how billing and support will work.
Is this a single dashboard for multiple cloudrons, so that we'll pay for each one separately? Or is it a single cloudron with multi-host capabilities, so that we just throw a bunch of machines on a single cloudron install and it just does its thing?
Thanks!
-
@malvim said in What's coming in Cloudron 7.0:
I've had an interest in multi-host support forever, but haven't been following the discussions as of late. Curious about how billing and support will work.
Is this a single dashboard for multiple cloudrons, so that we'll pay for each one separately? Or is it a single cloudron with multi-host capabilities, so that we just throw a bunch of machines on a single cloudron install and it just does its thing?We want to implement the latter i.e it's basically a single cloudron with multi-host capabilities, where you can add nodes to a single Cloudron install. As for pricing/billing, there will be some per-node pricing component to our existing pricing. I don't have the exact details yet.
-
@girish The most interesting thing about this is the way most hosts charge less per CPU/RAM for the smaller VPS tiers to capture people price-comparing.
It might be something that pays for itself, where growing single VPS CPU/RAM can be exponentially costly.
-
Most of the apps are updated to the new base image, yay! That was a lot of work
but atleast we can be confident that the apps work with the latest databases. So, we will push out a 6.2 release very soon with the following:- Move apps to new base image v3 - See https://forum.cloudron.io/topic/4366/docker-base-image-3-0
- Database upgrades - MySQL 8, Postgres 12, Redis 5, Mongo DB 4.2.
- Update node to 14.15.4
- Update docker to 20.10.3
- Make it possible to restore without updating DNS. This is useful if you want to test out cloudron backups.
- Add a way to manage apps <-> groups better. Currently, it's hard to get a grip on what apps a user/group has access to easily (maybe add filters as well).
- TLS addon (for DoT in AdguardHome)
-
Just finished up on the "Dry run" feature for Cloudron restore. You can use this to test your backups, test migrate to another server to see how well the server performs (for example, when you switch VPS) etc.
The way it works is :
-
you select this "Dry run" checkbox. When enabled, it will restore as always except it won't update the DNS.
-
Before you click 'Restore', add an entry in
/etc/hostsformy.domain.comto this new server's IP. You probably also want to add entries for your app domains if you want to test them. -
Once restored, and you feel happy, you can "switch over" to this new server, using the new sync DNS feature. This is in the
Domainsview.
-
-
-
-
@girish wouldn't it be a good idea to have something like a "pause switch" all it does is (don't know technically):
- "freeze" all the containers,
- then make a backup,
- migrate to new server,
- do some testing and
- switch DNS
- finally "un-freeze / un-pause" all the containers on the new server (leaving the old one freezed)
Between 1 and 6 you can show the now already available and customizable custom_pages and incoming mail is already buffered at the sender.
-
@imc67 This is easy to do manually in the meantime, but yes I agree it'd be awesome to have this process sort of automated. For me it's mostly just email I focus on that's likely to change between backup and restore, so I do a full system backup and once it gets to the "box" part of the backup I disable the mail container so that it won't receive mail after the backup. Helps a lot. Of course doing this if you have clients relying heavily on email like I do then it means you have to do this in the middle of the night though lol. The ability to automate this process would be awesome.
-
@imc67 Ah yes, we used to call this "retire" back in the managed hosting days
We used to show a page that the server is migrating. Incidentally, I just removed the retire script last night! It's really just systemctl stop docker boxbut of course these days you will see a "app is down page" instead of a better "migration in progress" page.I have created https://git.cloudron.io/cloudron/box/-/issues/774 but it won't make it to this release.
