I assume that he means "rather than pushing up each individual container for a project, it could take something like a compose file over a list of underlying containers, and push them all up to the endpoint."

▲

koakuma-chan 4 days ago | parent [-]

Yes, pushing all containers one by one would not be very convenient.

▲

baobun 4 days ago | parent [-]

The right yq|xargs invocation on your compose file should get you to a oneshot.

▲

koakuma-chan 4 days ago | parent [-]

I would prefer docker compose pussh or whatever

	▲	psviderski 4 days ago \| parent \| next [-]
		That's an interesting idea. I don't think you can create a subcommand/plugin for compose but creating a 'docker composepussh' command that parses the compose file and runs 'docker pussh' should be possible. My plan is to integrate Unregistry in Uncloud as the next step to make the build/deploy flow super simple and smooth. Check out Uncloud (link in the original post), it uses Compose as well.
	▲	djfivyvusn 3 days ago \| parent \| prev [-]
		You can wrap docker in a bash function that passes through to `command docker` when it's not a compose pussh command.