Every time you choose to apply a rule(s), explicitly state the rule(s) in the output. You can abbreviate the rule description to a single word or phrase.
[Brief description ]
- [more description]
- [more description]
- [more description]
Here are the simple steps needed to create a deployment from your local GIT repository to a server based on this in-depth tutorial.
You are developing in a working-copy on your local machine, lets say on the master branch. Most of the time, people would push code to a remote server like github.com or gitlab.com and pull or export it to a production server. Or you use a service like deepl.io to act upon a Web-Hook that's triggered that service.
| #!/bin/bash | |
| # Creator: Phil Cook | |
| # Email: phil@phil-cook.com | |
| # Twitter: @p_cook | |
| brew_prefix=$(brew --prefix | sed 's#/#\\\/#g') | |
| brew_array=("5.6","7.0","7.1","7.2") | |
| php_array=("php@5.6" "php@7.0" "php@7.1" "php@7.2") | |
| valet_support_php_version_array=("php@5.6" "php@7.0" "php@7.1" "php@7.2") | |
| php_installed_array=() |
| #!/bin/bash | |
| # | |
| # steps taken verbatim from: | |
| # http://docs.aws.amazon.com/AmazonECS/latest/developerguide/docker-basics.html#install_docker | |
| # | |
| sudo yum update -y | |
| sudo yum install -y docker | |
| sudo service docker start | |
| sudo usermod -a -G docker ec2-user | |
| # log out and log in to pickup the added group |
#Prerequisites
Copy the ZIP distribution to a directory and unzip it. This is your new FORGE_HOME:
$ export FORGE_HOME=<the location of the extracted build>