Many web apps need access to libraries via language-specific package
npm, and so on.
Supported by the platform stack
If you are using a "platform stack" that has built-in support for
downloading dependencies, like the Meteor stack or the Python stack,
then you can expect
vagrant-spk to handle downloading and installing
these dependencies for you. Specifically:
uwsgistack creates a virtualenv in the
envdirectory within the app's code directory (
/opt/app/envinside Vagrant) and, if a
requirements.txtis present, does `pip install -r requirements.txt' into the virtualenv.
meteorstack uses the
meteor buildprocess to create a Meteor bundle.
lemp(PHP) stack looks for
composer.jsonin the app directory and, if present, downloads and runs
composer.pharto download the dependencies listed in
golangstack expects the app directory define the
mainpackage for your program. It will pull in dependencies with
go get. If you need to pull in dependencies versioned with tools other than git, you'll have to modify
.sandstorm/setup.shto install the appropriate version control system. If your app is composed of multiple packages in one repository, you'll have to set
.sandstorm/build.sh; see the comments in that file for details.
Beyond the platform stack
If you need to install extra Debian packages, such as PHP extensions
or headers like
libxml2-dev, you can add commands to your package's
If you are creating your own platform stack, based on the DIY stack,
you will likely also need to customize