Skip to content

Instantly share code, notes, and snippets.

@mpahrens
Last active August 29, 2015 14:24
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save mpahrens/401ee162528b3130a90b to your computer and use it in GitHub Desktop.
Save mpahrens/401ee162528b3130a90b to your computer and use it in GitHub Desktop.
Run for development testing
Here are some TL;DR instructions for running blockytalky
Go into the /blockytalky/ directory
The first time you run blockytalky in dev mode you need to do the following:
- install npm node_modules
- install hex (package manager)
- install mix (task manager / install manager) tasks for phoenix (gives you phoenix.server, phoenix.new, phoenix.digest)
- install project libraries (dependencies)
run `npm list`. If you see ERRs, run `npm install` (on my vm I needed to `sudo npm install` due to shared folder permissions with windows
If you are using the vagrant vm on windows, like me, then you need to `rm -rf node_modules` to get rid of the node_modules folder. then `mkdir ~/node_modules` then `ln -s ~/node_modules node_modules` This will make a symlink to your homedirectory, but put the node_modules in your blockytalky directory. This is because windows filesystems cap the length of the path a directory tree can be. By making it a symlink, we are letting the ubuntu system handle it instead. Then `npm install`.
Run: `mix local.hex`
Run: `mix archive.install https://github.com/phoenixframework/phoenix/releases/download/v0.14.0/phoenix_new-0.14.0.ez`
Run: `mix deps.get`
Again, on windows I needed to sudo these. It might be worth it to fix the project so you do not need to sudo these.
To run in devmode on the vm, run:
`sudo iex -S mix phoenix.server`
To run only the backend code, without the webserver, run:
`sudo iex -S mix`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment