Docker Compose support for Deployments #12
Comments
|
Hey @NeGroRA I'm not sure I fully understand your question. Could you provide more details about the issue you're facing? Are you referring to copying and pasting a Docker Compose configuration, or something else? Any additional context would be helpful. Thanks! |
|
just like in colify with its own docker compose |
|
and what is this about |
Currently, Docker Compose uploads are not supported because QuickStack is built on Kubernetes (k3s) rather than Docker (like Coolify) which makes Docker Compose deployments a bit more difficult. If you'd like, I can tag this issue as an enhancement and look into potential support for this in the future. |
|
Okey |
The current setup script prints allot of debug information. In the future the script will be more "clean" so it doesn't prints that much "unnecessary" information. Since the script sets up nfs-common, Kubernetes, Longhorn, and Cert-Manager, it needs to wait for the necessary pods to start after each installation step. This is why you see messages indicating that the script is waiting for all required components/pods to come online. |
|
and for example how do I add port 80 to 8006 |
|
@biersoeckli this is how to add docker compose |
To make your app accessible from the internet, you need a domain. First, configure your domain to point to the server’s IP address where QuickStack is running. Then, in the “Domains” tab of your app, specify which port of your container should be routed to the domain. We’ve created a video demonstrating the deployment of a sample app: https://youtu.be/koqGZ2ChHvw?si=wrvTHkteS_UM3fiA Currently, direct mapping of a container port to a host port is not supported. For example map container port 80 to servers port 8080. |
I have a question because there is a problem with uploading docker manually Will there be such a possibility that in life not my own I mean copy and paste and not just image
The text was updated successfully, but these errors were encountered: