Skip to content

Instantly share code, notes, and snippets.

@ramingar
Last active August 29, 2015 14:22
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 ramingar/762e9d46b8305dc1b6d4 to your computer and use it in GitHub Desktop.
Save ramingar/762e9d46b8305dc1b6d4 to your computer and use it in GitHub Desktop.
Getting Started with the EB CLI - Empieza con EB CLI #aws #eb #eb-cli #getting-started

Getting started with the EB CLI

Set up your directory with EB CLI.

eb init -p node.js --profile rafeta

Create the environment dev-env and deploy the sample application.

eb create dev-env

View the sample application.

eb open

To deploy a new application version

eb deploy

Shut down your environment by typing the following:

eb terminate

Remove your application and the local project directory by typing the following:

eb terminate --all

Using Git with EB CLI

git init eb init

To use different Git branches

git checkout master eb use prod git checkout develop eb use dev

To assign Git tags to your application version

git tag -a v1.0 -m "My version 1.0"

EB CLI uses your commit ID and message as the application version label and description, respectively.

git commit

Deploy your updated code.

Now, when you run eb deploy, EB CLI will deploy only the code that was under source control.

NOTA IMPORTANTE

Si cuando lanzas eb open la aplicación devuelve un 502, tienes que hacer esto porque el servidor no ha arrancado la aplicación:

From the EB App Dashboard, go to Eb Configuration -> Software Configuration. Under Container Options -> Node Command add npm start, or node <yourmainfile>.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment