Dominik Sander

@MTStrothers The `DOMAIN` should be the URL how you are reaching Huginn, this could be the domain name or IP including the port. Assuming your are running Huginn on 127.0.0.1...

Hmm can you post the output from the [production log](https://github.com/huginn/huginn/blob/master/doc/manual/installation.md#rails-application-log-homehuginnhuginnlogproductionlog) or the docker logs (depending on your setup)?

Sorry, not sure why it is not working for you. I just authenticated a new service on my Huginn instance and it worked using the latest docker image. Maybe twitter...

Hi @keshavm021, you can not deploy individual Agents on machines. Huginn uses multiple background processes (either combined in `threaded.rb` in separated, seed the [Procfile](https://github.com/huginn/huginn/blob/master/Procfile) for examples) to schedule and run...

Do you want to write a new Agent or use existing ones? Huginn has many Agents that connect to external services on the internet, but the Agent itself would still...

No Huginn does not work like this, you can run Agents on multiple machines (to distribute the CPU/network load) but the Agents will run on randomly on all configured servers.

You need to install the same version of Huginn on all machines and configure the [database settings](https://github.com/huginn/huginn/blob/master/.env.example#L19-L25) to use the same database as the first server. On the additional servers...

No it does not work like this, I am not entirely sure how jenkins works, but to run Huginns background processor on multiple servers you need to set up Huginn...

You need to use a docker orchestration framework like [docker swarm](https://docs.docker.com/engine/swarm/) or [kubernetes](https://kubernetes.io/) to have "easy" access to cross node networking. An other option would be to use some kind...

I think it depends on the use case, the Agent expects to always get the same number of matches per "item". It should work if you have a list of...