(Last Updated On: September 15, 2018)

Wekan is an Open Source kanban board application with the MIT license. Wekan is an unbeatable tool that helps you keep your things organized, be it Work tasks, planning for holidays, preparing a personal todo list, managing other people e.t.c. It gives you a visual overview of the current state of projects which guarantees your productivity by allowing you to focus on the few items that matter the most.

For Ubuntu users, see How To Install Kanboard on Ubuntu 18.04 LTS with Nginx

Features of Wekan Kanban

  • You can list of all your public and private boards using shortcuts at top of page
  • Has a full screen or window on a desktop and full screen on mobile Firefox without a need for browser buttons
  • You have Keyboard shortcuts button at the bottom right corner
  • User management module
  • You can restore an archived board
  • You add, star, watch, archive and delete boards
  • Import Trello board: Text, labels, images, comments, checklists. Not imported yet: stickers, etc.
  • Export Wekan board
  • Clipboard and drag and drop functions
  • Provides a REST API
  • Authentication, Admin Panel, SMTP Settings and many others.

The easiest way to install Wekan Kanban board platform on CentOS 7 server is by using snapand snap package has to be installed separately.

Step 1: Install snap on CentOS 7

Install snap on CentOS 7 by running the commands below:

sudo yum makecache fast
sudo yum install yum-plugin-copr epel-release
sudo yum copr enable ngompa/snapcore-el7
sudo yum install snapd
sudo systemctl enable --now snapd.socket

Step 2: Install wekan on CentOS 7

Once the snap package is installed, use it to install wekan.

sudo snap install wekan

Set web URL root for wekan:

sudo snap set wekan root-url="https://wekan.example.com"

You can run Wekan on standard http port 80 or on a different port like.3001 A custom port is useful when running Wekan behind a proxy like Nginx

sudo snap set wekan port='3001'
sudo systemctl restart snap.wekan.mongodb
sudo systemctl restart snap.wekan.wekan

Check for status

# ss -tunelp | grep 3001
tcp    LISTEN     0      128       *:3001                  *:*                   users:(("node",pid=25724,fd=14)) ino:4125584 sk:ffff8b01487ab640 <->

# systemctl status  snap.wekan.wekan
● snap.wekan.wekan.service - Service for snap application wekan.wekan
   Loaded: loaded (/etc/systemd/system/snap.wekan.wekan.service; enabled; vendor preset: disabled)
   Active: active (running) since Sat 2018-08-18 09:08:44 UTC; 8s ago
 Main PID: 25621 (wekan-control)
   CGroup: /system.slice/snap.wekan.wekan.service
           ├─25621 /bin/bash /snap/wekan/249/bin/wekan-control
           └─25724 /snap/wekan/249/bin/node main.js

Aug 18 09:08:44 centos-01 wekan.wekan[25621]: BROWSER_POLICY_ENABLED=true (default value)
Aug 18 09:08:44 centos-01 wekan.wekan[25621]: TRUSTED_URL= (default value)
Aug 18 09:08:44 centos-01 wekan.wekan[25621]: MONGO_URL=mongodb:///var/snap/wekan/249/share/mongodb-27019.sock/wekan
Aug 18 09:08:45 centos-01 wekan.wekan[25621]: Presence started serverId=XxH7mx9v3uaiBPFTS
Aug 18 09:08:45 centos-01 wekan.wekan[25621]: Note: you are using a pure-JavaScript implementation of bcrypt.
Aug 18 09:08:45 centos-01 wekan.wekan[25621]: While this implementation will work correctly, it is known to be
Aug 18 09:08:45 centos-01 wekan.wekan[25621]: approximately three times slower than the native implementation.
Aug 18 09:08:45 centos-01 wekan.wekan[25621]: In order to use the native implementation instead, run
Aug 18 09:08:45 centos-01 wekan.wekan[25621]: meteor npm install --save bcrypt
Aug 18 09:08:45 centos-01 wekan.wekan[25621]: in the root directory of your application.

Its systemd service unit file is /etc/systemd/system/snap.wekan.wekan.service

Disable and enable wekan service

Use the following snap commands to enable and disable wekan on CentOS 7 server.

sudo snap disable wekan
sudo snap enable wekan

If you use the mongodb port for another app, then, change it too:

sudo snap set wekan mongodb-port=27019

Accessing MongoDB CLI for Administration

To use MongoDB CLI, you need to install MongoDB 3.2.x tools, and run on CLI:

$ mongo --port 27019

Restart Wekan after changes

If you need to restart Wekan whenever you make changes, use the command:

sudo systemctl restart snap.wekan.wekan

Step 3: Set Snap Auto-updates

Install all Snap updates automatically between 02:00 AM and 04:00 AM

snap set core refresh.schedule=02:00-04:00

Automatic upgrades happen sometime after Wekan is released, or at a scheduled time, or with:

sudo snap refresh

Step 4: Configure Wekan Email Settings (Optional)

Configure Admin notification email. This is optional since Wekan doesn’t need email configurations to function.

sudo snap set wekan mail-url='smtps://user:[email protected]:453'
sudo snap set wekan mail-from='Wekan Boards <[email protected]>'

Step 5: Get Letsencrypt SSL certificate

Request for certbot ssl certificate that will be used on Wekan nginx configuration file. As port 80 is used for this, ensure it is open on the firewall:

sudo firewall-cmd --add-service=http --permanent
sudo firewall-cmd --reload

Request for a certificate using scriptcertbot-auto. Provide a valid email address for expiry notifications and a valid domain to be used for Wekan.

wget https://dl.eff.org/certbot-auto
chmod a+x certbot-auto
mv certbot-auto /usr/local/bin
export DOMAIN="wekan.example.com"
export EMAIL="[email protected]"
certbot-auto certonly --standalone -d $DOMAIN --preferred-challenges http --agree-tos -n -m $EMAIL --keep-until-expiring

Step 6: Configure Nginx Proxy

Install Nginx which will serve as a Reverse proxy for Wekan.

sudo yum install nginx

Once installed, configure it like below:

sudo vim /etc/nginx/conf.d/wekan.conf

Remember and modify content to fit your use. An important setting to change is the Wekan domain name, so replace all occurrences of example.com with your domain name.

# this section is needed to proxy web-socket connections
map $http_upgrade $connection_upgrade {
    default upgrade;
    ''      close;
}

# HTTP
server {
    listen 80; # if this is not a default server, remove "default_server"
    listen [::]:80 ipv6only=on;

    server_name example.com;

    # redirect non-SSL to SSL
    location / {
        rewrite     ^ https://example.com$request_uri? permanent;
    }
}

# HTTPS server
server {
    listen 443 ssl http2; # we enable HTTP/2 here (previously SPDY)
    server_name example.com; # this domain must match Common Name (CN) in the SSL certificate

    ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;

    # If your application is not compatible with IE <= 10, this will redirect visitors to a page advising a browser update
    # This works because IE 11 does not present itself as MSIE anymore
    if ($http_user_agent ~ "MSIE" ) {
        return 303 https://browser-update.org/update.html;
    }

    # Pass requests to Wekan.
    # If you have Wekan at https://example.com/wekan , change location to:
    # location /wekan {
    location / {
        proxy_pass http://127.0.0.1:3001;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade; # allow websockets
        proxy_set_header Connection $connection_upgrade;
        proxy_set_header X-Forwarded-For $remote_addr; # preserve client IP

        # this setting allows the browser to cache the application in a way compatible with Meteor
        # on every applicaiton update the name of CSS and JS file is different, so they can be cache infinitely (here: 30 days)
        # the root path (/) MUST NOT be cached
        #if ($uri != '/wekan') {
        #    expires 30d;
        #}
    }
}

For the default Nginx configuration, here are the recommended settings:

user nginx;
worker_processes auto;
pid /run/nginx.pid;
include /usr/share/nginx/modules/*.conf;

events {
	worker_connections 1024;
	# multi_accept on;
}

http {

	##
	# Basic Settings
	##

	sendfile on;
	tcp_nopush on;
	tcp_nodelay on;
	types_hash_max_size 2048;
	server_tokens off;
        set_real_ip_from 0.0.0.0/32; # All addresses get a real IP.
        real_ip_header X-Forwarded-For;
        limit_conn_zone $binary_remote_addr zone=arbeit:10m;
        client_body_timeout 60;
        client_header_timeout 60;
        keepalive_timeout 10 10;
        send_timeout 60;
        reset_timedout_connection on;

	# server_names_hash_bucket_size 64;
	# server_name_in_redirect off;

	include /etc/nginx/mime.types;
	default_type application/octet-stream;

	##
	# SSL Settings
	##

	ssl_protocols TLSv1.2 TLSv1.1 TLSv1; # Dropping SSLv3, ref: POODLE
	ssl_prefer_server_ciphers on;
        ssl_session_cache shared:SSL:30m;
        ssl_session_timeout 1d;
        ssl_ciphers ECDH+aRSA+AESGCM:ECDH+aRSA+SHA384:ECDH+aRSA+SHA256:ECDH:EDH+CAMELLIA:EDH+aRSA:+CAMELLIA256:+AES256:+CAMELLIA128:+AES128:+SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS:!RC4:!SEED:!ECDSA:CAMELLIA256-SHA:AES256-SHA:CAMELLIA128-SHA:AES128-SHA;
        ssl_ecdh_curve secp384r1;
        ssl_stapling on;
        ssl_stapling_verify on;
        add_header X-XSS-Protection '1; mode=block';
        add_header X-Frame-Options SAMEORIGIN;
        add_header Strict-Transport-Security 'max-age=31536000';
        add_header X-Content-Options nosniff;
        add_header X-Micro-Cache $upstream_cache_status;

	##
	# Logging Settings
	##

	access_log /var/log/nginx/access.log;
	error_log /var/log/nginx/error.log;

	##
	# Gzip Settings
	##

	gzip on;
	gzip_disable "msie6";
        gzip_buffers 16 8k;
        gzip_comp_level 1;
        gzip_http_version 1.1;
        gzip_min_length 10;
        gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript image/x-icon application/vnd.ms-fontobject font/opentype application/x-font-ttf;
        gzip_vary on;
        gzip_proxied any; # Compression for all requests.

	##
	# Virtual Host Configs
	##

	include /etc/nginx/conf.d/*.conf;
	include /etc/nginx/sites-enabled/*;
}

Start nginx service and enable it to start on boot:

$ sudo nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

If config is OK, take it into use by starting nginx service:

sudo systemctl start nginx
sudo systemctl enable nginx

You can view wekan help page by running:

wekan.help

Step 7: Adding Wekan UI Users

Go to your Wekan URL like https://example.com/sign-up  page. For a fresh installation, you need to signup to get admin account.

Register your username, email address, and password. The first user to be registered have admin privileges, and the next one will be normal users. If you want other admins too, you can change their permission to admin at Admin Panel.

Note: If you get some error about email settings, you can ignore it. WORKING EMAIL IS NOT REQUIRED. Wekan works without setting up email.

Once an account has been created. Login to Wekan at https://example.com/sign-in

Registering normal users:

By default, other users can register themselves by visiting the page https://example.com/sign-up and creating an account. If you would like to disable self-registration, navigate to Admin Panel > Settings > Registration > [X] Disable self-registration. Then invite new users to selected boards by email address.

Conclusion

This has marked the end of how to install Wekan Kanban board application on CentOS 7 server. We went further and configured Nginx reverse proxy with Letsencrypt SSL certificate. This setup is qualified to be deployed in Production environments.