Add docker compose deployment handler

[mew1033]

I'd like to use the SSH deploy method, but deploy an entire docker compose file with potentially multiple containers. I can probably start adding this myself, but I want to ask where this would fit. Would you like an additional option in image:? Potentially something like ssh-compose? Or would you prefer an entirely new deployment handler?
I envision this process as follows:

1. Use subprocess to rsync-over-ssh the entire challenge folder to the remote server. Use the same slugify-d name as the directory name on the remote server.
2. SSH to the remote server and run docker compose up -d in the target directory. Let docker handle all the building/deploying on the remote server.

[pl4nty]

I've been doing something similar with custom deployment handlers in ctfcli plugins, so I don't have to fork ctfcli. This compose to k8s plugin looks for a compose file without needing any extra fields in challenge.yml

[mew1033]

I've been doing something similar with custom deployment handlers in ctfcli plugins, so I don't have to fork ctfcli. This compose to k8s plugin looks for a compose file without needing any extra fields in challenge.yml

Nice! I've made a super simple update to the ssh deployer that rsyncs the entire folder over and runs compose up on the remote host.

Also, I totally snagged your github actions workflow over here: https://github.com/pl4nty/auto-CTFd/blob/main/.github/workflows/challenges.yml for our upcoming CTF. It's awesome, thank you!

[pl4nty]

sweet, I'm glad it's useful! is there anything I could do to improve that repo? might start sharing it later this year, I've run a few CTFs with it and other organisers are starting to use it too