Jono

> [`v2.3.0` (release)](https://github.com/cypht-org/cypht/releases/tag/v2.3.0) was released and now also on DockerHub: [hub.docker.com/r/cypht/cypht/tags](https://hub.docker.com/r/cypht/cypht/tags) Great. Thanks @Shadow243

Yes I think this sounds good. And I agree that having daily fall behind it tests break is the way to go. I would go with this naming scheme as...

> Something else that could be usefull: having special tags pointing to the latest stable version. > > When you have a docker environment (for example using docker-compose), you must...

We should probably take down the sailfrog image eventually but I dont think it has to happen for a while. Once the new image is up in https://hub.docker.com/u/cypht we should...

Also since I have creds now I can publish something right away to cypht/cypht. I'm just not sure what to tag to use. Maybe it will just be a timestamp...

Also also we should probably merge this first: https://github.com/cypht-org/cypht/pull/1001 Preferably someone will 'accept' it before I merge.

> Oh wow! > > * [vsupalov.com/docker-latest-tag](https://vsupalov.com/docker-latest-tag/) Ha yes. I was about to post the same article. Long story short is 'latest' is not well defined and not well understood....

All that being said I have posted to 'latest' while we figure that out: https://hub.docker.com/r/cypht/cypht We can delete that tag if we want, but it will be more clear when...

> > By the way, this maybe would be a good time to do a release? Then we can get a real version number in there. > > Sure! @josaphatim...

> @jonocodes should https://github.com/cypht-org/cypht/pull/1044 be held back? I think it can get merged. Then the first real docker release would be php 8. The docker work will not be hard....