Join the conversation

Sign in to join this conversation, and others like it, in the communities you care about.

Wekan

Wekan is an open-source kanban board (Trello like) which allows a card-based task and to-do management.

Wekan / Bugs

Stuck at wekan-ldap: updating npm dependencies -- ldapjs...

Stuck at wekan-ldap: updating npm dependencies -- ldapjs...

Wekan/Bugs · July 19, 2020 at 10:17am

Stuck at wekan-ldap: updating npm dependencies -- ldapjs...

Wekan / Bugs · July 19, 2020 at 10:17am (Edited 4 years ago)

I am trying to run wekan from source

I followed the instructions on the wiki and have uncommented the build section from the docker-compose file and did docker-compose up -d --build

I am running it on windows 10 machine

anyone facing / faces similar issue ?

Load previous messages

July 20, 2020 at 9:55am

I did mirror wekan repo by adding my Wekan GitHub API key to Gitea migration username field. I have not tried does migration work without API key.

    • reply
    • like

    i just mirrored my wekan fork and it seems to be have done it

      • reply
      • like

      issues are not there obviously though

        • reply
        • like

        oh I didnt noticed that much, probably coz I dont use it much as well

          • reply
          • like

          I think it does not make sense to fetch all not all the time but when needed

            • reply
            • like

            here is what we are planning on doing for starters

              • reply
              • like

              add custom field in board called gitea-issue

                • reply
                • like

                anytime a card is created in open list / bug label is added to any card I would like to create a gitea issue for it

                  • reply
                  • like

                  once the gitea issue is created will be assigning the gitea issue number to the custom field

                    • reply
                    • like

                    also there will be a board for every gitea repo so in order to keep them in sync we will be relying on the naming of the repo and board

                      • reply
                      • like

                      so say if i have a repo dineshsalunke/sample-repo then there will be a board called dineshsalunke/sample-repo

                        • reply
                        • like

                        setting up such conventions for now, till we find better ways to handle integration

                          • reply
                          • like

                          so now in order to do this we would like to fetch some card, list and board info

                            • reply
                            • like

                            the current way to do this is using the ids from the webhook, first get the card then get the board then get the list

                              • reply
                              • like

                              I think this could be made simple

                                • reply
                                • like

                                and if it does than using node-red sort of thing to do your workflows would be a lot easier

                                  • reply
                                  • like

                                  thats exactly what we are doing now as we are playing around with the idea

                                    • reply
                                    • like

                                    If you have any better ideas to share we would love it

                                      • reply
                                      • like