In this episode we’ll look at one way to install Elixir. asdf together with Docker containers makes switching between projects using different tech stacks virtually seamless.In episode #64 we looked at my editor setup for ElixirCasts, but if we don’t have Elixir installed we wont get very far. I even avoided updates out of the fear of breaking something in my other projects. Before I’ve started using this approach, I’ve wasted dozens of hours resolving dependencies hell. I hope that the above tips will help you simplify your local development setup.
Presence of this file does not mean that everyone from your team must start using asdf.tool-versions file checked into the repository can work as a single source of truth on which versions should be used, regardless of how you do it. There are dozens of asdf plugins available for different programming languages and command line tools. tool-versions file in your home directory. After entering a folder with this file, all the executables will be switched to their specified versions. Here’s a sample config file for one of my Rails projects: ruby 2.7.3
You can install it by running: git clone ~/.asdf -branch v0.8.1Īfter installing asdf, you have to add plugins for executables that you want to use: asdf plugin-add ruby Īnd run asdf install to install dependencies specified in. I’ve been using various version managers, i.e., RVM, NVM, rbenv… Recently, I’ve discovered “the one to rule them all”, namely asdf.Īsdf lets you specify executable versions using a simple config file.
#ASDF NODEJS HOW TO#
Let’s now discuss how to work with different versions of executable dependencies like Ruby or NodeJS. This is the eBook that I wish existed when I was first tasked with moving the Heroku database to AWS as a developer with limited dev ops experience. A good practice is to keep only a in a version control, so that every developer can decide on the setup of his local environment. I usually don’t keep the docker-compose.yml file in the repository. You can check out the repository for implementation details. Each PG version is running on a different port. I use it to run the test suit of my rails-pg-extras library against PostgreSQL versions 11, 12, and 13 in a single command. Both Redis and PostgreSQL are exposed on their standard ports. To stop the processes, you have to run docker compose stop. A new PostgreSQL database will be created during the initial launch based on the configuration from the. To spin up your stack run docker compose up command. I’m not a proponent of dockerizing the apps for local development because it causes a cumbersome indirection.Īs you can see, we can fine-tune the exact versions of our dependencies and their ports. Notice that we don’t dockerize the Rails app itself, only the dependencies. ports : - ' 5432:5432' volumes : - project1_pg_data:/var/lib/postgresql/data redis : image : redis:6.2.5-alpine ports : - ' 6379:6379' volumes : project1_pg_data : POSTGRES_USER =project1_postgresĭocker-compose.yml services : postgres : image : postgres:12.2-alpine env_file :. Let’s see a sample configuration for PostgreSQL and Redis, a standard Ruby on Rails setup: With so-called Docker Compose you can describe your stack in an easy to understand yml file. Docker containers for local dependenciesĭocker let’s you run the processes for each of your dependencies in a separate container. Let’s discuss how we can improve this setup. But the mismatch can result in an unexpected downtime if some obscure feature is incompatible between releases. I understand that it’s not always easy to match the minor release of PostgreSQL or Redis ideally. While conducting my Rails performance audits, I sometimes see projects not paying attention to the consistency of their local and production dependency versions.
#ASDF NODEJS UPDATE#
I’ve finally decided to ditch using Homebrew for managing development dependencies after the update of the Vim package somehow bumped my local PostgreSQL major version… It resulted in cumbersome data restoration and a couple of wasted hours. Also, specifying a granular minor version is not straightforward. One critical issue of this approach is that it does not permit the installation of different versions at the same time. Many tutorials recommend it as a quick & easy way to install packages on MacOS. What are the dangers of using globally installed dependencies?īefore, I’ve used Homebrew to manage my local dependencies, e.g., PostgreSQL database. In this blog post, I describe how you can manage your local development stacks using Docker containers and asdf. Have you ever updated a database for one project just to discover that you accidentally broke another? Ensuring the isolation between your local dependencies can save you hours of rolling back a breaking update or resolving intertwined dependencies. A leading-edge performance and error monitoring tool for Ruby applications.
0 kommentar(er)
