-
Notifications
You must be signed in to change notification settings - Fork 110
Setup Walkthrough
Evan You edited this page Nov 27, 2013
·
10 revisions
$ npm install -g pod
You will be prompted to choose a place for pod to settle down. If the target directory does not exist, you can let pod create it for you:
The following happens on your local dev machine.
- Make sure your app's main file is
app.js
. If it's using a different name, you can either edit the config file on the server (~/.podrc
) or specify it in the app'spackage.json
's "main" field. - The path to the bare repo was listed in the output of last step.
- I've setup my VPS to be aliased "do" in my
~/.ssh/config
here, you can either do that or use raw username@ip format.
$ git remote add deploy ssh://do/srv/stuff/repos/myapp.git
... skipping all the npm install
remote messages...
Tada! The app is running!
You might notice there's a "fatal: bad default revision HEAD" error, but that's fine because the post-receive hook tries to determine the last commit of the remote repo in case things go wrong so pod can revert the working copy to it. Since this is the first push, the repo is still empty, hence that error. Just ignore it.
That's it! You may also want to find out how to setup an app using a GitHub repo.