I recently became intrigued with using Huggin for a few automation tasks I had been doing manually up to this point. However, it looks like nobody to this point had bothered to really post how to set this up with unRAID. It was not too tricky since you can use Docker with unRAID but there were a few things that slowed me down.
I’m documenting them here for anyone else who wants to do this, you can hopefully be saved some time.
As the first step, you’re going to to need a template to do this since unRAID makes use of Docker templates for setting up things quickly. I created one you can use right here if you don’t want to create your own. That template assumes you have a
appdata mount point already existed for your other applications. If you don’t have one already (this is your first docker app in unRAID) then you can read this to get more info.
If you are using my template, you can follow the below directions:
https://github.com/hilts-vaughan/unraid-docker-templates/tree/master/unraid-hilts-vaughan-templatesand then hit “Save”
password– make sure you have saved these.
I had to do a couple things in unRAID land to get this working properly as it was not working out of the box.
Configuring the user in Huginn
http://tower:3000/users/edit(you can change the
towerif you changed the name of your unRAID box)
Then, you can hit “Update”
Configuring unRAID with environment variables
If you plan on using GMail for the e-mail in Huginn, you may want to read the below section first. To configure environment variables, and email specifically for Huginn, you can use the following steps at the time of publication (tested for GMail):
If you want to configure anything else at this point, you can refer to this environment variable documentation to do so.
If you are using GMail, there are additional steps go through to generate something secure and that is usable for Huginn. I was getting some interesting errors like:
huginn rbuf fill
… and authentication errors among other things. In practice, if you plan on using this for any amount of time I would advise you sign up for something like Amazon SES or something with a very basic (or free) SMTP server you can use and then have them send your emails for you. This will give you a layer of insulation against having your e-mail credentials served.
Otherwise, do this:
To test this, I would just run a couple of the default agents and see if it works. The easiest way to do this is:
That should be it. I hope this saves you a couple hours. I wish someone had told me about a couple of these things when I started (and that a unRAID docker template existed!)