README.md in simple_provision-0.99.5 vs README.md in simple_provision-0.99.6
- old
+ new
@@ -1,14 +1,12 @@
# Introduction
This is based on the work that brandonhilkert initally carried to automate
-EC2 instance provision with YAML and SHELL script. It tries to bring the good spirit: SIMPLE, and JUST WORK to the world of Digital Ocean.
+EC2 instance provision with YAML and SHELL script. It tries to bring the good spirit: SIMPLE, and JUST WORK to the world of every remote machine.
-If you own a Digital Ocean, here is my advice: Chef and Puppet is shitty
-thing that just create more problems than it solves. It will take you
-days even weeks just to get familar and put things in the right order.
-
-With simple_provision, you get your hand dirty in a few minutes and
+I had been banging my head trying to work with Chef and Puppet in the
+past, so this is my attempt to make the provision stuff easier to be
+implemented. With this tool, you get your hand dirty in a few minutes and
we have the working provision profile in just half an hour. From that
moment, provision another instance is just the matter of kicking off
a command from the terminal.
I use simple_provision with mina in my Rails projects and the combination
@@ -17,11 +15,11 @@
Let's rock.
### Recipes repo
Don't forget to also checkout the recipes collection
-https://github.com/phuongnd08/simple_privision_recipes
+https://github.com/phuongnd08/simple_provision_recipes
# How it works
This gem carries the provision by uploading a set of scripts (and
files) to the server and execute there.
@@ -62,11 +60,11 @@
└── search-service.yml
```
So: You put definition of each type of server in `servers/type.yml`.
In `files` and `scripts` folder, you place files and scripts that will be
-uploaded to the Digital Ocean droplet and executed.
+uploaded to the server machine and executed there.
## Installation
Add this line to your application's Gemfile:
@@ -112,11 +110,11 @@
### Passing variables to scripts
Variables defined in `env` will be exposed to scripts during execution.
That way you can use the same scripts for different type of server and
still be able to produce different outcomes.
-## Provision your Digital Ocean server:
-`simpro y-awesome-server --droplet-name YOUR_DROPLET_NAME`
+## Provision your server
+`simpro my-awesome-server root@my-host`
## Contributing
1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)