bevacqua/baal

:whale: Automated, autoscaled, zero-downtime, immutable deployments using plain old bash, Packer, nginx, Node.js, and AWS. Made easy.

Nicolás Bevacqua is the Head of UI / UX Engineering at Ramp. As the published author of several JavaScript books (Mastering Modular JavaScript, O'Reilly 2018; Practical Modern JavaScript, O'Reilly 2017; JavaScript Application Design, Manning 2015) and the editor of Pony Foo, Nicolás has experience not only in working on JavaScript problems, but also in sharing his applied learning with others. You can find him on Twitter as @nzgb, and — if you're into cooking — on Instagram as @nbevacqua.

baal's Issues

Error on build - launching source instance: InvalidParameterCombination:

The full error is

==> amazon-ebs: Error launching source instance: InvalidParameterCombination: Non-Windows instances with a virtualization type of 'hvm' are currently not supported for this instance type.
==> amazon-ebs: status code: 400, request id:

Totally unhelpful, since it seems the problem has nothing to do with the instance being a t1.micro

I'm not sure whether it's packer or Amazon taking offense, but I solved this by renaming my templates json extensions to .packer in deploy/templates

¯_(ツ)/¯ - I have no idea why this fixed it

Thanksabunch for this, it's helped me out a ton.

No such process when stoping for the second time

the first time I run sudo service $CMD start and sudo service $CMD stop works fine, the second time I start the service also fine, but the second time I stop the service I got No such process error. This happens because the content of the pid file is different from the actual pid of the running process. I'm lost on how the content of the pid file is different. This can also reproduced by running sudo service $CMD restart multiple times.