Continuous Integration(CI) and Continuous Deployment(CD) play an essential role, especially when working in a team. In our project, we are following Agile methodology & we do multiple releases during the week. To ensure that the build is generated without any error, CI/CD proves advantageous. "There should be two tasks for a human being to perform to deploy software into a development, test, or production environment: to pick the version and environment and to press the “deploy” button." David Farley For every feature, we create a separate pull request. Every time on commit, CI automatically triggers

Devising ideas to writing code and finally deploying finished products can be quite tedious at times. You need to handle many things beyond just writing the code. But what if you could take some of this work off your shoulders? Well, this is where GitHub Actions really shines. In this article, we will cover how to create a workflow that will trigger the deployment using GitHub Actions into GitHub Pages whenever there is any change(s) found in the master branch of the repository. Lets go through some fundamentals 👨🏻‍💻 Already know these fundamentals? You may then skip directly to action

Nginx is a lightweight, high-performance web server. Passenger used with Nginx gives us many advantages. It automatically serves static assets from the public subdirectory to improve performance. Capistrano is used to automate deployment process to your remote server. Using Capistrano, you can deploy your web application on many servers simultaneously in sequence or as a rolling set. In this article, we will see basic steps that need to be followed to configure your DigitalOcean Ubuntu Droplet. Prerequisites: Ubuntu 16.04 x64 Droplet Working Rails app hosted in a remote git repository that's ready to be deployed Initial setup for the

Recently building few microservices and apps in Elixir and deploying it to heroku, we realised that heroku was not very cost effective for us and also we can't get into every nuts and bolt of how heroku manages our app. As a part of learning things related to deploying to our own server and to save some bucks we decided to look for other options and we decided to experiment deploying one of our app to Digital ocean. One thing we were worried about, was whether we can make deployment as easy as heroku makes it for us. After some

As you know Heroku **does not ** run rake db:migrate automatically. Most of the time we all face this issue of not running migrations on Heroku post deployment. Either we forget or for some reason we miss it. However there are some gems/plugins that help us overcome these issues. Even when we use [heroku auto deployment] [12] feature, there also we need to run rake db:migrate manually and Heroku will not run it automatically for us. That means it is not fully automatic. When I setup heroku auto-deployment I wanted everything to happen automatically, why should I run

While we deploy our changes to heroku, we use deployment scripts or setup yml in CI server. However Heroku has come up with an auto-deployment feature and for that we do not need to use even command line tools. To take advantage of this feature you should use Github/Bitbucket version control system If your Github/Bitbucket repo is setup and you have already pushed your code to Github then you are good to start with heroku I assume that you already have Heroku account and heroku-toolbelt is setup on your system. Now create an app on heroku for your