@girish said in Hiding superadmin to deliver 'managed' cloudron to clients.: @micmc said in Hiding superadmin to deliver 'managed' cloudron to clients.: And I guess, that is what would or should happen if we choose to hide the owner. I haven't thought really about this one but yeah, well thought and that should the be case also indeed, the superuser would not be seen in apps as well. We had this idea of creating a "service account" - https://git.cloudron.io/cloudron/box/-/issues/771 (which is scheduled for 7.3). I think this will get you this feature. This is how we see how great minds encounter! Also, there's the discussion about the "email admin" role to which your issue above refers too as well, which several of us have followed as well, which have popped several ideas and views as well and has brought to the creation of such feature.

@girish Yes there is. .ipfs is not a "normal" TLD. It's for websites which are on IPFS, which is an alternate decentralized protocol. Kinda like .onion domains for serving websites on tor. However, i don't really know how cloudron could support it, as I believe it does not use standard http/s at all, so regular apps would not work.

@nebulon woohoo! Thank you

I still really want to be able to filter apps by LDAP support

@fbartels I hear ya, not the main use case, but the subsetting feature with starting a new DB from previous prod data is the killer feature here.

@3246 yes, kind of like a torrent file where you can select priority per file/dir and which ones to skip. not sure a pause is needed, but more like a pre-start selection. I'm sure @staff can enumerate mail and other core services as required items but with flexible priority/order. Not only that, but while we're pondering that manual selection process with manual clicks, the essential bits can already be restored and ready for the next prioritized components.

How much of this will change with Multi-Cloudron?

@d19dotca I'm excited by the potential for https://ntfy.sh. Maybe a cloudron official instance which sets up channels for all customers, so cloudron-generated notifications can be delivered to a customer. Or maybe there's a better way. I just think ntfy.sh is so easy to implement into scripts.

This will be part of 7.2.1

This is now implemented and will be part of the next release.

@d19dotca that is also because Nginx uses FPM and not FastCGI(Apache in some cases can use FPM) for PHP, which give already a good boost. NextCloud and WP could take good advantage of it, and Nginx could help solve the issue of the main image being too "fatty" It's easy to use Nginx in a multi-layer image.

It seems they don't offer SMTP relay as per https://www.mailerlite.com/help/does-mailerlite-offer-smtp-simple-mail-transfer-protocol . Their partner company mailersend has it - https://www.mailersend.com/help/smtp-relay . If you can, please try using mailersend with Cloudron's External SMTP Server option - https://docs.cloudron.io/email/#relay-outbound-mails . If that works well, I can add it to the dropdown (the dropdown is really just a UI template to prefill things).

@d19dotca that's correct. There is no difference between using S3 compat vs Wasabi option since as you guessed they are just templates for pre-filling. Also, when you update, it won't get automatically changed to Wasabi, it will remain as s3 compatible. The change is entirely just UI - https://git.cloudron.io/cloudron/dashboard/-/commit/8dfc142905171160ba41bdb592933bd2dd60748d

There is a much simpler way to keep things in sync in a p2p fashion with GunDB. The trickier part is integrating with the different apps in a way where it can use that data.

@girish said in Mailing feature: add users and groups as members: When added to a list, are you expecting the primary email of the user to be used ? Indeed

This is now fixed for the next version. On upload conflict, the code will add .n to the filepath, whereas n is an increasing number until no conflict is found.

@girish I see, which seems like a fine choice for a single server, however QuestDB is better suited for multi server aggregation and immediate consistency from multiple sources.

@wind-gmbh FWIW, we don't use the upstream distro packages. We use the packages straight from nginx.org since they provide better security fixes - https://nginx.org/packages/ubuntu/pool/nginx/n/nginx/ . Looks like https://nginx.org/packages/ubuntu/pool/nginx/n/ is the pre-built modules they have.

@andreasdueren said in Hide admin user(name)s for mail managers: @girish personally I would enjoy the option to limit the E-Mail manager to the groups they are part of. For example some clients use so little resources like only a website with E-Mail that it doesn’t make sense to give them a dedicated server but instead put a few on the same. Very good points as well, however as @girish says, as this would require to implement shared resources the idea is easier said than done. On the other hand, I personally can't see why it would not make sense to provide dedicated VPS at low cost for its own little resources needs to such client. In when you think about it, any client can grow and in such case the client is already set to scale without any more hassle. Cloudron is not too heavy for a simple basic use as it will adjust its own resources need only for the needs of the installed apps. Now it would be nice if they could configure their own emails without being able to see let alone change the configuration of others. Moreover, as explained previously if you install Cloudron for the client, a 10 bucks per month VPS would be more than perfect for such low needs, as superadmin you keep full control of the instance's management for the client and you give it admin privileges so it can fully manage its mail server. And with the upcoming multiple instances of Cloudron feature that should should become easier to manage from your side as well.