[10:09:01]
<ChriChri> Do I need to care about
```
Warnung: Die Konfigurationsdatei '/var/www/.well-known/<any domain I configured>/autoconfig/mail/config-v1.1.xml' wurde manuell bearbeitet und wird nicht aktualisiert
```
saying something like that the files had been changed manually. But I didn't (on my Debian all files edited are automatically checeked into a revision control system which does not know about editing these files).
[10:18:14]
<ChriChri> BTW: Are there setups around in which the directory is shared by more than one server? E.g. running ressource hungry stuff on its own hardware?
[10:18:37]
<Aleks (he/him/il/lui)> nope
[10:19:04]
<ChriChri> But it would be likely possible by configuring synchronization between the two resulting slapd, right?
[10:19:25]
<Aleks (he/him/il/lui)> there's a lot of stuff that are theoretically possible with computers
[10:19:34]
<ChriChri> Well, domains shouldn't be synchronized, because they'd differ by the different systems...
[10:20:19]
<ChriChri> > <@Alekswag:matrix.org> there's a lot of stuff that are theoretically possible with computers
and the foundation layed by yunohost.a
[10:21:13]
<ChriChri> It seems I'm just finishing of the migration of users and aliases belonging to single users from my old mail server to my yunohost. 🥳
[10:22:30]
<ChriChri> > <@chrichri:librem.one> It seems I'm just finishing of the migration of users and aliases belonging to single users from my old mail server to my yunohost. 🥳
Meanwhile I installed a yunohost test vm to get more into ldap and its permissions. Any good read about slapd and ldap one could recommend?
[10:36:53]
<ChriChri> Uhm, thinking about it... Would be a dream to be able to form 'clusters' that are spread around a group of people sharing accounts and each offering one or two different services on their homes internet connection. The group could share a domain and spread the subdomains over multiple homes. Would be somehow like eduroam that works using radius....
[10:38:13]
<Aleks (he/him/il/lui)> yup, that's not the YunoHost project, YunoHost's scope is already big enough
[11:28:34]
<ChriChri> > <@Alekswag:matrix.org> yup, that's not the YunoHost project, YunoHost's scope is already big enough
Yupp, I already had the feeling that there are too many 'users' and two little admins and devs working on the project. I hope I can get to the point where I an start contributing, too. But in the end - from my experience - the project needs financing to have people work on it paid. Is yunohost already funded somehow in a way that it could pay e.g. your work? Only the foundation without the apps already seems so huge...
[11:37:42]
<Aleks (he/him/il/lui)> we had some grant in the past, and we still do have some donation, but there's like one order of magnitude between what we got / are getting and what would be a "normal" salary for all the development time
[11:38:00]
<Aleks (he/him/il/lui)> like if we sum up all the volunteers contribution in a year and convert this into time, and then into salary, you probably get somewhere around 300k, 500k, idk
[11:39:52]
<Aleks (he/him/il/lui)> and that's mostly just to "keep things going", major debian migrations, bugfixes, necessary refactorings, app maintenance, etc ..., so if you add to this new R&D stuff like "oh yeah we should be able to make clusters of yunohost" etc, add another order of magnitude to that i guess
[11:50:52]
<ChriChri> I do not think that every volunteer can be and should be paid. The main developers who organize the stuff, keep it somehow consistent and lay the foundation should be a good beginning. Volunteers are important and could have some hope to grow into the system that far that they might work one day paid.
The mixture works - at least for e.g. Purism. They pay developers and nevertheless there are people contributing.
Do you have a "donation app", yet? Without thinking much:
* it should be installed by default (though there is the freedom to uninstall it without consequences)
* it should remind users to donate
* it could offer ways to donate
* it could grow into ideas...
¹ crazy idea: have a crowdfounding system for issues to solve.
[11:50:58]
<Aleks (he/him/il/lui)> we have https://donate.yunohost.org/ and have various pointers to it accross the project, but the bottom line is, imho, you won't get enough for a full-time salary with just donations
[11:51:53]
<ChriChri> > <@Alekswag:matrix.org> and that's mostly just to "keep things going", major debian migrations, bugfixes, necessary refactorings, app maintenance, etc ..., so if you add to this new R&D stuff like "oh yeah we should be able to make clusters of yunohost" etc, add another order of magnitude to that i guess
Forget about the clusters. That could as well be a howto. People who can manage that in their group should be able to set it up on the foundation of what exists... It just has been dreaming ;-)...
[11:52:57]
<Aleks (he/him/il/lui)> yes sure you can have "bounties" for fixes / features, but that system doesn't magically get done, there are a gazillions technical question related to payment that starts happening, and then you have to manage the bounties etc, and all of this is extra work to somehow hopefully get people paid (not saying it shouldnt be done, but it's just a classic supposedly silver-bullet and the reality is not that magical)
[11:55:03]
<Aleks (he/him/il/lui)> and "bounties" usually don't cover all the boring maintenance that nobody even thinks exists in the first place yet there are people doing it, so "bounties" are clearly different from "an actual salary"
[11:55:27]
<Aleks (he/him/il/lui)> anyway, it's a big complex topic, my initial point was "it's out of YunoHost's scope"
[11:56:00]
<ChriChri> > <@Alekswag:matrix.org> yes sure you can have "bounties" for fixes / features, but that system doesn't magically get done, there are a gazillions technical question related to payment that starts happening, and then you have to manage the bounties etc, and all of this is extra work to somehow hopefully get people paid (not saying it shouldnt be done, but it's just a classic supposedly silver-bullet and the reality is not that magical)
True and therefor a very simple app just reminding and showing a sepa would be a good start. Keep it in Europe first using the most obvious, simple and widespread paying mechanism.
[11:56:22]
<ChriChri> > <@Alekswag:matrix.org> anyway, it's a big complex topic, my initial point was "it's out of YunoHost's scope"
I agree(d) 😇 ❗
[12:33:07]
<gerald> Hello!
I tried to install yunohost following instractions for a remote server on a x86machine without display:
https://yunohost.org/de/install/hardware:vps_debian
but unable to find out where to download a debian 11 image.
I can only find debian 12.
[12:33:40]
<Aleks (he/him/il/lui)> yeah debian 11 images are probably kind of hidden, let me have a quick look
[12:34:24]
<Aleks (he/him/il/lui)> i'm a bit confused what you mean by "image" tho ... do you mean install ISO ? 'cause you seem to mention a VPS install ...
[12:35:49]
<gerald> I want to install via usb stick on an apu2 boards (pcengines) . as I can not connect a display the instructions for a regular pc does not work. https://yunohost.org/de/install/hardware:regular
[12:36:41]
<gerald> so yes, an install iso would be fine
[12:37:45]
<Aleks (he/him/il/lui)> https://www.debian.org/releases/bullseye/debian-installer/index
[12:38:15]
<Aleks (he/him/il/lui)> i guess the "netiso" (first thing) is fine assuming your machine has internet connectivity
[12:38:54]
<Aleks (he/him/il/lui)> netinst*
[12:42:55]
<gerald> Thank you very much! I think now I know how to continue.
[15:10:33]
<ChriChri> Is there something better than `postfix -bv` to check mailrouting? I'd especially be grateful if the routing information would just be printed to the terminal instead being mailed.
[16:05:19]
<anmol> Hi everyone!!
[16:06:37]
<anmol> I have an situation. I have two Yuno servers and want to merge one into the other. Is there a simple way achieve this?
[16:07:38]
<anmol> The main problem is with the Nextcloud and Mails. Where is the mail alias kept for the users?
[16:08:33]
<tituspijean> I think you can do a system backup of one, and restore it onto the other. Be wary of conflicting usernames, aliases, and apps, though.
[16:12:07]
<anmol> @tituspijean So, if I have same user on first server to me migrated to main server. Should I delete the user on the main server so that there is no conflict?
[16:17:29]
<Aleks (he/him/il/lui)> that's one way to do it, but "merging things" is just not a trivial problem, nobody can know if you want to keep only version A, or only version B, or a mix of the two (and even then "a mix" is ill-defined)
[17:20:29]
<ChriChri> > <anmol> The main problem is with the Nextcloud and Mails. Where is the mail alias kept for the users?
Mail aliases are kept in the users ldap entry. You can look at it using phpldapadmin which is available as an app.
You can export a list of users using `yunohost user export` into csv. The aliases are contained in that list. That list could also be imported on another yunohst using `yunohost user import`, **but be aware**:
* existing users are just ignored while imported
* using the `-u` update option will probably not add the aliases to the existing ones, but overwrite the old ones (please correct me if I'm wrong on this).
* **don't use the `-d` _delete_ option** unless you really know what your doing (I deleted my users once, there is no question to confirm this)
I'm just moving from my old mail system to a yunohost and did some work and research for importing my setup into yunohost. Feel free to ask.
[17:22:24]
<anmol> @Aleks So how are the email alias managed, I have played around with alias before but I am not able to recall it. Probably I will create users on A and rsync mails from B. Manually configure domains and other apps.
[17:27:44]
<anmol> @ChriChri How to get the .csv?
[17:30:00]
<ChriChri> User are able to add or delete aliases in their profiles. Admins can do the same in the account page of each user. These aliases are 1-to-1 aliases - it's not possible to route a mail to alias@your.do.main to two different recipients. Neither is it possible to prohibit users from registering any alias that is not used elsewhere (at least not by the admin interface as far as I could find out).
[17:30:20]
<ChriChri> > <anmol> @ChriChri How to get the .csv?
`yunohost user export` on the command line
[17:31:20]
<anmol> ok and how do import these to the new server? I would have to do it one by one Manually ?
[17:32:31]
<ChriChri> A user with its aliases looks like this in ldap:
```
dn: uid=example,ou=users,dc=yunohost,dc=org
cn: Just Me
displayname: Just Me
gidnumber: 64058
givenname: Just
homedirectory: /home/example
loginshell: /bin/bash
mail: example@do.main
mail: example_alias@do.main
mail: another_example_alias@do.main
maildrop: example
mailuserquota: 0
objectclass: mailAccount
objectclass: inetOrgPerson
objectclass: posixAccount
objectclass: userPermissionYnh
permission: cn=mail.main,ou=permission,dc=yunohost,dc=org
sn: Me
uid: example
uidnumber: 64058
```
[17:37:03]
<ChriChri> The first attribute `mail:` cannot be changed by the user. All the following ones can be managed by the user itself (is what I experienced when importing).
**Important** might be my experience that importing the csv field `mail-alias` via `yunohost user import` possibly mixes the order of the `mail:` ldap entries. I ended up with users having any alias as their primary email and their ment to be primary (not by them changeable) email in some alias.
I worked around it by first importing all users without any alias and then adding all the aliases by `yunohost user update <user> --add-mailalias <alias>`. That worked for me.
[17:51:21]
<anmol> @ChriChri: I got the hint, Thanks.
[18:04:46]
<ChriChri> > <@chrichri:librem.one> Do I need to care about
> ```
> Warnung: Die Konfigurationsdatei '/var/www/.well-known/<any domain I configured>/autoconfig/mail/config-v1.1.xml' wurde manuell bearbeitet und wird nicht aktualisiert
> ```
> saying something like that the files had been changed manually. But I didn't (on my Debian all files edited are automatically checeked into a revision control system which does not know about editing these files).
Do I have to care?
[18:07:04]
<Aleks (he/him/il/lui)> not really, just force-regen the conf
[20:22:11]
<phinero> My bad... After:
**about:config**
**network.dns.echconfig.enabled TRUE**
**network.dns.use\_https\_rr\_as\_altsvc TRUE**
and FFox restart it works and got some sites (torrents etc.) unlocked without any VPN services.