I am a professional DevOps Engineer with a demonstrated history of working in the internet industry. I am an avid Linux lover and supporter of the open-source movement philosophy.
Location
Sofia, Bulgaria
Work
Developer Advocate at Materialize | Community Manager at DigitalOcean | Co-Founder at DevDojo
The Docker/DockerCompose is meant mostly for local development, although you can (and we have done) just use it in production as well, but that is not advised.
We are in a closed beta phase testing a tool where you can very, very easily deploy your local Docker Compose setup to a Kool.dev managed Kubernetes cluster. It will be as simple as "kool deploy". Stay tuned and follow us here that we soon will be posting more about it.
Please dont take me wrong, had to ask.
You said:
" you can (and we have done) just use it in production as well, but that is not advised"
Why would you do something on production, business, source of incomes, etc.. if you are not recommending it?
I am really confused.
Why is not advised, what Are the reasons? You are using it. Please help me understand Fabricio
Thanks for asking, indeed it came out a little confusing. Let me clarify:
What is not advised is to use the very same Docker Compose structure we use for local development, to a production deployment. We did that in the beginning for how easy it was... But when we talk about production we need to think about scaling/monitoring/observability/etc...
That is why for production we parse the Docker Compose local env to a Kubernetes namespace, where we are more provisioned and prepared to keep good care of production grade containers.
So Docker Compose is great for running a set of containers together, which helps a lot development of container based applications. But when we talk production, we will use those very same containers, but in a different orchestrator, to help us with the requirements of a production deployment.
And just to add to it - Kool CLI will help you all the way for local development in multiple languages/microservices/frameworks...
To move all that to production, we are cooking what we call Kool Cloud for helping making any Docker Compose based local environment deployable to a Kubernetes cluster. That is the coming soon/stay tuned part of my initial answer all about.
Laravel Sail is indeed great, we do have some differences so i would love if you could try and give us your feedback, we also support different stacks (frameworks, languages) with the very same UX.
As Fabricio said, we are also working on a premium feature called Kool Cloud but we plan to have proper documentation on how to use Kool on production with Docker, which is done but not documented yet.
If you're interested in learning more about it, please join our slack at kool.dev/slack and we can help you get started.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is pretty cool. Does it work for production or is it manly for local development?
I've been using official Laravel Sail package which does a similar thing for local environments and it's been very good.
The Docker/DockerCompose is meant mostly for local development, although you can (and we have done) just use it in production as well, but that is not advised.
We are in a closed beta phase testing a tool where you can very, very easily deploy your local Docker Compose setup to a Kool.dev managed Kubernetes cluster. It will be as simple as "kool deploy". Stay tuned and follow us here that we soon will be posting more about it.
Please dont take me wrong, had to ask.
You said:
" you can (and we have done) just use it in production as well, but that is not advised"
Why would you do something on production, business, source of incomes, etc.. if you are not recommending it?
I am really confused.
Why is not advised, what Are the reasons? You are using it. Please help me understand Fabricio
Thanks for asking, indeed it came out a little confusing. Let me clarify:
What is not advised is to use the very same Docker Compose structure we use for local development, to a production deployment. We did that in the beginning for how easy it was... But when we talk about production we need to think about scaling/monitoring/observability/etc...
That is why for production we parse the Docker Compose local env to a Kubernetes namespace, where we are more provisioned and prepared to keep good care of production grade containers.
So Docker Compose is great for running a set of containers together, which helps a lot development of container based applications. But when we talk production, we will use those very same containers, but in a different orchestrator, to help us with the requirements of a production deployment.
And just to add to it - Kool CLI will help you all the way for local development in multiple languages/microservices/frameworks...
To move all that to production, we are cooking what we call Kool Cloud for helping making any Docker Compose based local environment deployable to a Kubernetes cluster. That is the coming soon/stay tuned part of my initial answer all about.
Laravel Sail is indeed great, we do have some differences so i would love if you could try and give us your feedback, we also support different stacks (frameworks, languages) with the very same UX.
We already support / use kool images in production, if you take a look at our image: github.com/kool-dev/docker-php
As Fabricio said, we are also working on a premium feature called Kool Cloud but we plan to have proper documentation on how to use Kool on production with Docker, which is done but not documented yet.
If you're interested in learning more about it, please join our slack at kool.dev/slack and we can help you get started.