docs/TASKS.md in negroku-2.6.0 vs docs/TASKS.md in negroku-2.7.0

@@ -2,25 +2,26 @@
 
 * [Rails](#rails)
     * [Remote Console](#remote-console)
 * [Whenever](#whenever)
     * [Config](#config)
+* [Logs](#logs)
 
-### Rails 
+### Rails
 
 ##### Remote Console
 
-Negroku adds support to remotelly connect to the rails console integrating de [capistrano-rails-console][1] gem. 
+Negroku adds support to remotelly connect to the rails console integrating de [capistrano-rails-console][1] gem.
 
 ```shell
 cap <stage> rails:console
 cap <stage> rails:console sandbox=1
 ```
 
 [1]: https://github.com/ydkn/capistrano-rails-console
 
-### Whenever 
+### Whenever
 
 **Note:** By default we are not adding any path to the cron execution PATH. It's up the you to add the needed path to the PATH variable in the cron file.
 
 ##### Config
 You can change some defaults adding this variables to your `deploy.rb`
@@ -30,5 +31,65 @@
 
     ```ruby
     set :whenever_template, "bash -lc ':job'" #default
     set :whenever_template, "PATH=./bin:$PATH && bash -lc ':job'" #add location to the path
     ```
+
+### Logs
+
+You can stream al the application logs from the server.
+
+```shell
+# to get all application logs
+cap production logs
+
+# to get all nginx logs
+cap production logs:nginx
+
+# to get the nginx access or error logs only
+cap production logs:nginx:access
+cap production logs:nginx:error
+```
+
+You can pass an argument with the number of line to show in the beginning
+
+```shell
+# to get the nginx access logs starting with 1000 lines
+cap production logs:nginx:access[1000]
+```
+
+The build in supported log tasks are
+
+
+- `logs:nginx:access`
+- `logs:nginx:error`
+- `logs:delayed_job:out`
+- `logs:eye:app`
+- `logs:puma:error`
+- `logs:puma:access`
+- `logs:rails:app`
+- `logs:sphinx:out`
+- `logs:sphinx:query`
+- `logs:unicorn:error`
+- `logs:unicorn:out`
+- `logs:whenever:out`
+
+> The will be loaded based on what module you loaded in your `Capfile`
+
+#### Custom Logs
+
+If you have other logs in your applicacion you can add them to the log task
+using the `define_logs` method in your `deploy.rb` file
+
+This assume that your logs are in the `shared/logs` folder
+
+```ruby
+define_logs(:other_process, {
+  error: 'other_process_error.log',
+  out: 'other_process_out.log'
+})
+```
+
+With that you will have a new `other_process` task
+
+- `logs:other_process:error`
+- `logs:other_process:out`