"Bridge" between DDEV & setting up projects in coolify? (yaml configs?) #2047
mandrasch
started this conversation in
Feature Requests
Replies: 2 comments 3 replies
-
Hey @mandrasch Any news on this? |
Beta Was this translation helpful? Give feedback.
3 replies
-
Minor typo in title, fixing will help readability. Brige -> Bridge |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey everyone,
I use DDEV for local development of PHP projects.
In each project there is already a
.ddev/config.yaml
file which defines the PHP version as well as database type and version:When I set up a new project / resource in coolify via GitHub, it would be awesome if these values could somehow be used to configure the new resources in coolify? 🪄 🧙♀️
I already saw coolify templates, but they work like 1-click fresh installs - not for adding existing git repository projects if I understood it correctly.
So if anyone has an idea on how to achieve a bridge between DDEV and coolify - please let me know! 🤗
My dream is a workflow like Vercel, but for PHP projects:
.env
file valuesGuess platform.sh works a bit that way with yaml config files (https://docs.platform.sh/add-services.html), but haven't used it yet. Would be awesome to store the coolify project config in git as well to make deployments easier?
(I did various experiments with deploying PHP / CraftCMS projects in the past, e.g. with ploi.io https://dev.to/mandrasch/install-craftcms-via-ploiio-on-hetzner-cloud-including-ddev-57f8 - currently working on a tutorial for coolify 🚀 )
Update: There is a new tutorial with Coolify and Docker Compose ✨ https://samuelreichor.at/blogs/craft-coolify
Thx in advance & cheers,
Matthias
Beta Was this translation helpful? Give feedback.
All reactions