search

antosubash / blog-comments

MIT License
0 stars 0 forks source link

posts/netcore-microservice-with-abp-docker-and-ci-cd-part-10 #26

Open utterances-bot opened 1 year ago

utterances-bot commented 1 year ago

Docker and CI/CD

In this post we will see how to add docker support and create a CI/CD with github actions

https://blog.antosubash.com/posts/netcore-microservice-with-abp-docker-and-ci-cd-part-10

sturlath commented 1 year ago

I would really like to see you do an article of combining this article with https://blog.antosubash.com/posts/automatic-version-and-release .

After going over all your blog posts I think there is a "all in one post" post missing for the CI/CD scenario.

I am now going to try to deploy my Blazor Server/single-layer/none-tiered/Postgress db/container to Azure Container Apps and would like to see a complete setup for dev/prod using containers and proper versioning using all the good stuff you have mentioned.

Keep on the great work! I love your posts! They add so much to the abp.io experience!

sturlath commented 1 year ago

@antosubash I created a docker-build-deploy.yml gist https://gist.github.com/sturlath/d51df80d8daf38aa343c9208fdd0b402 that I would love to have enhanced with Versionize and Husky and any other best practise you have.

I tried to do it but had lots of issues and was not sure what would be the best way to incorporate those two into this my docker-build-deploy.yml.

Like what should be the way to push to production? Is that just through a commit tag? But what if somebody does that by accident? There were quite few other issues I had (that I now cant remember) so I left it has is.

You are btw 100% free to use my yml if you want to do with as you please.

antosubash commented 1 year ago

@sturlath I agree "all in one post" for CI/CD is missing. Thanks for pointing it out. I will write one soon.

Regarding the prod deployment and migration. I usually do that manually. I will lock the main branch and allow only PR on that branch and manually create the PR. This will trigger the prod deployment.

For dev, I used automatic deployment along with migration.

Maybe the PR creation can be automated. but someone has to merge it manually to trigger the deployment to prod.