-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mailcow alternatives / mailcow-kubernettes / mailcow-terraform #5037
Comments
There’s still ongoing support for mailcow from tinc side. I’m open for a discussion on this topic somewhere else, if possible. :) Not as a drop-in replacement for mailcow, but, as mentioned, a more lightweight and modern alternative with other features etc. This tracker is not the right place, that’s not fair. |
I don't see anything unfair in an honest discussion around open source software. This is the eternal argument - nobody owns open source or should be able to control how it is used and what is discussed imho I do see a conflict of interests if @andryyy would have started this thread, but as this is not the case, I take all the blame which is what? Freedom of speech? :) Companies who open source software deliberately give away control over its fate. |
I can understand your fear, however ´mailcow-dockerized´ is a well-established open-source project with many different developers and an awesome community involved. Ofcourse it hurts, when the founder of the project is leaving. But the development will definitely go on. And as @andryyy already stated, there is still ongoing support and development from tinc. |
So one question to clarify: can we talk about |
Whats the progress on this mailcow-k8s is very very overdue |
Summary
With the development of the tech such as managed kubernetes.io (GKE/EKE etc) and terraform.io it is now very easy to implement the docker-compose part of the mailcow as a set of terraform modules.
Do we actually need a single database or is it enough to be able to manage all the configuration as a set of configuration files under revision control system (i.e. private repo in github) and have terraform manage all the bits?
We would still have the UI of the sidekars, like SOGO, rspamd, solr but perhaps some simple ui similar to mailcow can be built or used (parts of mailcow or modoboa)
If there is interest - apexive.com can help sponsor the development.
Do we have terraform engineers here?
Motivation
As it seems there might a risk of lack of ongoing support as it seems from #1485 perhaps it is a good idea to be ready to think about alternatives?
Additional context
There is another alternative https://github.com/modoboa/modoboa
The text was updated successfully, but these errors were encountered: