Hey @xet7 yes i got some ideas, i use wekan to plan where our constructors are

Solved my first Problem hehe

hi i'm Sat and I am new to wekan

Welcome @satrapes :)

@satrapes Do you have any questions about Wekan?

hi @xet7 actually I am having a bit of trouble with setting up wekan to be accessed by a hostname in my local network in an automated way (avoid manually editing /etc/hosts files). Also to keep it simple I am not using https or anything. Thus far I have

1. Installed wekan and tried a few of its features with localhost address.
2. Changed root-url to let's say http://example.com
3. Added a .conf in sites-enabled. http://ix.io/2BywT

Now since I am new to both wekan and nginx and my linux networking is a bit suspect I may be doing somethiing silly anywhere else. How I reproduce the issue? I log into my localhost to make sure that wekan works alright. I click on a board and then a card. On clicking the card the link will then change to the root-url and then nothing happens. I notice that the link becomes root-url/b/{15-20 random letters}/{board_name}/{15-20 random letters} If I try to access from another computer in the same network it will access example.com in the internet Any ideas? I have spent a few nights trying to understand this and I can't figure it out.

I also have a question regarding making wekan like jira in terms of having a unique number. It would be nice if you could refer to other cards by a human readable name.

Wekan has assignee like Jira https://github.com/wekan/wekan/issues/2452 . But Board Key feature is not funded yet https://github.com/wekan/wekan/issues/2449#issuecomment-671964070

About ROOT_URL: https://github.com/wekan/wekan/wiki/Settings

For example, in Wekan Snap, set ROOT_URL to your computer IP address:

sudo snap set wekan root-url='http://192.168.0.100'
sudo snap set wekan port='80'

There is no need for Nginx, you can stop that.

Alternatively, set some other port:

sudo snap set wekan root-url='http://192.168.0.100:2000'
sudo snap set wekan port='2000'

Boards do have human readable names at end of URL, it is generated from board name/title/topic, whichever you like to call it. When you change board name, also board URL changes.

Thanks, you are right I forgot to mention that I am using Wekan Snap. I have followed the instructions about root-url. And though it works as you say with http://192.168.0.100 but it doesn't work if root-url='http://example.com'. I only provided the url format to indicate that I have set up root-url correctly and it is trying to do the right thing, but something is preventing it from actually loading the card. I understand this https://github.com/wekan/wekan/issues/2896#issuecomment-577257140 and I can make it work with solution 1. For solution 2, I have enabled the DHCP server on my router and matched the root-url with the hostname for my laptop. Do you know of any router or linux network settings that may affect this? I will try again without nginx to see if that makes a mess of things and failing that try to actually set wekan up to be accessible from the internet as example 1 from https://github.com/wekan/wekan/wiki/Settings Thanks again, really nice application.

If you have some exising domain, or buy some domain and set it's nameserver A record pointing to your IP addess, it does work.

Hosts file probably does not work for domain names that have dot

Or, set some subdomain pointing to your Wekan server IP address

For some website to be visible at Internet, usually it needs ports 80 and 443 open to Internet

Also, if you have subdomain that points to your private IP address like 192.168.0.100 , it does work inside your local network for all devices, but not at Internet, because private LAN IP addresses are not routed to Internet

BTW, for programmers: There is currently in progress Meteor.js Impact free online conference https://impact.meteor.com , some talks are now in progress, and all of the conference talks are recorded

There are talks about scaling Meteor, PWAs, etc etc

Thanks again for the pointers.

Hello, How can I transfer my Wekan docker-db? I transer "volumes:

  - ./wekan-db:/data/db" but if I start docker-compose it's didn't start (eternal restarting docker-db) 

how can I migrate Wekan-db if I have only "./wekan-db:/data/db" from my other server

@dmitrii See https://github.com/wekan/wekan/wiki/Export-from-Wekan-Sandstorm-grain-.zip-file and https://github.com/wekan/wekan/wiki/Backup

You copy raw MongoDB files to same version of MongoDB database server raw file directory, start MongoDB, do mongodump, restore to Wekan Snap or Wekan Docker