[Bug]: Can't edit Docker Compose Location on a Docker Compose Build Pack project

[DiegoBM]

Description

When trying to add a project from a github repository using the Docker Compose build pack, it won't allow to change the docker compose location field which I need for it to find the file within the repo

Minimal Reproduction (if possible, example repository)

• Setup a brand new server (in my case ubuntu server 24.04 LTS)
• Install docker
• Get Coolify up and running following the instructions in the website
• Setup coolify to install in localhost (no other settings)
• Create a new project
• Add a new resource, of type "Public Repository" and assign it to a server and destination
• Enter the repository URL (in my case https://github.com/supabase/supabase)
• Select "Docker Compose" as Build Pack and click continue
• On the next screen nothing is editable including "Base Directory" or "Docker Compose location" which I need to change for it to find the docker compose file in the repo. It also displays a "504 Gateway Time-out" after a few seconds

Exception or Error

Build data should be editable, in particular Docker Compose Location

Version

v4.0.0-beta.294

[andrasbacsai]

It is reproducible, because the supabase repository is huge and the request times out. I will figure out a better way to do the docker-compose parsing on huge repos.

[DiegoBM]

Maybe you could add a depth setting to github repos, so that they can be cloned with depth 1? That's what they recommend to do in the self hosted supabase guide

[andrasbacsai]

Closing old issue (which is probably fixed already). Reopen if still reproducible.

[muuvmuuv]

Yes I still experience it, I am trying to configure it to docker-compose.stage.yml but it keeps reseting to name without "stage" in it. Therefor reloading fails. Our Stage file just extends the base file and removes/adds variables.
Edit: our version is v4.0.0-beta.454

[jevido]

I'm experiencing it as well on version:
v4.0.0-beta.454

[djedu28]

I'm experiencing it as well on version:
v4.0.0-beta.455

[djedu28]

@andrasbacsai The error still persists.

You can check if it still happens in the current stable version: v4.0.0-beta.460.

If it still happens, it is necessary to reopen the issue.

I'm on version 'v4.0.0-beta.455' and I didn't find any information related to fixing the bug in the update log '+v4.0.0-beta.455 -> v4.0.0-beta.460'

[djedu28]

@andrasbacsai To replicate the BUG.

• Create a new project

• connect to a github repository that has Docker Compose files

• set 'Build Pack *' to 'Docker Compose'
  

• change 'Docker Compose Location' to a name other than '/docker-compose.yaml' (the file needs to exist)
  

• Save the project, and receive pop-up successfully
  

• Refresh the page. Verify that 'Docker Compose Location' has returned to default: '/docker-compose.yaml'

---

I don't know how. But at some point, the edit to '/docker-compose.config.yaml' was successfully performed, I generated the build and success.

However, I can't edit the 'Docker Compose Location' again, for example, to '/docker-compose.yaml'.

output_Configuration_Coolify.mp4.mp4

PS.:

(Before this video, and after successfully build, I deleted the file 'docker-compose.config.yaml' on github, hoping to force coolify to save the new address 'docker-compose.prod.yaml')

When editing Docker Compose Location, and pressing "enter" (or clicking save), it's possible to preview the file's contents. The file's contents ('docker-compose.yaml') persist in the preview when refreshing the page, although the file name 'docker-compose.config.yaml' is displayed.

[Cinzya]

@djedu28 can you provide a link to an example repo that causes this bug for you. Also is this still happening on beta462 as well?