I fall into issue 11 as well. Was a bit "frustrated", as I have only a small server, but it is managed in ansible fully.
I get the point of not making a template, as there is a known process of making things.
As I wasnot brave enough to make something on mailcow repo itself I created a small "hack" and replaced the memory limit. There is no failure check yet. Might be woth a deboug output. Anyway, I set up the server using this.
I also added a replacement of the default network mask. As I have another stack running on the server the range was taken. So I needed to make an extra network!
Maybe this helps some one.
I would also create a template for the mailcow config if this is an option?
Hi all,
I fall into issue 11 as well. Was a bit "frustrated", as I have only a small server, but it is managed in ansible fully. I get the point of not making a template, as there is a known process of making things.
As I wasnot brave enough to make something on mailcow repo itself I created a small "hack" and replaced the memory limit. There is no failure check yet. Might be woth a deboug output. Anyway, I set up the server using this.
I also added a replacement of the default network mask. As I have another stack running on the server the range was taken. So I needed to make an extra network!
Maybe this helps some one. I would also create a template for the mailcow config if this is an option?
Cheers!