Email Bot Troubles about huginn HOT 1 OPEN

We were able to resolve this issue on Ubuntu 22 and Windows implementations. I think this line of the README could use more clarity:

* Copy .env.example to .env (cp .env.example .env) and edit .env, at least updating the APP_SECRET_TOKEN variable.

In my head, I would prefer a huginn deployment that uses compose, such as the following:

services:
  huginn:
    image: huginn/huginn
    ports:
      - "3000:3000"
    volumes:
      - .env:/app/.env

However, when sharing the .env file, huginn doesn't like that the system owns it. When I ran this command in Ubuntu I was able to share it through into the container:

sudo chown 1001:0 .env

So when we moved @b-don194 to a Windows system, we used Docker copy to directly inject the new .env file (as I wasn't sure at the time how to change the Windows file permissions. That command was something like the following:

docker cp .env <container_name>:/app/.env

Hope this helps the next person!

from huginn.