Wekan and Yunohost

And what kind of builds you mean, like bundle.zip, or some deb package, or Snap, or Docker. I have tried to add additional architectures sometime but it's not automated or not working yet.

Hi @xet7,

I'm one of the app packager of Wekan for YunoHost. And the link to the original post I made : https://github.com/YunoHost-Apps/wekan_ynh/issues/54#issuecomment-537271009

First I have to say a big thank you for the hard work you have already done to the awesome Wekan. It was just the app I was looking for to manage my work on YunoHost. And thank to having took the time to respond.

My bad for the changelog, I didn't seen it exists. I used to go on the releases page (https://github.com/wekan/wekan/releases ) of the repository to find the information. But now I know ^^

Regarding the number of releases, sometimes there are 9 releases a day (V3.27 to V3.35 on 2019-08-29).

As I'm not a developer, I'm not a good juge..

I don't know if it's because Wekan is still developing but from YunoHost perspective we use to package apps with longer release cycle (Mastodon: v3.0.0rc2 / 137 releases; Peertube: v1.4.1 / 76 releases; pixelfed 0.10.6 beta / 19 releases)

Or maybe it's the way we package Wekan for YunoHost.

YunoHost plans to provide apps for selfhosting. Hosting from a RaspberryPi (arm and arm64) to servers or virtual servers (amd64). Having YunoHost users installing apps with one clic...

We don't package using .deb package or snap or docker. We do it like a manual installation.

At the beginning we packaged directly from the sources and since you provided builds at https://releases.wekan.team/, we use them to improve installation reproductibility and reduce installation time.

When I discovered https://releases.wekan.team/raspi3/, it was just perfect for us to be able to install wekan on raspberry Pi arm64 from an already built version.

So for packaging wekan, we use a link to the builded .zip files (amd64 and arm64), having a sha256sum of each release file to be sure they are not altered.

A first point is: as each built is not kept at https://releases.wekan.team/, we have to download them and upload them on our own website to keep them available.

A second point is: as there is no new raspberryPi since 2.94, it difficult to upgrade the whole package for YunoHost

A third point is: for each Wekan release we have to make changes in our own package.

So the effort for maintaining the wekan package up to date is high for us.

I don't know how other applications do and if it can be automated but some are able to provide builds with the release sources:

• https://github.com/writeas/writefreely/releases
• https://github.com/Requarks/wiki/releases
• https://github.com/syncthing/syncthing/releases (^^ too much builds ^^)

Or maybe we should go back to package from the source file.

I can provide arm64 .zip file https://releases.wekan.team/raspi3/ sometime in near future

Wekan has been developed since 2015, and there is very rapid release / feedback / fix cycle in Wekan development. I don't mean everyone should upgrade for every release. For example with Snap it's possible to set updating to happen at night. Some update bash scripts use cron to update at some time at night.

Sometimes I receive many pull requests per day. I do check and merge them soon, making new releases.

For some platforms like Univention, I release less often. Sometime new version can be for example 30 releases newer.

With cron, it's possible to setup update for example at weekend or once a month

@yalh76 I have now created new bundle wekan-3.45-arm64.zip at http://releases.wekan.team/raspi3/

Please test

It did take quite a lot of steps, for those I added there my in-progress version of maintainer-make-bundle.sh

Would you need also RasPi3 disk image?

I will look later when I could have time for that

Thanks a lot @xet7. I know it could took a lot of time. I will update Wekan for YunoHost right now. Maybe a good way to reduce the time needed for you would be to use something like GitHub CI. There are some CI that are able to build the release from sources on different architectures and push them to http://releases.wekan.team/

If we can do something to help you on that point, let us know.

Hey. How can I solve this problem? Log:

2020-10-21 07:41:18,095: INFO - Installing wekan… 2020-10-21 07:41:18,174: DEBUG - The permission database has been resynchronized 2020-10-21 07:41:18,196: INFO - Could not complete the operation ‘Create permission ‘wekan’’. Please provide the full log of this operation by clicking here to get help

The file does not exist: ‘/etc/yunohost/apps/docker/settings.yml’

@yalh76 Do you know about those docker settings?

@alex22 I also recommend you asking at yonohost issues too

https://github.com/YunoHost/issues/issues

Anyway, newest Wekan Docker settings are at docker-compose.yml at https://github.com/wekan/wekan , I don't know YonoHost specific differences

I would gues that at your /etc/yonohost/apps are some other app settings, so for Wekan ROOT_URL something similar

like in other apps

We don't use docker in YunoHost. @alex22 better to open an issue at https://github.com/YunoHost-Apps/wekan_ynh/issues