@girish Awesome! You guys really know how to set priorities and I love the direction cloudron development is going in! Great job guys!

@girish said in What's coming in 4.5:

Mail fts search - This will be optional since the dovecot+solr integration takes a lot of memory.

Mail fulltext search for dovecot with solr would be awesome. I would love to see solr being integrated in a way that other apps can use it, eg. for implementing a Nextcloud fulltext search.

Getting elasticsearch into Cloudron would be great! Fulltext search for Nextcloud is a must and running a separate instance side by side to cloudron is very inefficient...

@girish said in matrix.org (communication):

@subven Yes, I am not 100% sure if the configuration I have actually works (for federation) but in theory it should. For the well-known, we are looking into adding this to Cloudron itself (probably in the domains view). We can then do mail auto-discovery, mastodon etc.

Heads up for adding the well-known to the root domain! As you said, this would add autoconfig for mail as well which would be great. Not quite sure if this could be added as a configurable feature for Caldav for example, as users could use different Caldav server (Sogo, Nextcloud, etc.)

@girish said in What's coming in 5.1:

First off, I hope all you guys are staying safe in these tough times! Our team is split in Santa Clara and Berlin and we are doing well!

5.1 will be a quick release. There are a bunch of security related fixes but the main feature is the integration of turn addon/service into the platform. This will help us get the video conference apps in asap since it's the need of the hour.

I am very much looking forward to the TURN server integration. Great job, guys! Please also consider updating the Nextcloud package to include the TURN server configuration for Nextcloud Talk if possible.

Next thing on my wishlist for integrated services would be the - admittedly quite heavy performance wise - optional integration of an elasticsearch addon/service to allow for fulltext search in several apps (e.g. Nextcloud, etc.).

I recently did a migration from one VPS to another by simple backup and restore. Great process that went smoother than expected. Just one thing I noticed: sieve filters in email accounts seem to not be backed up or restored.
This might be something that could easily be implemented in a future release.

I‘d be available for testing as well if that helps.

Excellent choice and and a great option to enable Talk by default to allow for auto provisioning of the TURN server setting in the database.
One more separate server (coturn) outside of cloudron I can get rid off!

@girish said in matrix.org (communication):

@subven Yes, I am not 100% sure if the configuration I have actually works (for federation) but in theory it should. For the well-known, we are looking into adding this to Cloudron itself (probably in the domains view). We can then do mail auto-discovery, mastodon etc.

Heads up for adding the well-known to the root domain! As you said, this would add autoconfig for mail as well which would be great. Not quite sure if this could be added as a configurable feature for Caldav for example, as users could use different Caldav server (Sogo, Nextcloud, etc.)

@nebulon said in Email aliases on different domains:

The proposal from @msbt is currently the only supported way, as Cloudron does not support cross domain aliases. Also rainloop is setup in a way that it only works with one domain, the one where it is installed at. To create the server side sieve rules for forwarding, you could also use other mail clients instead of Rainloop, which support sieve. One example is Thunderbird with the sieve plugin.

Would cross domain aliases be something you would consider for future releases? I personally would see this as something very common in business environments.

I‘d be available for testing as well if that helps.

Excellent choice and and a great option to enable Talk by default to allow for auto provisioning of the TURN server setting in the database.
One more separate server (coturn) outside of cloudron I can get rid off!

@girish said in What's coming in 5.1:

First off, I hope all you guys are staying safe in these tough times! Our team is split in Santa Clara and Berlin and we are doing well!

5.1 will be a quick release. There are a bunch of security related fixes but the main feature is the integration of turn addon/service into the platform. This will help us get the video conference apps in asap since it's the need of the hour.

I am very much looking forward to the TURN server integration. Great job, guys! Please also consider updating the Nextcloud package to include the TURN server configuration for Nextcloud Talk if possible.

Next thing on my wishlist for integrated services would be the - admittedly quite heavy performance wise - optional integration of an elasticsearch addon/service to allow for fulltext search in several apps (e.g. Nextcloud, etc.).

@girish Awesome! You guys really know how to set priorities and I love the direction cloudron development is going in! Great job guys!

I recently did a migration from one VPS to another by simple backup and restore. Great process that went smoother than expected. Just one thing I noticed: sieve filters in email accounts seem to not be backed up or restored.
This might be something that could easily be implemented in a future release.

The Heimdall app launcher / dashboard would be a great addition to the build in app luncher for cloudron.

Maybe even a preset provisioning with the cloudron apps could be accomplished.

Packaging the docker image should be fairly easy (I think).

https://heimdall.site/

@girish said in What's coming in 4.5:

Mail fts search - This will be optional since the dovecot+solr integration takes a lot of memory.

Mail fulltext search for dovecot with solr would be awesome. I would love to see solr being integrated in a way that other apps can use it, eg. for implementing a Nextcloud fulltext search.

Getting elasticsearch into Cloudron would be great! Fulltext search for Nextcloud is a must and running a separate instance side by side to cloudron is very inefficient...