Skip to content
This repository
Browse code

Merge branch 'master' of github.com:cantino/huginn

  • Loading branch information...
commit 6dd1fa58a3a48f3e1cfb563c49ec1ac5b61af70b 2 parents 4df8685 + 9b87532
Andrew Cantino authored

Showing 1 changed file with 9 additions and 9 deletions. Show diff stats Hide diff stats

  1. +9 9 README.md
18 README.md
Source Rendered
@@ -2,17 +2,17 @@
2 2
3 3 ## What is Huginn?
4 4
5   -Huginn is a system for building agents that perform automated tasks for you online. They can read the web, watch for events, and take actions on your behalf. Huginn's Agents create and consume events, propogating events along a directed event flow graph. Think of it as Yahoo! Pipes plus ITTT, on your own server. You always know who has your data. You do.
  5 +Huginn is a system for building agents that perform automated tasks for you online. They can read the web, watch for events, and take actions on your behalf. Huginn's Agents create and consume events, propagating events along a directed event flow graph. Think of it as Yahoo! Pipes plus IFTTT on your own server. You always know who has your data. You do.
6 6
7 7 ![the origin of the name](doc/imgs/the-name.png)
8 8
9   -#### We're just getting started, but here are some of the things that you can do right now with Huginn:
  9 +#### This is just getting started, but here are some of the things that you can do right now with Huginn:
10 10
11 11 * Watch for air travel deals
12 12 * List terms you care about and receive emails when their occurrence on Twitter changes drastically
13 13 * Track the weather and get an email when it's going to rain (or snow) tomorrow
14 14 * Follow your project names on Twitter and get updates when people mention them
15   -* Scrape websites and receive email when they change
  15 +* Scrape websites and receive emails when they change
16 16 * Track your location over time
17 17
18 18 ## Examples
@@ -37,12 +37,12 @@ If you just want to play around, you can simply clone this repository, then perf
37 37
38 38 * Edit `config/secret_token.rb` and replace `REPLACE_ME_NOW!` with the output of `rake secret`.
39 39 * Run `rake db:create`, `rake db:migrate`, and then `rake db:seed` to create a development MySQL database with some example seed data. Run `rails s`, visit `http://localhost:3000`, and login with the username of `admin` and the password of `password`.
40   -* Make some extra Terminal windows and run `bundle exec rails runner bin/schedule.rb` and `bundle exec rails runner bin/twitter_stream.rb`
  40 +* Make some extra Terminal windows and run `bundle exec rails runner bin/schedule.rb`, `bundle exec rails runner bin/twitter_stream.rb`, and `script/delayed_job run` in separate windows.
41 41 * Setup some Agents!
42 42
43 43 ### Real Start
44 44
45   -Follow these instructions if you wish to deploy your own version of Huginn or contribute back to the project. GitHub doesn't make it easy to work with private forks of public repositories, so we recommend that you follow the following steps:
  45 +Follow these instructions if you wish to deploy your own version of Huginn or contribute back to the project. GitHub doesn't make it easy to work with private forks of public repositories, so I recommend that you follow the following steps:
46 46
47 47 * Make a public fork of Huginn
48 48 * Make a private, empty GitHub repository called `huginn-private`
@@ -59,11 +59,11 @@ Follow these instructions if you wish to deploy your own version of Huginn or co
59 59 git remote add public git@github.com:you/huginn.git
60 60
61 61 * Run the steps from *Quick Start* above to configure your copy of Huginn.
62   -* When you want to contribute patches, do a remote push from your private repository to your public fork, then make a pull request to us.
  62 +* When you want to contribute patches, do a remote push from your private repository to your public fork of the relevant commits, then make a pull request to this repository.
63 63
64 64 ## Deployment
65 65
66   -Deployment right now is configured with Capistrano, Unicorn, and nginx. You should feel free to deploy in a different way, however.
  66 +Deployment right now is configured with Capistrano, Unicorn, and nginx. You should feel free to deploy in a different way, however, and please submit your deployment solutions back!
67 67
68 68 ### Required Setup
69 69
@@ -71,11 +71,11 @@ In your private copy of Huginn, do the following:
71 71
72 72 * Edit `app/models/user.rb` and change the invitation code(s) in `INVITATION_CODES`. This controls who can signup to use your installation.
73 73 * Edit `app/mailers/system_mailer.rb` and set your default from address.
74   -* Edit `config/unicorn/production.rb` and replace instances of *you* with the correct username for your server.
75 74 * Edit `config/environments/production.rb` and change the value of `DOMAIN` and the `config.action_mailer.smtp_settings` setup, which is currently setup for sending email through a Google Apps account on Gmail.
76 75 * Setup a place for Huginn to run. I recommend making a dedicated user on your server for Huginn, but this is not required. Setup nginx or Apache to proxy pass to unicorn. There is an example nginx script in `config/nginx/production.conf`.
77 76 * Setup a production MySQL database for your installation.
78   -* Edit `config/deploy.rb` and change all instances of `you` and `yourdomain` to the appropriate values for your server setup, then run `cap deploy:setup` followed by `cap deploy`. If everything goes well, this should start some unicorn workers on your server to run the Huginn web app.
  77 +* Edit `config/unicorn/production.rb` and replace instances of *you* with the correct username for your server.
  78 +* Edit `config/deploy.rb` and change all instances of `you` and `yourdomain` to the appropriate values for your server setup. If you want RVM to be used, uncomment the appropriate lines. Then, run `cap deploy:setup` followed by `cap deploy`. If everything goes well, this should start some unicorn workers on your server to run the Huginn web app.
79 79 * After deploying with capistrano, SSH into your server, go to the deployment directory, and run `RAILS_ENV=production bundle exec rake db:seed` to generate your admin user. Immediately login to your new Huginn installation with the username of `admin` and the password of `password` and change your email and password!
80 80 * You'll need to run bin/schedule.rb and bin/twitter_stream.rb in a daemonized way. I've just been using screen sessions, but please contribute something better!
81 81

0 comments on commit 6dd1fa5

Please sign in to comment.
Something went wrong with that request. Please try again.