Created
January 15, 2015 17:53
-
-
Save leto/265f7840db7543ed54c9 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Skip to content | |
This repository | |
Explore | |
Gist | |
Blog | |
Help | |
Duke Leto leto | |
2 | |
0 | |
0 | |
illustratedsound/api private | |
api/README.md | |
Duke Leto leto 2 days ago | |
Update README.md | |
1 contributor | |
43 lines (21 sloc) 1.113 kb | |
Internal Illustrated Sound Network API | |
Hacking on stuff | |
You will need at least Vagrant 1.7 for the following. | |
Bringing up a local VM: | |
vagrant up local | |
You will be able to see the site at http://isn.virtual | |
To bring up our dev machine | |
vagrant up dev --provider=digital_ocean | |
and for production: | |
vagrant up prod --provider=digital_ocean | |
If you are only changing Javascript, CSS or HTML, no vagrant stuff is needed. Just refresh your browser and do what ye will. Changes to Python code (in the api) will require a vagrant VM to either be re-provisioned or destroyed and recreated, after doing a git pull. It depends. | |
To re-provision your local VM: | |
vagrant provision local | |
To start from scratch (the -f prevents it from asking you, be careful!) | |
vagrant destroy -f && vagrant up | |
Deploying | |
To deploy new code changes to a server, use "vagrant push": | |
vagrant push | |
You will need to have the correct SSH keys for the above to work. | |
How Deployment Sausage is Made | |
Vagrant push uses scp to copy all the files in the web and api repos to the remote server. That is it. | |
Status | |
API | |
Training | |
Shop | |
Blog | |
About | |
© 2015 GitHub, Inc. | |
Terms | |
Privacy | |
Security | |
Contact | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment