A lot of this boils down to whether you want a single or multi-process (systemd, supervisord etc.) container...
|* PhantomJS script for importing collection dumps to Parse.com.|
|* Usage: phantomjs --ssl-protocol any import-parse-class.js <configFile> <dumpFile> <collectionName>|
|* - configFile: path of a JSON file with contents:|
|* "email": <Parse user email>,|
|* "password": <Parse user password>,|
|VAGRANTFILE_API_VERSION = "2"|
|Vagrant.configure(VAGRANTFILE_API_VERSION) do |config||
|config.vm.box = "ubuntu-12.04-docker"|
|config.vm.box_url = "https://oss-binaries.phusionpassenger.com/vagrant/boxes/latest/ubuntu-12.04-amd64-vbox.box"|
|# Sets the ip we'll use to access the box|
|config.vm.network :private_network, ip: "10.0.0.10"|
|config.vm.hostname = "myapp"|
Here is a high level overview for what you need to do to get most of an Android environment setup and maintained.
Prerequisites (for Homebrew at a minimum, lots of other tools need these too):
- XCode is installed (via the App Store)
- XCode command line tools are installed (
xcode-select --installwill prompt up a dialog)
ruby -e "$(curl -fsSL https://raw.github.com/Homebrew/homebrew/go/install)"
READ THIS Very Important Update
This entire guide is based on an old version of Homebrew/Node and no longer applies. It was only ever intended to fix a specific error message which has since been fixed. I've kept it here for historical purposes, but it should no longer be used. Homebrew maintainers have fixed things and the options mentioned don't exist and won't work.
I still believe it is better to manually install npm separately since having a generic package manager maintain another package manager is a bad idea, but the instructions below don't explain how to do that.
Fixing npm On Mac OS X for Homebrew Users
Installing node through Homebrew can cause problems with npm for globally installed packages. To fix it quickly, use the solution below. An explanation is also included at the end of this document.