tag symlinks

[manuelstofer]

would be nice if regisshtry-push example 0.1.0 created a symlink example:0.1.0 -> example.5

[maxkueng]

Yeah but I think it would be better if it would use docker-style tagging like example:0.0.1. I think most users would intuitively use it like that.

[manuelstofer]

Good input. I updated the issue

[maxkueng]

I actually meant regisshtry-push example:0.1.0

[manuelstofer]

Im actually not a big fan of including the tags in the image name. Seems like a workaround for not really supporting tags to me. But I guess we should do it to stay as close as possible to the docker interface.

Personally i would prefer following interface regisshtry-push example 0.0.1 staging. this would also allow to push multiple tags at once. In this case one for the version and one for deploying it into staging.

[manuelstofer]

Maybe we could support docker tags on the first argument, but just for identifying the image on the docker host.

regisshtry-push example:0.1.0 would mean: push local image example:0.1.0 as remote image example without tags

[manuelstofer]

Hmm, actually lets forget about tags. They are exported anyway with the tarball. Its probably better to just keep it simple so we can manage it with bash scripts.

[manuelstofer]

So regisshtry-push example:0.1.0 would just push 0.0.1 to example without creating any symlinks. an import should restore anyway all tags that were on the image. The only thing we would need to do is to drop the :0.0.1 on the remote path