thanks @girish, works now!

@girish Thankyou, will give it a go.

Awesome, I'm glad it's a possibility. It's obviously not a high priority feature, but do you think it could be added to the roadmap at some point?

I didn't thought of any specific LDAP server. It would be great to connect Cloudron to any external LDAP server, that would manage groups and users. For example, connect a Cloudron server to another one so that only one Cloudron server manages the users and groups for both servers.

@nebulon said in Mail domain alias for subdomain:

I guess what you are looking for is a way to match the app internal username (resulting in this email) with some other inbox?

yes, exactly (as long as you refer to the user in nextcloud by internal username).

Sending would not be required, only receiving (which should minimise the setup effort, since only a mx record is needed).

Much thanks to @girish for helping me figure out what was wrong. Sendy (sendy.co) is working well in the LAMP app. Yay! It was simply an issue of changing the
$dbHost = 'localhost';

to

$dbHost = 'mysql';

@fer-raspo Are you using a mail relay by any chance? There is an issue that email forwarding is not working as expected when using a mail relay - https://git.cloudron.io/cloudron/box/issues/593. We are working on a fix. Otherwise, are you able to join our chat at https://chat.cloudron.io and ping me there? (@girish).

@girish Even the "changeme" note might be good enough.

Cool, this is great, thanks! Even if it's not perfectly dynamic this will save me a lot of typing 🙂

@vincitygialam There are probably better forum to discuss this. This forum is for discussing Cloudron related stuff.

@uiharu We have implemented this now in our latest release. Should be out in the coming week or so.

https://cloudron.io/developer/api/#update-user-password is the API

We are working together with Reclaim Hosting and Bates University to create a new edition of Cloudron for this specific use-case. Please contact us at support@cloudron.io for futher information.

@saglagla There are no plans for any kind of multi IP setup at the moment.

I will mark this as solved for now, as the main issue to change the domain appears to be solved.

Hi, there is already an issue for the feature request at https://git.cloudron.io/cloudron/box/issues/283 lets track it there.

Thanks for the heads up about the broken documentation links, we fixed them now.

This is released now.

@girish Hi , I have made sure that that my repo should not have any git data or meta data. I even tried shrinking the app on my end as much as I can. If you want to take a look on the app , here it is : https://github.com/llaske/sugarizer

This is implemented as part of next release.

This feature is now merged to master and will be part of the next release. There is still some amount of testing needed.

If someone has an opinion on which http status code we should be using, please respond here. Currently I have put a 301, but I am not yet sure if this is dynamic enough for our use-case.

Yes that should work fine. Based on the information you gave, I assume each one of your customer has an individual domain, which can be added to your Cloudron and then the corresponding apps installed on subdomains of that. Once a domain is added, the email server and mailboxes can be managed for each domain individually.

This software should be able to do this
http://duplicity.nongnu.org/index.html

Hi @adamlevine ,

are any of these (Zoho and Mautic) installed on Cloudron? I don't see either of these in the app store of cloudron.

That is going to be a bit hard to add at the moment, since the data model for access controls is user and group based and the admin status is just a flag on the user record. This may be possible once we have more fine grained access controls and a real admin group as such.

Nano will be part of the next version of the app base image. However there is no schedule currently when that will be released.

@alexy here it goes:

install an empty lamp app

install piwigo (download from http://piwigo.org/download/dlcounter.php?code=latest)

following this tutorial http://www.jouvinio.net/wiki/index.php/LDAP_Plugin_Piwigo and put https://github.com/kvakanet/ldap_login/archive/config2base.zip as ldap_login in your plugins directory and activate it in the backend

add the following info in the "Ldap Login" settings:

LDAP server host: 172.18.0.1
LDAP port: 3002
BASE DN of LDAP server: ou=users,dc=cloudron
Users Branch: ou=users
LDAP attributes: ou=users,dc=cloudron
Attribute corresponding to the user name: username
Groups Branch: ou=groups,dc=cloudron
Attributes corresponding to the group name: cn
Admins group: users (not working)

In the "New users when LDAP auth is successful" tab check

Should new Piwigo users be created when users authenticate succesfully via LDAP?

Automatic group settings don't work, maybe that's my fault, this means after a user is successfully logged in, you have to manually change his/her group to whichever you want. There's also the mentioning of an OpenLDAP bug on the page, but that's where my french stopped working and I didn't use that code.

Let me know how it goes.