2 ms·
Currently I am using Elastic Beanstalk because it means I don't have to worry about machines or scaling. Using the configuration (http://docs.aws.amazon.com/ela
by joshstrange 14y ago
Currently I am using Elastic Beanstalk because it means I don't have to worry about machines or scaling. Using the configuration (http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/customize-containers-ec2.html http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/custom...) files I am able to install any extra packages I need or run commands. After I am more confident that out EC2 config will not change I will create an AMI to launch new instances from so that I don't have to wait for the server to install the packages I need.
I run 2 environments in my app (develop and production) my production branch is master and I work on a "develop" branch and push those changes to EB to test before merging and committing them in the master branch.
- 13rules 14y agoHow are you updating your master branch? Are you just doing a 'git aws.push'? I'm reading that causes a little bit of downtime and AWS' recommendation for zero downtime is to create a new environment and then switch the CNAME to point to the new environment once it is ready... Seems like a little bit of an ordeal for pushing out changes. Thoughts?