It should build using the dockerfile in the 'cli' directory
not hugely important
checking
at a glance it looks fine, dockerhub just flashes when I press "trigger" and nothing happens.
I'd declare this an issue with dockerhub
yeah, probably something about being in the subdir to do the build
but I don't know
it isn't worth a lot of investigation, I can easily just push a new version as needed
and really no one is likely to run it from docker other than me
I'll want automatic builds on the other (rosetta) but we will need to split out the docker files. The rosetta spec calls for doing it in a somewhat odd way, they want the dockerfile to pull the git source rather than just using what is in the current repo.
So we can make one that does exactly what they are asking for
and one that uses current repo and have that set to build on push
only on main branch?
Yeah
@Fireduck subdirectories are pretty normal, I believe dockerhub is just bugging out.
alright, I looked again, javascript console reports `errorMessage: "Branch 'master' not found"`
oh, it is main or something
and, apparently it's been named "main"
because master is racist
I vote for keeping with convention in this case. :P
I'll go rename anything that says "slave" to "comerade-worker"
the convention has changed. :wink:
wait really
yeah, github new default is main
Alright, so I renamed the output docker tag to "dev", because "latest" would interfere with pointing to latest tags being built. So, the latest commit would be "dev", and latest release would be "1.2.3" sound reasonable?
and if there are multiple types, perhaps /cli/ should be cli-dev and cli-1.2.3 ?
triggers build
so the cli will be in snowblossom/rosetta-cli
the other docker image goes in snowlbossom/rosetta
if that's the convention they/you want, sure.
if cli is just a specific sub component of the repo, I personally generally prefer: `snowblossom/rosetta:cli-1.2.3` I think. but I'm a newb.
heh, renaming that to your convention.
yeah, they are completely different things that do different things
the tag name (after the colon) is for different versions of the same concept
at least that is how I see people using it
I know this is just bikeshedding, but I view the repo as just being "the software" and the tag being a version or specific offshoot of it.
I see what you are saying
but the docker user doesn't care where it comes from
so in my mind it is org/function:version
version being latest or stable or version numbers
@Fireduck well, do you want a specific output? My default is: rosetta-cli:dev for latest commit and rosetta-cli:1.2.3 for tags? or do you want to configure it?
that sounds perfect
Also, I personally try to make sure latest typically points to latest release, for user friendliness. Typically I don't expect :dev to always be working. I need to read up on how `latest` tag is used though. I think it automatically points to the last pushed tag?
dunno what triggered that one, but okay. :shrug:
Ha