Light

bevacqua / baal Goto Github PK

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

Home Page: https://ponyfoo.com

License: MIT License

Nginx 4.65% Shell 95.35%

baal's Introduction

baal: build. automate. autoscale. launch.

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

Read about this deployment strategy on Pony Foo, and then clone this repository. Copy the scripts, and adjust as needed. A few pointers.

The application is named baal in a few places. Change that to your application's name
You need to set a value for HOSTED_ZONE in the setup script. Read the articles on Pony Foo to learn about that
In the deploy script you can set PRIMAL_ID to an AMI so that your base AMI isn't rebuilt on every deploy
By default, baal expects to build your static assets with npm run build-$NODE_ENV

reading

Relevant Pony Foo articles:

requirements

You'll need to install all of the following.

pip install awscli
aws configure
brew install jq
npm install underscore-cli --save-dev

license

MIT

baal's People

Contributors

Stargazers

Watchers

Forkers

modulexcite yeshodhan xrzhao

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.

Recommend Projects

React

A declarative, efficient, and flexible JavaScript library for building user interfaces.
Vue.js

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
TensorFlow

An Open Source Machine Learning Framework for Everyone
Django

The Web framework for perfectionists with deadlines.
Laravel

A PHP framework for web artisans
D3

Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

javascript

JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
web

Some thing interesting about web. New door for the world.
server

A server is a program made to process requests and deliver data to clients.
Machine learning

Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Visualization

Some thing interesting about visualization, use data art
Game

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft

Open source projects and samples from Microsoft.
Google

Google ❤️ Open Source for everyone.
Alibaba

Alibaba Open Source for everyone
D3

Data-Driven Documents codes.
Tencent

China tencent open source team.