Monk applications use the Dependencies gem to specify which libraries they depend on. It uses a simple text file called
sinatra 0.9.4 haml 2.2.2 # ...
By using version numbers, you make Dependencies look for your libraries using RubyGems.
However, a practice many developers follow is to bundle all the dependencies inside your project. Dependencies makes it easy to do so:
$ dep vendor --all
After that, your dependencies will be extracted to
$ tree vendor -L 1 vendor |-- sinatra-0.9.4 `-- haml-2.2.2
The good thing about this practice is that it allows you to deploy your application more easily by not relying on the environment. Also, it’s easier for the development process, because your project’s dependencies are updated as soon as your code is.
Specifying dependencies from source
Dependencies allows you to specify a URL, rather than a version, so you can live “on the edge”:
# ./dependencies sinatra git://github.com/sinatra/sinatra.git contest (test) git://github.com/citrusbyte/contest.git
If you run
dep vendor sinatra, you’ll be cloning the Git repository directly, rather than using a gem. The resulting directory is also
Checking the dependencies for each environment
dep list in your project root directory to see what dependencies are needed for the current environment. You can also supply the target environment as a second parameter:
dep list test.
Updating a vendored library
In order to update a vendored library, remove the directory in
/vendor, change the version in the
./dependencies file and run
For example, if you have Sinatra 0.9.2 installed and you want to upgrade to Sinatra 0.9.4, you would proceed as follows:
# Change the version in ./dependencies sinatra 0.9.4 # Remove the vendored version. $ rm -rf vendor/sinatra-0.9.2 # Vendor the new version. $ dep vendor sinatra
Read more about dependencies here.