The process of getting completed feature or bug fix code from the development environment to your web servers is web software deployment. We have b...
For further actions, you may consider blocking this person and/or reporting abuse
We're moving our apps to docker, push them to our private registry and deploy them in a k8s cluster. Our next step is CI/CD, so every merge request will trigger a new docker container build that will be automatically pushed and deployed.
You are heading on the right path. Google container builder is a great tool.
That's exactly what we do but we use the docker-swarm instead of k8s.
Thanks, I regularly go through your post. Normally, this is how we deploy. We setup a jenkins for CI and CD. We add options to choose the branch or Tag to deploy from the Repo and deploy it to selected instance.
How can we add the deployment tools in our pipeline. or in our flow rather than depending completely on jenkins. How will it be if we choose the deployment tools too.
Thanks you
If the current setup works I would say just use it. If you want to add the tools like capistrano or Fabric add it after the tests pass. So then Jenkins just runs the cap or fab command if the tests passed. Thanks!
Use Capistrano with php deployment tools, like Envoyer and you have got a complete server provisioning and setup workflow. You can automatically provision multiple servers through Capistrano and deploy PHP apps on these server automatically on the server through Envoyer.
Right tool for the right jobalways applies. Thank you for the resources Geshan.Thanks for the summary :)
google.com
Good.