Multiply instances

[gmarke]

As I already mentioned before in issue created some time ago => with this solution it's possible to run multiply instances of mailcow on one host.

All is about to consider COMPOSE_PROJECT_NAME when selecting data from docker api.

in this commit I made some review and change it in all files where CONTENER_D is assigned.

Please merge this in to project ==> this is not impacting any security or performance part it's just extended select.

[mkuron]

The original pull request, #2755, only dealt with php-fpm and had to be reverted because it resulted in an invalid select statement. Clearly, this pull request needs to be properly tested before merging.

[andryyy]

Yes, we can only merge if it is fully tested. The last PR did not address all problems, just like this does not cover all problems with multiple mailcows on a single host (netfilter for example).

Someone needs to pull and test, I will not try it again, as I don't see an advantage anyway. :(
Is this even safe to use with every compose version?

[mkuron]

Is this even safe to use with every compose version?

Good point. I think the first version that supports config format 2.1 was docker-compose 1.9 from three years ago. We need to test whether that already adds the necessary attributes to the containers.

just like this does not cover all problems with multiple mailcows on a single host

I expect we‘ll get there eventually. If @gmarke really wants to do this, he‘ll need to find and fix the other problems too. But I think it‘s fine if he posts small pull requests like this one that fix issues as he finds them. As long as they don‘t change behavior on regular mailcows.

[andryyy]

Yes, that's true.

When I find more time, I will try to contribute and fix netfilter-mailcow.

[melihsd]

This is working perfectly fine for me;
I tested my already existing systems and did emailing, attachments etc. but not ipv6 yet;
But its working fairly well without any errors.

Hope it will get merged soon and also the ipv6 problem will get solved.

I may setup a test system with 10 installations to see if there will be any problems.

[gmarke]

Cool ProJaCore ;)
Finally someone interested about this solution..
If you describe what is about concerning ipv6 maybe I can do something..

[djdomi]

i am interessted, but more in a solution to create an mailcow cluster on different hosts, because i want to have an active/backup situation without re-creating all accesses/domains on the backup-mx

[mkuron]

@djdomi, high availability is a completely different thing. There is a separate issue for that.

[djdomi]

yup i agree :) but still a feature i look for Am Donnerstag, August 22, 2019 09:07 CEST, schrieb Michael Kuron <[email protected]>:   @djdomi, high availability is a completely different thing. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.  

[andryyy]

Not planned in the open source mailcow. If you want to provide a PR, go ahead.

[djdomi]

Not planned in the open source mailcow. If you want to provide a PR, go ahead.

Hm, maybe theres an idea: You can create a site for export all domains for an import of backup-mx i t hink that would be the easiest way at all?

[patschi]

In general issue #241 might be more related for this kind of feature request.

Hm, maybe theres an idea: You can create a site for export all domains for an import of backup-mx i t hink that would be the easiest way at all?

There's a way to retrieve all domains from a mailcow instance using the API:

mailcow-dockerized/data/web/json_api.php

Lines 228 to 242 in 7483f2e

	case "domain":
	switch ($object) {
	case "all":
	$domains = mailbox('get', 'domains');
	if (!empty($domains)) {
	foreach ($domains as $domain) {
	if ($details = mailbox('get', 'domain_details', $domain)) {
	$data[] = $details;
	}
	else {
	continue;
	}
	}
	process_get_return($data);
	}

So you might be able to script that part yourself.