-
Notifications
You must be signed in to change notification settings - Fork 184
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
Please provide docker images for clients too #270
Comments
I wanted to add the clients to our docker compose file so it is easier to look at the mails when developing. That would be awesome if they would be provided via docker hub. |
@derTobsch : I'm thinking about a separate GreenMail repo containing GreenMail + clients dockerized combinations. |
@marcelmay what would be the benefit if you would do that instead of keeping it in the same repo? If you separate it you need a job IMHO that updates the other repo after a release so you do not have to do that manually. |
You might want to have a look at this docker-compose file: There are also some examples in the repo: |
Thx alot, @JensKnipper ! Added your article link to the docs and look forward to your PR. Those docker clients were created usually only created for reproducing issues, and are not really maintained. |
Hey @marcelmay, I am not finished yet, but I would like to discuss some things with you guys:
What do you think about that? |
thanks alot for the PR and your input.
In general, I was thinking about moving these client integrations into new repo , eg https://github.com/greenmail-mail-test/greenmail-client-integrations (better name is open for suggestions). To keep the core repo more lean and focused. |
Sounds good :) |
Created https://github.com/greenmail-mail-test/greenmail-client-integrations/ and migrated roundcube/squirrelmail/rainloop. Regarding SquirellMail, if the project is not maintained I think we should mark it as deprecated or drop it. |
Hello,
could you please add automated builds for the greenmail docker client images to docker hub?
Thank you very much,
Michael.
The text was updated successfully, but these errors were encountered: