Skip to content

Commit 587a6fc

Browse files
committed
Added Readme
1 parent 8e71f0c commit 587a6fc

File tree

1 file changed

+66
-0
lines changed

1 file changed

+66
-0
lines changed

README.md

Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
2+
3+
# Capistrano::Clockwork
4+
5+
Integrate clockwork gem with capistrano
6+
7+
## Installation
8+
9+
Add this line to your application's Gemfile:
10+
11+
gem 'capistrano-clockwork'
12+
13+
or:
14+
15+
gem 'capistrano-clockwork', group: :development
16+
17+
And then execute:
18+
19+
$ bundle
20+
21+
22+
## Usage
23+
```ruby
24+
# Capfile
25+
26+
require 'capistrano/clockwork'
27+
```
28+
Configurable options, shown here with defaults:
29+
By default the gem expects a the clockwork script to be present in the lib folder
30+
31+
```ruby
32+
33+
:clockwork_default_hooks = true
34+
:clockwork_file = "lib/clockwork.rb"
35+
```
36+
To override the defaults just change it in your Capfile
37+
38+
## To Change the clockscript location
39+
```ruby
40+
41+
set :clockwork_file, "clockwork.rb"
42+
```
43+
## To remove the default hooks
44+
45+
By default the clockwork daemon is restarted everytime you deploy to your server
46+
```ruby
47+
48+
:clockwork_default_hooks = false
49+
```
50+
## Other capistrano tasks
51+
By default the clockwork daemon is restarted everytime you deploy to your server
52+
```bash
53+
54+
cap clockwork:restart #=> Restarts your clockwork instance
55+
cap clockwork:stop #=> Stops the clockwork daemon
56+
cap clockwork:status #=> Checks if clockwork daemon is running
57+
cap clockwork:start #=> Starts the clockwork daemon
58+
```
59+
## Contributing
60+
61+
1. Fork it
62+
2. Create your feature branch (`git checkout -b my-new-feature`)
63+
3. Commit your changes (`git commit -am 'Add some feature'`)
64+
4. Push to the branch (`git push origin my-new-feature`)
65+
5. Create new Pull Request
66+
6. Build your gem using the rake command `rake build`

0 commit comments

Comments
 (0)