Question about Coolify in CI/CD Workflows

[llPekoll]

Hello guys,

I Didn't had much luck with this post on discord :/, let's try here.

I would like to improve my Coolify setup so, I am curious a about others way of integrating Coolify into CI/CD processes. Specifically, I'm considering these approaches:

Using Coolify's direct repository auto-deploy feature
Setting up GitHub Actions to build and push images to a Docker registry, with Coolify monitoring for registry updates
Alternative approaches I might not have considered

What methods have you found most effective? Thanks for sharing your experiences!
1️⃣ Direct auto-deploy from repository
2️⃣ GitHub Actions with Docker registry
3️⃣ Other methods

Please react below, and share you config! 👇

[Smurrlawa]

Hi,
I don't have a good setup for this right now but I was also experimenting with the Github Actions in combination with Coolify.
My Insights:

• I think it only makes sense to do this if you really "need" CI for tests e.g. Otherwise it makes sense to use the normal autodeploy and build feature directly connected with Github as it is way easier and less complex
• I was hosting my Github Runner also on Coolify by Dockerizing the Self-Hosted Runner itself, this will cause some problems (e.g. docker in docker, if you need to build anything with docker inside the Actions it currently fails) but I really like the approach to also manage my runners with Coolify.

Generally spoken is this propably the best approach with the deploy from docker registry.

If you want to do self hosted Github Runners: The guide I used