1. Home
  2. Announcements
  3. What's coming in 4.2

What's coming in 4.2

  • girish

    4.2 will add the following:

    • Update apps to manifest v2.
    • Fix up apps to make migration easier. Many users are migrating apps from one Cloudron to another. For example, they install and setup an app in staging.domain.com and then move it to another cloudron at prod.domain.com. In such cases, the LDAP identification/auth causes problems because users of one Cloudron are different from the other Cloudron. We are fixing the apps to use username attribute consistently instead of uid. This means that as long as usernames match, migrations will happen seamlessly.
    • Migrate mongodb to cluster mode. New versions of Rocket.Chat require mongodb oplog to be enabled and also to run mongodb in cluster mode.
    • Rework app task. This is an internal code refactor but expected to be quite big.
    • Customizable app data directory - this will allow you to mount an external disk (like a DO block storage) and make an app use that storage block. This was expected to be in 4.1 but is blocked by the app task rework.
    4
  • girish

    Some updates:

    • All apps are now updated to v2
    • We have fixed app migration for all apps as well. It's not easy to migrate apps easily across cloudrons. We settled on using username LDAP attribute for all newly installed apps.
    • Mongodb is now migrated to cluster mode. This was part of 4.1.7.
    1
  • d19dotca

    I was checking up on things at git.cloudron.io and noticed that the email features we had discussed before were moved from milestone 4.2 to 4.3 which is disappointing though I understand you guys have a lot on your plate. Out of curiosity, since this is a pretty major feature that's needed for my freelance business / my clients, I'd like to know if possible a sort of time frame of when 4.2 and 4.3 are expected to land.

    Knowing the approximate time frames (like 4.3 in say 2-3 months maybe?) would be helpful so I can make changes to how I currently deliver these features for my clients. Right now I have been holding off making big changes because I knew they were coming in 4.2, but since they've now been moved out to 4.3, I'm a bit more concerned and would like to know some more data so I can make an informed decision on what I should do next.

    But please don't get me wrong - you guys are doing an awesome job and I'm definitely in love with this product! Happy it exists! 🙂 This is just a major feature I had prior to my move to Cloudron which I am really missing and some clients aren't as happy as they were because of it. That's on me of course, but that was not a limitation I expected to run into. Remember, if you could even just possibly tweak the number of addresses allowed in a forward rule in order to execute, that would at least buy me some time. Right now it's an unreliable workaround because anytime the server needs to be rebooted I have to remember to go in and make that change in the appropriate Docker container again. Maybe that tweak could still go into 4.2 even if just temporary? That would at least help remove the need to do it manually every time.

    0
  • girish

    @d19dotca It can still end up for 4.2. I just removed the tag, so it's not a blocker for 4.2. 4.2 itself will be out only in a couple of weeks, so there is still time.

    Implementing the forwarding is quite easy (and we already have something working). But for getting the delivery to be correct, we found that SPF is in conflict with email forwarding - http://www.luke.maurits.id.au/blog/post/spf-breaks-email-forwarding.html (is one rant). It looks the fix is to implement https://en.wikipedia.org/wiki/Sender_Rewriting_Scheme to make forwarding work. So, I am still investigating. I will keep this post updated.

    0
  • d19dotca

    Oh that's fantastic then, thank you @girish 🙂 Much appreciated. I just saw the milestone flag change and got concerned, thinking I may need to devise my own solution if it would be quite far into the future for that to come out. Glad to hear it won't be too long and could still make it to 4.2.

    0
  • d19dotca

    Any ETA for when 4.2 will be released? Or is it too early to tell yet?

    3
  • girish

    @d19dotca It's passed our e2e test now, so 4.2.0 will be out next week. It's a long weekend here, so wednesday.

    2 d19dotca 1 Reply
  • d19dotca

    @girish Perfect! 🙂 No worries, was a long weekend for me too in Canada.

    0
  • girish

    The initial 4.2 was pushed out yesterday. So new Cloudrons will get 4.2 already. But this will take some time to hit existing cloudrons. We also have some features/cleanups to do for 4.2 to be properly released - https://git.cloudron.io/cloudron/box/issues/647 . The unofficial change log is here - https://git.cloudron.io/cloudron/box/blob/master/CHANGES#L1652

    0 d19dotca 1 Reply
  • d19dotca

    @girish how do we force it? I assumed when you said it’s take a while to roll out to existing Cloudron’s I figured that’d only impact the automatic ones, but that it’d still be usable if manually requested in the Settings page using the Check for Update button, however it won’t find it when I do that. Is that intentional?

    0
  • nebulon

    @d19dotca yes that is intentional, what we do is we have a white/black list of domains to which we push out updates one after another. This allows more fine grained testing from our side. You can send us an email at support@cloudron.io and we can whitelist yours if you want to test it sooner.

    0 d19dotca 2 Replies
  • d19dotca

    @nebulon Okay, I kind of understand that methodology but I would still like to request then that for the future, when a user manually checks for an update it's because they want to update so that should be sort of auto-whitelisted (not to mention it would save you some unnecessary support emails). I can appreciate and totally understand scattering it for automatic download types, but it should be understandable from your side too that when a user is manually tapping the Check For Update button it's because they already know there's a new update out and are ready to deploy it. 😉 So it'd be great if that auto-whitelisted the domain.

    0
  • T

    Hey @girish. Congrats on the release! I know it took a bunch of work.

    Did this feature get pulled from the 4.2 release? I wasn't able to see it in the release notes or on the demo site. Really looking forward to this feature.

    @girish said in What's coming in 4.2:

    Customizable app data directory - this will allow you to mount an external disk (like a DO block storage) and make an app use that storage block

    0
  • girish

    @tamayers @d19dotca We have made the release available but it's only in use for new installations. This allows us get some early testing before we push it to all the existing Cloudrons. We are still working on the new app configuration UI + the mailbox forwarding feature. The data directory change is also there in the 4.2 release.

    0
  • girish

    Quick update: the mailbox forwarding landed today ! You can now creating forwarding addresses to external domains. Cloudron will do SRS and reverse SRS as required.

    2
  • d19dotca

    @nebulon & @girish - my Cloudron still shows 4.1.7 when I check for updates. I would definitely say this should be a feature request then that is a user manually clicks/taps the Check For Updates button, the latest build is presented. It would only generally be used when someone is aware of an update and expecting to install it. I understand the blacklist/whitelist thing but I would say it should be ignored when the button is pressed. The rollout using a blacklist/whitelist should only be done for those who don't manually use the button so it notifies them when it's ready.

    0
  • nebulon

    @d19dotca we don't push out 4.2.0 yet, even when checking for updates manually, has good reasons. We have found a few regressions which will affect existing Cloudrons, for example the stats view will miss data since that release would not reconfigure collectd as required. Newly created Cloudrons are not affected here.

    0 d19dotca 1 Reply
  • d19dotca

    @nebulon So to confirm then... 4.2 isn't really released at all then yet. It's pretty much in a "beta" state, used for new installs but nobody with an existing install will have received it yet unless we formally request our domain be whitelisted. Is that correct? There seems to be confusion here with the way things are being worded. 17 days ago it was stated "The initial 4.2 was pushed out yesterday" but now you're saying "we don't push out 4.2.0 yet" -- this is creating a bit of confusion.

    0
  • nebulon

    Yes correct, the confusion comes from the fact that we wanted to release it normally but found regressions which are blocking it for now. Sorry about the communication here.

    0
  • yusf

    It's out!

    Add external LDAP server integration

    This is very good. Now if only the reverse was possible too we'd have ourselves a real symphony. 🙂

    1 M 1 Reply
Log in to reply