I choose Netlify because of it's powerful features, such as built in CI/CD and Slack integration without any line of code. With all of my technologies, I almost focus on Frontend, backend should don't take much effort.
I have a similar focus but I'm too lazy to setup netlify and I don't use any of those other CI/CD features because my projects are basically just hobby projects.
Haha my project is personal also. But because I'm lazy, I choose Netlify.
Everytime I push code into my develop branch, Netlify automatically build and deploy for you. That's the basic CI/CD I think we need for every project.
I see. Firebase CLI and GCP is also a good way for modern CI/CD. Everything has its own pros and cons. I have used both and depend on situation, I'll choose the right solution for.
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.
Why bring Netlify into this when you can just use firebase static hosting? You're already using firebase...
I choose Netlify because of it's powerful features, such as built in CI/CD and Slack integration without any line of code. With all of my technologies, I almost focus on Frontend, backend should don't take much effort.
I have a similar focus but I'm too lazy to setup netlify and I don't use any of those other CI/CD features because my projects are basically just hobby projects.
Haha my project is personal also. But because I'm lazy, I choose Netlify.
Everytime I push code into my
developbranch, Netlify automatically build and deploy for you. That's the basic CI/CD I think we need for every project.I disagree. My "CI/CD" is simply running:
yarn build
yarn deploy
Under the hood those map to firebase commands. But this is a thing about which reasonable people can disagree.
I see. Firebase CLI and GCP is also a good way for modern CI/CD. Everything has its own pros and cons. I have used both and depend on situation, I'll choose the right solution for.