Closed maziyarpanahi closed 5 years ago
@maziyarpanahi
If you're offering to push new Docker versions to DockerHub following tarball releases, then what do you need access to in order to do that?
Hi @samtuke and thanks for your quick reply. For the moment, I would like to know the way you update the Docker Hub just to be on the same page in terms of producing the same stable docker image.
Then, I will try it on my Docker Hub with all the versions. When it's done, you can add me to Docker Hub and allow me to push it directly on phplist
account (or we can make some automation for that)
But for now, I would like to know how you make an image from the latest release so I can go back and reproduce it for at least everything after version 3.x
Again, thanks :)
I have just pushed 3.3.6: https://hub.docker.com/r/phplist/phplist/tags/
You can use the following environment vars to use it:
DB_HOST
DB_USER
DB_PASSWORD
DB_NAME
MAILHOST
The mailhost needs to operate on port 25.
That is great @michield! Thank you. I am available if you need any help now or in future :)
Thanks again!
Thanks @maziyarpanahi please let me know if it works correctly for you and if you need any more environment vars. Also, if you can double check the docs to see if that's all still correct that would be great.
@michield sure I'll do. Thanks again I appreciate it :)
Hi,
We have
phplist
as a docker for small academic newsletter. The process of updating/upgradingphplist
via docker is not mentioned anywhere so I am assuming is straightforward like pulling the latest images?Which brings us to the second issue, how often you guys update
phplist/phplist
on Docker Hub and why does it only have one tag? Having tags with the same version allows us to choose or go back. Besides, it's not possible to know what islatest
when it was updated 2 months ago.As this is an open source project, I am offering help regarding pushing a new version into DockerHub and also make the tags available align with the versions if help is needed :)