Improve commands passed to Docker Compose

[jaydrogers]

Feedback received from @ijpatricio:

3rd time I've been to starting an Issue in Spin, but it's very hard to start it, following the entire template, when I'm with so many things on my plate. In the picture, the service "coolify" should have been "php" for the defaults. I think there should be a way to run those as default, with minimal keystrokes.

also, something like proxies:

"spin artisan X" would run X inside "php" service
"spin ps" is not available... so anything not matching the known commands should forward to docker compose, no?

[jaydrogers]

Thanks for the feedback @ijpatricio! I'm very grateful for you sharing your perspective. Here are a few more questions I have to help improve the experience:

it's very hard to start it

Can you elaborate more what you mean by this? Do you mean it is confusing to get started?

In the picture, the service "coolify" should have been "php" for the defaults. I think there should be a way to run those as default, with minimal keystrokes.
"spin artisan X" would run X inside "php" service

We could potentially assume that php is a service name and shortcut a few things. I want to keep this as framework agnostic as possible. I am thinking of possibly allowing people to have custom aliases in their config files.

"spin ps" is not available

This is a good one to get added 👍

so anything not matching the known commands should forward to docker compose, no?

I don't have it fully passing everything, just a few things. I wonder if it is safe to open that up to make it easier. I could potentially "intercept" the command for things like run and up (so I can automatically pull the docker images), but then pass everything else directly to Docker compose. Let me stew on that 😃

You can see what I have here:

spin/bin/spin

Lines 280 to 324 in 9fc6cdd

	# Check that an argument is passed
	if [ $# -gt 0 ]; then
	# Check the first argument and pass the user to proper action, Only some actions need arguments passed.
	case $1 in
	build)
	action_build "$@"
	;;
	debug)
	action_debug "$@"
	;;
	down)
	action_down "$@"
	;;
	exec)
	action_exec "$@"
	;;
	help)
	action_help
	;;
	kill)
	action_kill
	;;
	logs)
	action_logs "$@"
	;;
	new)
	action_new "$@"
	;;
	run)
	action_run "$@"
	;;
	up)
	action_up "$@"
	;;
	update)
	action_update
	;;
	version)
	action_version
	;;
	*)
	echo "\"$1\" is not a valid command. Below are the commands available."
	action_help
	;;
	esac