search

elmsln / spawn

A distribution for helping managing multiple drupal, distribution, elmsln and other package deployments in EC2
GNU General Public License v2.0
2 stars 0 forks source link

Construct Scripts Structure #6

Open bradallenfisher opened 8 years ago

bradallenfisher commented 8 years ago

Basically we need to start organizing scripts to run application specific routines. For now and possibly forever, we will create an AMI to be used as our baseline.

It shall be named SPAWN.

It will have all the common repeatable packages that we currently spin up on each install routine. Since we are assuming a certain level of responsibility for items like php, apache, mysql, patch, git, wget, etc... it doesn't make sense to run those every time we spin up an instance.

1 liners will be kicked off after the initialization of the IAM user and the EC2 system is in place. These 1 liners should be organized into application specific zones.

For instance:

One thing to note is that SPAWN can be run from anywhere. Essentially if you can install a Drupal site you can install SPAWN.

bradallenfisher commented 8 years ago

For reference on the concept see http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMIs.html#creating-an-ami