Debugging

Finding memory leaks

Collect a heap profile and then analyze it

Older article: How to Self Detect a Memory Leak in Node

100% CPU usage

1. Increase ulimit system wide to 100 000 in systemd config.

2. Wekan Javascript code has Node 100% CPU fixes included. Also read on-going 100% CPU usage issue progress.

3. Newest Wekan includes fixed Node.js binary. Use Fibers fixed node source from Sandstorm or binary copied from Sandstorm or downloaded as node binary or tar.gz package from https://releases.wekan.team , related fixes are in Wekan GitHub repo Dockerfile, snapcraft.yaml and wekan/server/authentication.js.

Scaling to thousands of users

Production setup at AWS

Current versions of dependencies

Dockerfile, versions of Meteor.js, Node etc listed at beginning.

Included Meteor packages

Included Meteor package versions

Added packages at package.json

Build from source

Wekan:

• On any x64 hardware that has Ubuntu 14.04 or Debian 9 or newer installed directly or in VM: Build from source scripts

Wekan for Sandstorm:

• Install above Wekan from source
• Install Sandstorm locally with curl https://install.sandstorm.io | bash, select dev install
• Install meteor-spk
• Get 100% CPU issue fibers fixed node, and copy it to spk directory:
  wget https://releases.wekan.team/node
chmod +x node
mv node ~/projects/meteor-spk/meteor-spk-0.4.0/meteor-spk.deps/bin/
• Add to your /home/username/.bashrc :
  export PATH=$PATH:$HOME/projects/meteor-spk/meteor-spk-0.4.0
• Close and open your terminal, or read settings from .bashrc with
  source ~/.bashrc
• cd wekan && meteor-spk dev
• Then Wekan will be visible at local sandstorm at http://local.sandstorm.io:6080/
• Sandstorm commands: sudo sandstorm. Release scripts. Official releases require publishing key that only xet7 has.

Docker:

• git clone https://github.com/wekan/wekan
• cd wekan
• Edit docker-compose.yml script ROOT_URL etc like documented at https://github.com/wekan/wekan-mongodb docker-compose.yml script
• docker-compose up -d --build