What's coming in 5.2
-
Here's what you can expect from 5.2. We are still working actively on a few more apps and the apps have more priority. Specifically @nebulon is working on Bitwarden and I am trying to get Jitsi/BBB.
- Update base image - this should update many packages, the vim/bash history configuration etc.
- Some user onboarding flow - don't have concrete plans here. But sometimes new users are confused by all the automation we do - like db, email, user management. Feels very magical, so we have to put in some videos/images to re-assure them/explain what's happening.
- Add support for member-only mailing lists.
- Support for external volumes for apps
- Default to ECC certs from Let's Encrypt.
- App firewall (protect login screens and login routes of apps)
Any more suggestions?
-
Great news as always, you guys are doing an incredible job!
If you want more things to do, I would suggest a feature that you already once had (I think): The possibility to add links to adminpanels for the apps in the dashboard (maybe in the manifest?), maybe on the left side when you hover it (like
/wp-admin/for WordPress,/_admin/for surfer). There are probably a few more of those, but those are the main ones that I'm using.Not sure if that's something anyone else wants, but I would be up for that
-
@msbt Yes, there's a field in the manifest for this. Both taiga and limesurvey also have those admin links "hidden". Maybe we can add 'admin panel' button left of the docs button.
-
I was thinking on the dashboard icon itself, but left of the docs works for me as well
-
@girish could you elaborate on what adding external volumes will do? Sounds like this would be adding additional controlled servers to an existing installation?
-
@echokos Currently, there is no way for an app to access data on the host/server. For example, let's say you have lots of photos or videos in an external drive or accessible via NFS, there is no way for the app to access it because of the containerization. Volumes will provide a way to mount host paths into containers. If we implement volume sharing, one use case is you can download a file via torrent and have the media immediately viewable via emby.
-
@girish The symlink approach is always available though?
-
@yusf I guess you mean creating a symlinking straight in the appsdata directory? That won't work because the container can see what the symlink resolves to but cannot access the resolved path itself since it can only see within it's own file system.
-
@girish Right. That wouldn’t be very isolated if it did work.
-
@girish Ah, got it. Thanks that will be useful as well.
-
Like I've mentioned via email, I'd really appreciate email aliases - I have a couple of domains where I receive an email, so - mario@{domain1.com,domain2.com,domain3.com,..} is essential for my workflow.
-
@mario said in What's coming in 5.2:
Like I've mentioned via email, I'd really appreciate email aliases - I have a couple of domains where I receive an email, so - mario@{domain1.com,domain2.com,domain3.com,..} is essential for my workflow
Same here, this would be great and hopefully not too hard to implement. But there are most likely higher priorities in future development work to get done first.
-
Would it be possible to get a measurement of bandwidth used per month per container (in and out)?
-
-
@girish said in What's coming in 5.2:
@mario @NCKNE so a single mailbox with aliases? Essentially just like the current alias but across domains.
Yes, I believe that is a common scenario for business implementations.
-
@girish said in What's coming in 5.2:
@mario @NCKNE so a single mailbox with aliases? Essentially just like the current alias but across domains.
That's indeed it, and @NCKNE is right - it's a business requirement.
-
On notifications, when Redis runs out of memory, we get just a GUID - that takes time to track down which app that is to increase memory. Any way to tie that back to the deployed app name or URL?
-
@doodlemania2 Yes, redis changes are coming in https://git.cloudron.io/cloudron/box/-/issues/671
-
Because I just gave a user the "User Manager" role (I thought this would enable a user to manage the users of a certain group): It would be awesome to lock that user-manager to a specific domain/group, so all other users won't be visible to that person.
Same goes for admin vs. group-admin (admin = global, group admin can only install/manage apps, email and users on the (primary-) groups he's added. This way you can let people manage their own users without interfering with other groups. Does that explanation make sense?
-
@msbt Yes, I think so. A couple of people have requested a sort of "group manager"/"group admin" role. We can look into it for the next release. We are hoping to get 5.2 out next week or so.
-
Another +1 for group managers (I've mentioned this before of course
). This would relieve a lot of my reservation on granting user manager to certain folks in some organizations! -
Exactly what @jimcavoli said.
-
I think Jitsi and/or BigBlueButtom would be great!
I hope you don't loose the timing for it, because after somebody chooses a platform for its users is difficult to change. If it were ready now I'm sure Cloudron would have many more new users. -
Wanted to give some progress on the release here. Both @nebulon and I are taking a bit of break for Jitsi
We will revisit once we finish some more enjoyable tasks.-
Update base image - this is done! Apps are slowly getting updated one by one.
-
Add support for member-only mailing lists - done!
-
Default to ECC certs from Let's Encrypt - done!
-
Redis status - Under services, you can now tune redis instance of each app
App firewall will not make it this release since the changes are stacking up.
-
-
Volumes/External mounting - we did a couple of iterations of this and neither of them are satisfactory. The feature itself is quite easy to implement but what we found is that other than Emby and Nextcloud most apps don't support scanning random directories for content.
To go back to why people were trying external storage to start with had to do with Cloudron backups not having flexibility wrt backup policy and persistence. So, we are going to look into fixing that first instead (in this release).
-
@girish Sounds great, well done for the work and really glad to see the mailing list feature!
As for external storage, understandable choice for a first implementation. In a second time though, even if it only work for Nextcloud and Emby, that could still be a decent step forward too.
And for Jitsi, sounds like a right headache. Thanks for having tried hard for a while now. Did you get any support from upstream devs?
-
@avatar1024 We haven't contacted upstream devs. From what we have seen, most people who try to install the non-debian packages are basically stuck with incomplete docs. One has to just reverse engineer from the deb package source code. It's all open source, so it just takes time to decode.
-
Some more updates.
-
Clicking the update button now will always give you an update, if it's available. No more required to ask us to whitelist an update.
-
Encrypted backups - there were security flaws with the current encryption. It's been fixed (more info when we do the actual release). thanks to @mehdi who has patiently worked with us through this.
-
App graphs! Currently, just RAM and Disk. CPU and Network will come later.
-
System graphs
-
Backup listing UI for the platform
-
New backup retention policy (this is same as keep daily/weekly/monthly in borg/restic).
-
Finally, there is a way import and export the backup configuration easily. You see this in the right of the backups. You get a config file that can then be put in another Cloudron instance for restore or import.
We hope to get this out next week. Just doing a lot testing now.
-
-
@girish Loving the graphs! Eager to get 5.2.
-
@girish One very minor thought. "Cleanup Backups" seems like a mouth-full. Maybe something like "Purge backups" or similar?
-
@d19dotca Currently, that button actually doesn't remove backups. It just cleans up backup based on the backup policy (i.e it triggers the cleanup-backups cron job instantly). Maybe, I will keep it hidden for the coming release, because I can see it needs some explanation.
-
I'd still really like to be able to filter apps in the app store by LDAP support
-
Full text search for email really important and much needed too. Would make ditching Gmail a little more bearable given how limited all open source webmail clients are.
-
And once we've got Jitsi Meet and BigBlueButton being able to scale a single instance of Cloudron across multiple servers will become ever more important too.
-
We are slowly rolling out 5.2 to a more wider audience week. The exact version as of right now is 5.2.3. Actual release announcement will follow in two days or so.
-
@jdaviescoates Thank you, server-side e-mail full text search is high on my wish list, too. I have already ditched gmail in anticipation of the more great things to come. Cloudron rocks.
-
An update on the rollout, we have found some regressions with 5.2.3:
- If you enable/disable email, it will show an error popup in UI. This is a harmless error and can be ignored.
- If you have a stopped app which uses redis, then backups fail (it's more nuanced, it fails if you stopped it after you updated to 5.2.0/5.2.1/5.2.2)
- App disk graphs are not working.
We will fix the above for 5.2.4.
-
@girish said in What's coming in 5.2:
An update on the rollout, we have found some regressions with 5.2.3:
- If you enable/disable email, it will show an error popup in UI. This is a harmless error and can be ignored.
- If you have a stopped app which uses redis, then backups fail (it's more nuanced, it fails if you stopped it after you updated to 5.2.0/5.2.1/5.2.2)
- App disk graphs are not working.
We will fix the above for 5.2.4.
One small annoyance: If you give app passwords for different the same name, it throws an error that the ID is already in use. Example: I wanted to use the same device name (e.g. iPhone, iPad, PC) for the app password for mail, radicale, nextcloud etc.. After setting up the mail password calling it "iPhone", I couldn't name the app password for radicale "iPhone", too.
-
@necrevistonnezr Good catch. Looks like we got the uniqueness constraint in 5.1 itself wrong. Currently, it is (name, userid). It shoud be (name, appid, userid) or maybe even just (appid, userid). We cannot fix it for this release but maybe the next since we try to do db changes only in new releases.
