huginn | Create agents that monitor and act on your behalf Your agents are standing by! | Runtime Evironment library

If you just want to play around, you can simply fork this repository, then perform the following steps:. Note: By default, email messages are intercepted in the development Rails environment, which is what you just setup. You can view them at http://localhost:3000/letter_opener. If you'd like to send real email via SMTP when playing with Huginn locally, set SEND_EMAIL_IN_DEVELOPMENT to true in your .env file. If you need more detailed instructions, see the Novice setup guide.
Run git remote add upstream https://github.com/huginn/huginn.git to add the main repository as a remote for your fork.
Copy .env.example to .env (cp .env.example .env) and edit .env, at least updating the APP_SECRET_TOKEN variable.
Make sure that you have MySQL or PostgreSQL installed. (On a Mac, the easiest way is with Homebrew. If you're going to use PostgreSQL, you'll need to prepend all commands below with DATABASE_ADAPTER=postgresql.)
Run bundle to install dependencies
Run bundle exec rake db:create, bundle exec rake db:migrate, and then bundle exec rake db:seed to create a development database with some example Agents.
Run bundle exec foreman start, visit http://localhost:3000/, and login with the username of admin and the password of password.
Setup some Agents!
Read the wiki for usage examples and to get started making new Agents.
Periodically run git fetch upstream and then git checkout master && git merge upstream/master to merge in the newest version of Huginn.
Have a look at the installation guide.
See private development instructions on the wiki. In order to use the WeatherAgent you need an API key with Wunderground. Signup for one and then change the value of api_key: your-key in your seeded WeatherAgent. Note, Wunderground no longer offers free API keys. You can still use the WeatherAgent by setting the service key to darksky, and getting an API key from DarkSky. We assume your deployment will run over SSL. This is a very good idea! However, if you wish to turn this off, you'll probably need to edit config/initializers/devise.rb and modify the line containing config.rememberable_options = { :secure => true }. You will also need to edit config/environments/production.rb and modify the value of config.force_ssl.