![]() ![]() You should change that to your application’s real name throughout the examples. Finally, the application used in this article is named “docker_example”. Once you’ve gained an understanding of Docker terminology and tools then come back here to learn how to make your existing Rails application multi-container and production deployable. If you’ve never worked with Docker then I suggest you begin by following the excellent getting started guide and browsing the docs. ![]() There are tons of articles written on that subject. The article assumes you’re comfortable with Rails, Docker, Docker Compose, and the command line. Note to the readerįor your convenience, all of the code in this article is available online at GitHub. This article will discuss how to make that happen, and is the first of three I plan to write on spinning up Docker-based development for a CI to CD pipeline. I wanted an optimal setup that allows me to work with Rails the way that I’m used to as well as deliver on the promise of containerization. Docker delivers on all these hopes, but with so many different ways to use Docker it’s hard to craft a good setup. I also wanted to simplify server configuration and maintenance, plus make it super easy for another person to jump on the project. ![]() The hope is that this style of development would eliminate the differences in environment you typically find between work laptops running OS X and staging, testing, and production servers running Linux. I wanted a container-based development environment that fed into a continuous integration to continuous deployment pipeline. A few weeks ago I decided to take an existing Ruby on Rails application and configure it to work with Docker. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |