Unlock superior Git workflows with Gitness. Experience seamless code reviews, robust CI/CD solutions, and up to 4x faster pipeline execution. Begin your journey in just 30 seconds.
Yeh, docker is sweet. Docker compose is even better.
It's great when you start dockerising things yourself, and stuff just works.
A note, tho. Docker is a brand name. Open Container Initiative (or OCI) is the open source equivalent. Its mostly compatible (IE compatible until you get into the weeds). A lot of the tooling, you can just alias docker for whatever the tool is and it's the same.
You really gotta try it to get it. You can read about the benefits all day but u til you have the aha moment it won't be the same. So let me give an example. Some tools use some scripting languages you haven't set up and you have to sit there and figure out how to get some build tool working you've never used for some language you e never used just to get some tool to do something that might fit your needs. But they also have a docker container. Do you can just docker run blah and zero set up.
Docker for example is used on the Kbin project. They've created a docker image that gets PHP, Posgres and all the other services needed to get up and running with the project.
Without that image you'd have to manually get everything up and running and while I'm sure some people are comfortable jumping into a new project, having a single image that does most of the legwork means you can attract developers who just want to get started right now.
This is super handy for UI/UX/Designers/concept focused people who need to get the project running locally quickly.
like
I haven't seen why to use docker until recently. It is easy and fast to run non trivial setup quickly on any Linux distribution or WSL.
Yeh, docker is sweet. Docker compose is even better.
It's great when you start dockerising things yourself, and stuff just works.
A note, tho. Docker is a brand name. Open Container Initiative (or OCI) is the open source equivalent. Its mostly compatible (IE compatible until you get into the weeds). A lot of the tooling, you can just alias docker for whatever the tool is and it's the same.
You really gotta try it to get it. You can read about the benefits all day but u til you have the aha moment it won't be the same. So let me give an example. Some tools use some scripting languages you haven't set up and you have to sit there and figure out how to get some build tool working you've never used for some language you e never used just to get some tool to do something that might fit your needs. But they also have a docker container. Do you can just docker run blah and zero set up.
I had similar thoughts in Docker, started using it for my media server, haven't looked back since. It's so efficient and simple, absolutely love it.
Docker for example is used on the Kbin project. They've created a docker image that gets PHP, Posgres and all the other services needed to get up and running with the project.
Without that image you'd have to manually get everything up and running and while I'm sure some people are comfortable jumping into a new project, having a single image that does most of the legwork means you can attract developers who just want to get started right now.
This is super handy for UI/UX/Designers/concept focused people who need to get the project running locally quickly.