18 ms·
Oh man, do I love this question. For the stack, Ruby on Rails with React. But my secret sauce is the DevOps: + GitLab + GitLab CI + Heroku + Git + Git tag
by amingilani 8y ago
Oh man, do I love this question.
For the stack, Ruby on Rails with React.
But my secret sauce is the DevOps:
+ GitLab
+ GitLab CI
+ Heroku
+ Git + Git tags
I also add some magic npm scripts to take care of semver tagging. And with my build:
+ All pushes are tested
+ All changes to master are tested and deployed to staging
+ All semver tagged commits are tested and deployed to production
+ Also, all database migrations happen automatically.
I documented my entire process by building and deploying a sample app here: https://www.toptal.com/devops/effective-ci-cd-deployment-pipeline#contract-just-respected-software-architects https://www.toptal.com/devops/effective-ci-cd-deployment-pip...
- ai_ia 8y agoCan you give me a resource to get started with devops. I have only heard these ideas, but don't have any clue why at all they are required.
- rhizome31 8y agoThe idea is to automate repetitive tasks as much as you can because doing them by hand takes time and is error-prone. Build, deployment and testing are tasks that are well suited to automation.
- amingilani 8y agoThis! I started by automating things that would take too long. At first it was taking code from my repository and deploying it to Heroku. Then I discovered that CI services literally gave you servers to run scripts on to interact with your code after a git push, so I started running tests in these servers. Fast forward a few years and I automated everything except writing and maintaining the codebase. I even run linting tests in CI so no badly written code can even make it to code review.