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.
-
@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.
-
@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.
-
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)?
-
-
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.
