Installs SciPy according to Scipy Stack 1.0 specification.
- CentOS 6
- Fedora 17, 18, 19
- Red Hat Enterprise Linux 6
- Ubuntu 12.04, 12.10, 13.04
These attributes are under the node['scipy']
namespace.
Attribute | Description | Type | Default |
---|---|---|---|
install_type | "package" or "source" | String | package |
packages | OS packages for installation | Array of Strings | auto-detected (see attributes/default.rb) |
pip_packages | PIP packages for installation in requirements format | Array of Strings | auto-detected (see attributes/default.rb) |
recipe[scipy]
default installation of SciPyrecipe[scipy::package]
Installs SciPy via OS packagesrecipe[scipy::source]
Installs SciPy via source
- Optionally set
node['scipy']['install_type']
- Add
recipe[scipy]
to your node's run list.
For running in a more stable development environment or in production, you may want to hard set the package version installed by pip. To do so, add to or update node['scipy']['pip_packages']
and (if necessary) remove from node['scipy']['packages']
. The pip_packages Array accepts package names in requirements format.
For example on Ubuntu 13.04, which installs pandas 0.10.X via package, let's say we'd like to pip install 0.12.0 instead:
Defaults to:
default['scipy']['packages'] = %w{
ipython
ipython-notebook
python-numpy
python-scipy
python-matplotlib
python-nose
python-pandas
python-sympy
}
default['scipy']['pip_packages'] = %w{}
Let's override pandas installation:
set['scipy']['packages'] = %w{
ipython
ipython-notebook
python-numpy
python-scipy
python-matplotlib
python-nose
python-sympy
}
set['scipy']['pip_packages'] = %w{
pandas==0.12.0
}
Here's how you can quickly get testing or developing against the cookbook thanks to Vagrant and Berkshelf.
git clone git://github.com/bflad/chef-scipy.git
cd chef-scipy
vagrant plugin install vagrant-berkshelf
vagrant plugin install vagrant-cachier
vagrant plugin install vagrant-omnibus
vagrant up BOX # BOX being centos5, centos6, debian7, fedora18, fedora19, fedora20, freebsd9, ubuntu1204, ubuntu1210, ubuntu1304, or ubuntu1310
You can then SSH into the running VM using the vagrant ssh
command.
The VM can easily be stopped and deleted with the vagrant destroy
command. Please see the official Vagrant documentation
for a more in depth explanation of available commands.
Please use standard Github issues/pull requests and if possible, in combination with testing on the Vagrant boxes.
See LICENSE file for more information.
- Author:: Brian Flad (bflad417@gmail.com)
- Copyright:: 2013 Brian Flad