How do I run server and rest of docker-compose separately?

[SashvDave]

⚠️ Check for existing issues before proceeding. ⚠️

• [X] I have searched the existing issues, and there is no existing issue for my problem

Where are you using SuperCoder?

MacOS

Which branch of SuperCoder are you using?

Main

Which area covers your issue best?

Installation and setup

Describe your issue.

Hey, I want to be able to make changes to the go backend without having to re-run docker compose to see them. How would I go about doing so? or, is there something wrong on my end and this already works?

How to replicate your Issue?

No response

Upload Error Log Content

n/a

[luciferlinx101]

You can build just the server using docker compose up -d --no-deps --build server this is will not let you build everything again.

[SashvDave]

So for running the rest of the project, I just the regular docker compose up and it should just ignore the server start because the containers already running?

Also with this cmd, do I still need to restart every time I make a chance or will it auto-refresh?

On Mon, Jul 29, 2024 at 9:34 PM Abhijeet @.***> wrote:

You can build just the server using docker compose up -d --no-deps --build server this is will let you build everything again.

— Reply to this email directly, view it on GitHub https://github.com/TransformerOptimus/SuperCoder/issues/104#issuecomment-2257442734, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANK5A35Z6GGJSTTV5IMLLADZO4JVVAVCNFSM6AAAAABLVPCBN2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJXGQ2DENZTGQ . You are receiving this because you authored the thread.Message ID: @.***>

[czezi]

@SashvDave

Start the project by running the following command

docker compose up -d --build

Once you make any changes in the backend code, please use the following command for the changes to reflect in the server container.

docker compose up -d --no-deps --build server

[czezi]

Closing this issue as it's mostly on how you run docker, and answer should suffice.