Created
June 27, 2016 08:58
-
-
Save OpakAlex/2e12a48dd6d80a7455835312b8fec087 to your computer and use it in GitHub Desktop.
This file contains hidden or 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
1. Run the bootstrap script | |
This script will install the following: | |
Homebrew with XCode Command Line Tools | |
Homebrew Cask | |
Ansible | |
Docker | |
Docker Machine | |
Docker Compose | |
and will create: | |
A Docker Machine VM | |
Lines in your /etc/hosts file (you may have to clear out old ones manually) | |
Lines in your shell profile | |
It should run idempotently, meaning you should be able to run it as many times as you want and it won't hurt anything. If it fails due to a temporary condition (like network issues), running it again should pick up where it left off. If new items are added to the script, running it against a functioning environment should only add the new things. | |
git clone [email protected]:IFTTT/dev-env | |
cd dev-env | |
bin/bootstrap | |
# Once all steps are complete, delete this initial checkout of dev-env. | |
2. Start Shared Services | |
dev shared up | |
3. Code Checkout (Skip if migrating from previous version) | |
# Make a directory where you plan to keep all of your repositories (e.g. ~/ifttt) | |
mkdir -p ~/ifttt | |
cd ~/ifttt && git clone [email protected]:IFTTT/ifttt_front_end | |
4. Pull Docker Images, Build IFE, and Start Servers | |
cd ~/ifttt/ifttt_front_end | |
dev run ifeweb bundle | |
Restart your computer if you stumble across something like this: | |
Cannot start container 0fb27213f6857cdad8b999f667be12cda73ab56fcbbd25e1f1d348b0dc4cee47: [8] System error: exec: "entrypoint": executable file not found in $PATH | |
5. Load a database snapshot | |
dev run ifeweb rake db:create | |
dev run ifeweb rake db:snapshot:load | |
6. Start the server! | |
dev up |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment