Skip to content

Debugging

Lauri Ojansivu edited this page Apr 30, 2018 · 26 revisions

Finding memory leaks

How to Self Detect a Memory Leak in Node

100% CPU usage

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

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

  3. 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

Wekan

General

Security

Scaling

Migrating

Support priorities for new features and bugfixes

  1. Commercial Support
  2. Community Support
  3. Debugging

Backup

Repair

Themes

Markdown Syntax

Login Auth

Metrics, Logs, Stats

Integrations

Time

Features

Email

Required Settings

Download

Webservers

REST API Docs

REST API issue

REST API client code

Webhooks

Case Studies

Development

Issues

Clone this wiki locally