[GH-ISSUE #1146] What can we learn and implement from the Docker strategy of other webmail project? #583

New issue

Open

opened 2026-02-25 21:35:25 +03:00 by kerem · 3 comments

kerem commented

2026-02-25 21:35:25 +03:00

Owner

Originally created by @marclaporte on GitHub (Aug 4, 2024).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/1146

We made a gigantic step forward with: https://github.com/cypht-org/cypht-docker/issues/31 and we now have https://hub.docker.com/r/cypht/cypht

Now, as a lower priority, let's review what others are doing to get some good ideas :-)

Originally created by @marclaporte on GitHub (Aug 4, 2024). Original GitHub issue: https://github.com/cypht-org/cypht/issues/1146 We made a gigantic step forward with: https://github.com/cypht-org/cypht-docker/issues/31 and we now have https://hub.docker.com/r/cypht/cypht Now, as a lower priority, let's review what others are doing to get some good ideas :-) - https://github.com/the-djmaze/snappymail/blob/master/docker-compose.yml - https://github.com/the-djmaze/snappymail/pull/965 - https://hub.docker.com/r/roundcube/roundcubemail/

kerem added the

strategic

docker

labels

2026-02-25 21:35:25 +03:00

kerem commented

2026-02-25 21:35:26 +03:00

Author

Owner

@jonocodes commented on GitHub (Aug 5, 2024):

Good idea. Here are the things that I think come up here after looking at those repos:

1. ssl/https

Snappy shows the use of self signed certs, presumably in development. I tend to think this is not a good idea. But we can discuss it.
In terms of production deployment, we should definitely tell/recommend that people use ssl. I dont think we should/need to tell them how to do that since there are many ways. That being said we can link to one of our pages that shows one possible way to do it for those who are not familiar. (I thought there was a wiki page here that used caddy or traefik or something.)

2. imprecise version numbering

We can point tags to eachother like:
2 -> 2.1 -> 2.1.3

Such that the user can pull just the major version and not worry about the minor version. This is a bit hacky, but fairly common in docker. I tend to think its not worth the trouble, but we can talk more about it.

3. configurable logging

We should be using env vars to tune logging, as that is common practice in or outside of docker. There has been some discussion around this here:
https://github.com/cypht-org/cypht/issues/1027

@jonocodes commented on GitHub (Aug 5, 2024): Good idea. Here are the things that I think come up here after looking at those repos: # 1. ssl/https Snappy shows the use of self signed certs, presumably in development. I tend to think this is not a good idea. But we can discuss it. In terms of production deployment, we should definitely tell/recommend that people use ssl. I dont think we should/need to tell them how to do that since there are many ways. That being said we can link to one of our pages that shows one possible way to do it for those who are not familiar. (I thought there was a wiki page here that used caddy or traefik or something.) # 2. imprecise version numbering We can point tags to eachother like: 2 -> 2.1 -> 2.1.3 Such that the user can pull just the major version and not worry about the minor version. This is a bit hacky, but fairly common in docker. I tend to think its not worth the trouble, but we can talk more about it. # 3. configurable logging We should be using env vars to tune logging, as that is common practice in or outside of docker. There has been some discussion around this here: https://github.com/cypht-org/cypht/issues/1027

kerem commented

2026-02-25 21:35:26 +03:00

Author

Owner

@marclaporte commented on GitHub (Aug 15, 2024):

@marclaporte commented on GitHub (Aug 15, 2024): Related: https://github.com/cypht-org/cypht/issues/1175

kerem commented

2026-02-25 21:35:26 +03:00

Author

Owner

@marclaporte commented on GitHub (Aug 20, 2024):

@rodriguezny @kroky @josaphatim @Shadow243 @Baraka24