This is done by now.

@ChristopherMag yes, having valid certs is the best way forward. Certs are also used in various non-HTTP protocols (irc, jabber, DoT, DoH etc) and most mobile apps will pretty much refuse to connect without valid certs. You are just fighting a battle which you will lose eventually. If not now, in the next update of the app.

Cloudron has support for self signed certs, but Cloudron started even before Let's Encrypt was a reality . These days all that code is just legacy. There is really no reason to use self signed certs for most purposes.

@nebulon Cool beans! Thanks a lot.

@xet7 welcome here!

Cloudron is currently on Mongo 4.4 . Next release will make it Mongo 5 or Mongo 6. The version we choose here will largely depend on how easy it is to migrate from existing Mongo 4 automatically. If we can automatically go from 4->6 then we will probably go with 6.

Goes without saying thanks for all your work on wekan.

@nebulon sorted & found it in spam -- I guess because it was set to a subdomain

@adamaragon If I understand correctly, you are asking how to implement a new theme and not how to use an existing theme. If you want to use an existing theme, then you just Select Board -> Board Settings -> Change Color.

For making a new theme, you have to setup a development environment for wekan since it involves editing code files. If you are looking for a persistent way to keep your custom code/theme changes, then there is no way than to build a custom wekan package. This is because code on Cloudron is read-only and if we let people edit the files, it will break updates. Building a custom package is quite easy, if you want to go down the route - https://forum.cloudron.io/topic/3102/building-custom-packages

If you want to just have a dev Wekan environment and the goal is to submit a PR to the upstream project, you can do it like this on Cloudron:

Install wekan. Best not to use your production instance. Install the CLI tool - sudo npm install -g cloudron on your laptop (and not on the server) cloudron debug --app mywekan.domain.com . This command will place your app in "debug" mode. In debug mode, you can edit all the files you want. Note that this does not start the app itself, just puts the files in a editable filesystem. At this point, you won't be able to access Wekan in the browser since the app is not running. You can now use Cloudron's File manager to edit the files. All the wekan code is in /app/code In the CLI, you can cloudron exec --app wekan.example.com. This gives you a shell into the app's file system. You can edit the files here too inside /app/code. It's the same as the UI above. Once you have edited it, you have to run /app/code/start.sh (using the exec terminal above). This will start the app and you can also access Wekan in your browser now. To stop the app, ctrl+c.

Once you have made changes, I guess you have to submit a PR to upstream Wekan project so they can include it.

Finally, you can remove the debug mode using cloudron debug --disable --app mywekan.domain.com. Important that removing debug mode will roll back the code and you will lose your code changes (as mentioned in the beginning).

Let me know if you need help.

@girish Many thanks Girish. It must have been a space problem indeed. Looking at the log, the processed froze while downloading the last big part of the image (~570MB). I tried to duplicate the app, which worked fine but and the process also froze when trying to update it (also while downloading that part the image).

Anyway, I had a about 3GB of free space which I though would be enough to update Wekan but after doing some cleaning up on the server (like deleting old apps I wasn't using), I went to about 7GB of free space and the update started working again.

I found restarting Mongodb service manually fixes the error. Or maybe it was just a coincidence.

Brill! Thanks for looking into it and managing to sort out that quick!

Got it. It seems the swimlane is hard coded - https://github.com/wekan/wekan/blob/e9d27c521e2aced2232fbbb30af32b0c12ed6148/i18n/en.i18n.json#L10 I guess that is what Lauri was trying to say. I guess Wekan code has to have an option to remove it/make it optional.

yup, i have pushed the change for next wekan release.

@girish said in How to disable user signup?:

Bbut if you click register and try to register, one cannot login without an invite code.

Ah, I see. I just tested this and you are correct. That is good enough!

I do still have these two extra "blank" users (one admin and one not) that I cannot figure out how to get rid of and cannot edit (I tried to set them to Inactive, but the Save button doesn't appear to do anything), but I also cannot login as them, so I think it's okay. (These users are only in wekan, not in cloudron. My cloudron users are just the ones I expect to see.)

Thanks for the help, and for the update to the docs. You are doing wonderful work trying to make self-hosting feasible for folks willing to try.

@yusf AI 🙂

@nebulon great, thanks!

@jdaviescoates Ok thanks. I will try again and report back.

There we go, it is updating now. Thanks so much.

Is there any way Wekan can be reconfigured to allow for LDAP sign-ins as well as open self-registration? @girish