Where did the docker-compose.yml go?

[joh-klein]

I just tried to update to the new v6 (thanks for that btw!) and it failed – (just an error in my own docker-compose). But when I tried to ssh into the server and edit the docker compose myself I couldn't find it anymore.
Before, when I logged into the server, I was in a directory with my build output from github. Now the directory is empty (except for the unzipped db-cache-folder). Nothing there. Not even the docker-compose.yml.
I thought it had something todo with the failed build – but after I fixed the problems on my side the folder on the lightsail instance is still empty. Still no docker-compose.yml …

Is that by design? If so, can I change it?

[crohr]

Well yes the new version "simplifies" rollouts by not relying on the sync'ing of the entire app folder, but using the docker context feature to deploy an environment on a remote server, from the github action. Note that a missing follow-up is to release a pullpreview CLI that allows you to replicate what the github actions is doing, but locally, for easy troubleshooting. It's just missing the release workflow but I'll get to it soon.

[joh-klein]

Thanks for the quick reply. I really liked logging into the instance and troubleshooting the docker-compose "live". I'm not sure if a local cli can replace that. But I'm willing to give it a try

[joh-klein]

What do you think about adding a "debug" flag that replicates the old behavior? Because sometimes it is hard to locally replicate the state that is at the end of the GitHub pipeline (before the pullpreview action starts) – either because you don't have the same exact OS or you don't have the access to github.secrets that get baked in etc