nikku / wuffle

A multi-repository / multi-organization task board for GitHub issues.
https://wuffle.dev
MIT License
118 stars 23 forks source link

Problems installing #32

Closed retog closed 5 years ago

retog commented 5 years ago

Hi, I've installed the docker image and I can see a board with the configured columns but I have the following issues/questions:

nikku commented 5 years ago

The preferred way of setting up the application is via a local development setup. The docker images are meant for production use only.

Did you configure your app providing all required environment variables?

retog commented 5 years ago

Thank @nikku,I forgot the BASE_URL variable, after adding I'm no longer redirected to localhost. However I still se no card on the board.

nikku commented 5 years ago

Which exact steps did you undertake? How did you configure the board?

joannenolan-sky commented 5 years ago

This could be because you have not updated your User authorization callback URL on the app setting page(https://github.com/settings/apps/<app-name>). It should be <BASE_URL>/wuffle/login/callback. It is probably still set to http://localhost:3000/wuffle/login/callback which it is set to as a default.

nikku commented 5 years ago

The setup instructions are not great. Bear with me, as I think about how to improve it.

:grimacing:

retog commented 5 years ago

What I've basically done is adding and fixing env-variables till I no longer got an error message....

I ended up with the following configuration in docker-compose (the first part is traefik sepcific which I use for SSL termination):

wuffle:
    image: nrehwaldt/wuffle
    labels:
      traefik.frontend.rule: Host:wuffle.factsmission.org
      traefik.frontend.entryPoints: https
      traefik.port: '3000'
      traefik.enable: 'true'
    volumes:
      - ./wuffle/wuffle.config.js:/app/packages/app/wuffle.config.js # this didn't work, so I added config as variable below
    environment:
      APP_ID: 35560 
      GITHUB_CLIENT_ID: Iv1.026bc702254c070f
      GITHUB_CLIENT_SECRET: *****
      WEBHOOK_SECRET: sameAsEnteredIn AppConfig
      PRIVATE_KEY: LS0tL......WS0tLS0tCg==
      SESSION_SECRET: justWroteSomething
      BASE_URL: https://wuffle.factsmission.org/board
      BOARD_CONFIG: '{"columns":[{"name":"Inbox","label":null},{"name":"Backlog","label":"backlog"},{"name":"Ready","label":"ready"},{"name":"In Progress","label":"in progress"},{"name":"Needs Review","label":"needs review"},{"name":"Done","label":null,"closed":true}],"repositories":["retog/repo1", "org/repo2"]}'
    restart: unless-stopped

This is some of the config in GitHub:

image

nikku commented 5 years ago

Good stuff.

nikku commented 5 years ago

BASE_URL should not end with /board I believe.

retog commented 5 years ago

Change the BASE_URL to https://wuffle.factsmission.org/ - but this doesn't seem to have changed anything,

nikku commented 5 years ago

Well, the login does not seem to work at the moment. This is related to the BASE_URL not properly being set up or some other configuration issue.

joannenolan-sky commented 5 years ago

I would try removing the forward slash at the end.

Also I don't see a WEBHOOK_PROXY_URL in you environment variables

nikku commented 5 years ago

WEBHOOK_PROXY_URL should not be set in production. It is required for development mode, only.

retog commented 5 years ago

YES!!!! Removing the trailing slash from BASE_URL fixed it!

The only remaining thing is that I only see issues of first repository specified in the array for the repositories key in the BOARD_CONFIG json.

Thanks a lot for your help!

nikku commented 5 years ago

What do your logs say? The app should give you helpful debug output.

nikku commented 5 years ago

I've improved the run validation via https://github.com/nikku/wuffle/commit/9866414c9d68e9280e6ba76181dcb07934179169. It will now capture miss-configured or missing BASE_URL configs.

image

nikku commented 5 years ago

Regarding your last comment, you must install your app on all organizations / enable it for all your repositories in order to see stuff on the board.

nikku commented 5 years ago

Created some reasonable setup instructions that should prevent this issue from happening again.

I've fixed a few quirks on the way, too :bike:.

retog commented 5 years ago

YES

What do your logs say? The app should give you helpful debug output.

The log is somehow cluttered with lines like these:


17:03:19.738Z  INFO http: GET /wuffle/board/updates?cursor=7841334 304 - 0.98 ms (id=83901d09-1854-4e70-b8e1-a1afd2978a8a)

17:03:19.837Z  INFO http: GET /wuffle/board/updates?cursor=7841334 304 - 1.23 ms (id=2b41cbcc-9bad-4595-8cbe-b19042a44b32)

17:03:20.740Z  INFO http: GET /wuffle/board/updates?cursor=7841334 304 - 1.08 ms (id=050532c0-4cef-40c3-a225-6add78bfc912)

17:03:20.780Z  INFO http: GET /wuffle/board/updates?cursor=7841334 304 - 1.29 ms (id=6bffb249-1947-49a6-89a1-1858b8285796)

17:03:22.739Z  INFO http: GET /wuffle/board/updates?cursor=7841334 304 - 2.30 ms (id=d1de582e-6415-49fd-9788-c5850ce676c5)

17:03:22.847Z  INFO http: GET /wuffle/board/updates?cursor=7841334 304 - 1.59 ms (id=856fe100-4255-4f46-aa43-54db6ddeb42f)

17:03:23.741Z  INFO http: GET /wuffle/board/updates?cursor=7841334 304 - 1.56 ms (id=501fdeef-b02e-4d34-bea5-ad284a525049)

17:03:23.778Z  INFO http: GET /wuffle/board/updates?cursor=7841334 304 - 1.43 ms (id=8bab9f99-fba1-4975-993d-48d633479d2b)

17:03:25.741Z  INFO http: GET /wuffle/board/updates?cursor=7841334 304 - 1.16 ms (id=8be89bd5-4246-46fa-b6a3-f07c61ab6866)

17:03:25.848Z  INFO http: GET /wuffle/board/updates?cursor=7841334 304 - 1.10 ms (id=af7b1afa-865c-45fd-92fa-ecc0196dcbdf)

17:03:26.742Z  INFO http: GET /wuffle/board/updates?cursor=7841334 304 - 0.89 ms (id=56c814d8-a5cc-41a9-868d-2b085c49e93d)

17:03:26.786Z  INFO http: GET /wuffle/board/updates?cursor=7841334 304 - 2.90 ms (id=af0ed47b-7e3a-4956-ab23-9640afb3d579)

17:03:28.737Z  INFO http: GET /wuffle/board/updates?cursor=7841334 304 - 0.90 ms (id=b5f7b9a1-eb77-4d68-b4ec-08d587983909)