diff --git a/README.md b/README.md index 8aeea85..80a4887 100644 --- a/README.md +++ b/README.md @@ -15,6 +15,16 @@ vagrant up The above will create a local site at [http://ation.local](http://ation.local/) that points to the `www` folder. +## Production + +Using AWS at the moment. You will need to configure `aws` and `ecs-cli` to deploy. After making changes and appspec is good: + +``` +aws deploy push --application-name ation --description "Your description" --ignore-hidden-files --s3-location s3://dmd-ation/Revision.zip --source . +``` + +Then you will have to deploy with CodeDeploy on the console. + ## Development Development started with node v5. diff --git a/appspec.yml b/appspec.yml new file mode 100644 index 0000000..d14c217 --- /dev/null +++ b/appspec.yml @@ -0,0 +1,122 @@ +# This is an appspec.yml template file for use with AWS CodeDeploy. +# The lines in this template starting with the hashtag symbol are +# instructional comments and can be safely left in the file or +# ignored. +# For help completing this file, see the "AppSpec File Reference" in the +# "AWS CodeDeploy User Guide" at +# http://docs.aws.amazon.com/codedeploy/latest/userguide/app-spec-ref.html +version: 1.0 +# Specify "os: linux" if this revision targets Amazon Linux, +# Red Hat Enterprise Linux (RHEL), or Ubuntu Server +# instances. +# Specify "os: windows" if this revision targets Windows Server instances. +# (You cannot specify both "os: linux" and "os: windows".) +os: linux +# os: windows +# During the Install deployment lifecycle event (which occurs between the +# BeforeInstall and AfterInstall events), copy the specified files +# in "source" starting from the root of the revision's file bundle +# to "destination" on the Amazon EC2 instance. +# Specify multiple "source" and "destination" pairs if you want to copy +# from multiple sources or to multiple destinations. +# If you are not copying any files to the Amazon EC2 instance, then remove the +# "files" section altogether. A blank or incomplete "files" section +# may cause associated deployments to fail. +files: + - source: www + destination: /var/www/ation +# For deployments to Amazon Linux, Ubuntu Server, or RHEL instances, +# you can specify a "permissions" +# section here that describes special permissions to apply to the files +# in the "files" section as they are being copied over to +# the Amazon EC2 instance. +# For more information, see the documentation. +# If you are deploying to Windows Server instances, +# then remove the +# "permissions" section altogether. A blank or incomplete "permissions" +# section may cause associated deployments to fail. +permissions: + - object: + pattern: + except: + owner: + group: + mode: + acls: + - + context: + user: + type: + range: + type: + - +# If you are not running any commands on the Amazon EC2 instance, then remove +# the "hooks" section altogether. A blank or incomplete "hooks" section +# may cause associated deployments to fail. +# hooks: +# For each deployment lifecycle event, specify multiple "location" entries +# if you want to run multiple scripts during that event. +# You can specify "timeout" as the number of seconds to wait until failing the deployment +# if the specified scripts do not run within the specified time limit for the +# specified event. For example, 900 seconds is 15 minutes. If not specified, +# the default is 1800 seconds (30 minutes). +# Note that the maximum amount of time that all scripts must finish executing +# for each individual deployment lifecycle event is 3600 seconds (1 hour). +# Otherwise, the deployment will stop and AWS CodeDeploy will consider the deployment +# to have failed to the Amazon EC2 instance. Make sure that the total number of seconds +# that are specified in "timeout" for all scripts in each individual deployment +# lifecycle event does not exceed a combined 3600 seconds (1 hour). +# For deployments to Amazon Linux, Ubuntu Server, or RHEL instances, +# you can specify "runas" in an event to +# run as the specified user. For more information, see the documentation. +# If you are deploying to Windows Server instances, +# remove "runas" altogether. +# If you do not want to run any commands during a particular deployment +# lifecycle event, remove that event declaration altogether. Blank or +# incomplete event declarations may cause associated deployments to fail. +# During the ApplicationStop deployment lifecycle event, run the commands +# in the script specified in "location" starting from the root of the +# revision's file bundle. + # ApplicationStop: + # - location: + # timeout: + # runas: + # - location: + # timeout: + # runas: +# During the BeforeInstall deployment lifecycle event, run the commands +# in the script specified in "location". + # BeforeInstall: + # - location: + # timeout: + # runas: + # - location: + # timeout: + # runas: +# During the AfterInstall deployment lifecycle event, run the commands +# in the script specified in "location". + # AfterInstall: + # - location: + # timeout: + # runas: + # - location: + # timeout: + # runas: +# During the ApplicationInstall deployment lifecycle event, run the commands +# in the script specified in "location". + # ApplicationStart: + # - location: + # timeout: + # runas: + # - location: + # timeout: + # runas: +# During the ValidateService deployment lifecycle event, run the commands +# in the script specified in "location". + # ValidateService: + # - location: + # timeout: + # runas: + # - location: + # timeout: + # runas: \ No newline at end of file diff --git a/docker-compose-prod.yml b/docker-compose-prod.yml index ed44225..caccd0e 100644 --- a/docker-compose-prod.yml +++ b/docker-compose-prod.yml @@ -1,5 +1,6 @@ wordpress: - extends: - file: docker-compose.yml - service: wordpress - env_file: env/production.env \ No newline at end of file + env_file: env/production.env + image: wordpress:4.5-apache + cpu_shares: 10 + ports: + - 80:80 \ No newline at end of file