Working with Ionic sometimes means to handle different versions of Ionic\/Cordova and Ionic\/Cordova Plugins. My goal was, to setup an Ionic environment specify for each project. And I want do activate the environments automatically.<\/p>\n\n\n\n
I started with autoenv<\/a>, but unfortunately there is no unload\/deactivate mechanism. So, finally, i switched to direnv<\/a>. But i also tried different solutions with Vagrant or Docker.<\/p>\n\n\n\n You will need a package manager to install the different software packages. There are a variety of package manager for the different platforms. <\/p>\n\n\n\n For macOS, i will use Homebrew<\/a>.<\/p>\n\n\n\n Mostly, i try to group files in different directories, depending on their functionality.<\/p>\n\n\n\n Environment files goes to a directory .env<\/span>. But, wait: there could be more environments (node.js, ruby, python), which all could be used in my project.<\/p>\n\n\n\n So, i decide to use subfolders for each possible environment. Here it looks like:<\/p>\n\n\n\n Suppose, you have this directory structure<\/p>\n\n\n\n If you walk<\/em> between this different rooms, you will see how direnv<\/span> follow you<\/p>\n\n\n\n There is a detailed installation instruction here<\/a>, but for macOS, here is the simple step<\/p>\n\n\n\n Finally, check if installation has succeed<\/p>\n\n\n\n Directory specific configuration is made through the file .envrc<\/span>. It’s like a normal Shell profile script, so mostly all commands are allowed and possible.<\/p>\n\n\n\n Entering the directory triggers this configuration file, so a normal cd<\/span> into the directory does the environment setup.. pretty cool<\/strong>!<\/p>\n\n\n\n In my simple example<\/a>, i used this configuration files<\/p>\n\n\n\n Ionic heavily depends on node.js<\/a> So, the challenge is to setup different node.js environments. Luckily, there is already a solution for that: Node Version Manager nvm<\/a>.<\/p>\n\n\n\nRequirements<\/h2>\n\n\n\n
Things about my directory structure<\/h2>\n\n\n\n
$ tree myproject\nmyproject\n\u2514\u2500\u2500 .env\n \u251c\u2500\u2500 nvm\n \u251c\u2500\u2500 pyenv\n \u2514\u2500\u2500 ruby<\/pre>\n\n\n\n
<\/a>Some small example<\/h2>\n\n\n\n
.\n\u251c\u2500\u2500 home\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 .envrc\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 bath\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 .envrc\n\u2514\u2500\u2500 office\n \u2514\u2500\u2500 .envrc<\/pre>\n\n\n\n
~\/tmp$ cd home\ndirenv: loading .envrc\nYou are at home\n~\/tmp\/home$ cd bath\ndirenv: loading .envrc\nYou are in the bath\n~\/tmp\/home\/bath$ cd ..\ndirenv: loading .envrc\nYou are at home\n~\/tmp\/home$ cd ..\ndirenv: unloading\n~\/tmp$ cd office\ndirenv: loading .envrc\nYou are at work\n~\/tmp\/office$ cd ..\/home\/bath\ndirenv: loading .envrc\nYou are in the bath\n~\/tmp\/home\/bath$<\/pre>\n\n\n\n
Installation<\/h2>\n\n\n\n
$ brew install direnv\n==> Downloading https:\/\/homebrew.bintray.com\/bottles\/direnv-2.14.0.high_sierra.bottle.tar.gz\nAlready downloaded: \/home\/user\/Library\/Caches\/Homebrew\/direnv-2.14.0.high_sierra.bottle.tar.gz\n==> Pouring direnv-2.14.0.high_sierra.bottle.tar.gz\n \/usr\/local\/Cellar\/direnv\/2.14.0: 8 files, 3.7MB\n<\/pre>\n\n\n\n
$ direnv version\n2.14.0<\/pre>\n\n\n\n
Configuration<\/h2>\n\n\n\n
~\/tmp$ find . -name .envrc\n.\/home\/.envrc\n.\/home\/bath\/.envrc\n.\/office\/.envrc\n~\/tmp$ find . -name .envrc -exec cat {} \\;\necho \"You are at home\"\necho \"You are in the bath\"\necho \"You are at work\"<\/pre>\n\n\n\nSetting up a sample project<\/h1>\n\n\n\n
Install nvm<\/h2>\n\n\n\n