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

You need to build from source

There is existing Wekan-Gogs integration https://github.com/wekan/wekan-gogs

You can look at it for inspiration to integration to Gitea

You can also send pull requests to that integration and Wekan https://github.com/wekan/wekan

For UI changes, you can send pull request for new theme https://github.com/wekan/wekan/wiki/Custom-CSS-themes

Or add some new config options to Board Settings

I do recommend sending all your changes to this upstream Wekan https://blog.wekan.team/2018/02/benefits-of-contributing-your-features-to-upstream-wekan/

Because it's a huge amount of work to maintain separate fork of Wekan

I'm releasing new version of Wekan about once a day

So in case of fork, you would need to merge changes and fix merge conflicts very often

Current UI plans are here https://github.com/wekan/wekan/issues/3086#issuecomment-629682047

If you don't have any important files on your Ubuntu 18.04 then you could install Ubuntu 20.04 on top of it

Or alternatively, from Ubuntu 20.04 live USB copy files to your Windows partition

For some new laptops, booting to Linux requires disabling Secure Boot and enabling Legacy Boot

at BIOS/UEFI settings

The time to build could change in future, if there are fixes to build time bottlenecks. For example, previously building Wekan did take about one hour - after changing one dependency to older version, time dropped to 11 minutes.

Some future fix could also change time from 11 minutes to much less, or some more. It remains to be seen, there are updates to dependencies very often.

We checked wekan-gogs

but we need something more different and tightly integrated, also wekan-gogs in not maintained for quite some time now

one of the first things i would like to do is update the rest API

one of the first difficulties we are having with rest api is there is no search parameter

so right now we have to take a loner route to fetch all the boards, filter them based on title, find the right one and then fetch all info related to it with the id

thats a real pain point right now

also one more pain point is fetching labels and custom fields for cards