Ad
AWS Elastic Beanstalk : How To Change Node Command ? Container Options Removed In Recent Update?
I had deployed a node.js application on Elastic Beanstalk recently and it gave me container options so that I could change the command to be run on startup.
But in the recent update I suppose they've removed this option, now how do I configure my on-startup command?
Ad
Answer
AWS has changed the process recently. Now you have to upload a Procfile with all your application files. The same approach exists in Heroku as well.
The content of Procfile should be:
web: node index.js (i.e specify the node command to be run for your application)
Official Documentation : https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_nodejs.container.html
Ad
source: stackoverflow.com
Related Questions
- → How to update data attribute on Ajax complete
- → October CMS - Radio Button Ajax Click Twice in a Row Causes Content to disappear
- → Octobercms Component Unique id (Twig & Javascript)
- → Passing a JS var from AJAX response to Twig
- → Laravel {!! Form::open() !!} doesn't work within AngularJS
- → DropzoneJS & Laravel - Output form validation errors
- → Import statement and Babel
- → Uncaught TypeError: Cannot read property '__SECRET_DOM_DO_NOT_USE_OR_YOU_WILL_BE_FIRED' of undefined
- → React-router: Passing props to children
- → ListView.DataSource looping data for React Native
- → Can't test submit handler in React component
- → React + Flux - How to avoid global variable
- → Webpack, React & Babel, not rendering DOM
Ad