hercules 0.1.1 → 0.1.2
Sign up to get free protection for your applications and to get access to all the features.
- data/README.md +14 -3
- data/VERSION +1 -1
- data/hercules.gemspec +1 -1
- data/lib/config.rb +1 -1
- metadata +3 -3
data/README.md
CHANGED
@@ -30,6 +30,16 @@
|
|
30
30
|
Take a look at tests/fixtures/config.yml for a sample configuration file and at tests/fixtures/deployer_true.rb for a sample deployer script.
|
31
31
|
*Very important:* Hercules does not work with bundler 0.9.
|
32
32
|
|
33
|
+
### Installing the service hook in your github project
|
34
|
+
It is necessary to notify hercules whenever changes are made to your project's repository. So we need to setup some service hooks in the github admin interface (which you can access using the "admin" button in your github project page).
|
35
|
+
In your project's github admin interface, go to "service hooks" -> Post-Receive URLs.
|
36
|
+
Then you put the URL that will call hercules in the blank textbox and click "Update Settings".
|
37
|
+
Your URL should look like:
|
38
|
+
http://yourdomain.tld/github/security_token
|
39
|
+
|
40
|
+
Where github is a constant string, and security token is a string that you will put inside the config.yml.
|
41
|
+
You will need only one service hook for each server you want to deploy to. When you deploy several branches to the same server hercules will diferentiate between them through the information that github sends along with the notification.
|
42
|
+
|
33
43
|
## The deploy hooks
|
34
44
|
The deployer scripts should be inside lib/hercules_triggers.rb
|
35
45
|
Hercules implements two deploy hooks so far: before_deploy and after_deploy.
|
@@ -63,9 +73,10 @@
|
|
63
73
|
|
64
74
|
## The JSON interface
|
65
75
|
You can check the deployment's status of your projects using GET requests.
|
66
|
-
If you access the address where hercules is listening (defaults to 0.0.0.0:
|
76
|
+
If you access the address where hercules is listening (defaults to 0.0.0.0:49456) in a web browser you can ask for a project and get a JSON with the deployment's status.
|
67
77
|
For example, assuming I have the project test_project with the token "abc" using the default configuration I can see its deployment status with:
|
68
78
|
|
69
|
-
curl http://localhost:
|
79
|
+
curl http://localhost:49456/test_project/abc
|
70
80
|
|
71
|
-
|
81
|
+
## The HDI
|
82
|
+
There is a very simple web interface that relies on javascript to parse and present the JSON. The plan is to improve this interface over time. This web interface is unique for each project, you can access our example project's HDI in http://localhost:49456/test_project/abc/hdi
|
data/VERSION
CHANGED
@@ -1 +1 @@
|
|
1
|
-
0.1.
|
1
|
+
0.1.2
|
data/hercules.gemspec
CHANGED
data/lib/config.rb
CHANGED
metadata
CHANGED
@@ -1,13 +1,13 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: hercules
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
hash:
|
4
|
+
hash: 31
|
5
5
|
prerelease: false
|
6
6
|
segments:
|
7
7
|
- 0
|
8
8
|
- 1
|
9
|
-
-
|
10
|
-
version: 0.1.
|
9
|
+
- 2
|
10
|
+
version: 0.1.2
|
11
11
|
platform: ruby
|
12
12
|
authors:
|
13
13
|
- Diogo Biazus
|