Table of Contents
- Testers to ping with new Wekan Edge release
- Why test?
- Who should test
- What usually happens when Wekan gets broken
- ChangeLog
- Backup before testing. And backup daily in production.
- Snap
- Docker
- Latest development version from master branch
- Example of using release tags
- How to change Docker version
- Build Docker version from source
- Sandstorm
Testers to ping with new Wekan Edge release
- All those whose issues were fixed at ChangeLog
- @saschafoerster
Those should reply to new issue that has name Test Edge Wekan (version-number-here)
at https://github.com/wekan/wekan/issues .
Why test?
https://github.com/wekan/wekan/issues/2811
Who should test
- If you are the person in your company that gets yelled at when something breaks in new version of Wekan.
- If you think xet7 releasing new version of Wekan every day directly to stable production Snap channel is in any way risky.
What usually happens when Wekan gets broken
- There is many new issues about some same new feature or bug. Yes, also when some notices new feature that is already at ChangeLog, they add issue about it, usually asking "Can this feature be turned off or made optional?". This is usually if new feature changes some old workflow radically.
- Many do tag @xet7 that are you aware of the issue.
- Someone yells at IRC that "this is too much, it's time to fork Wekan". Well, that's because he gets yelled at by all users of Wekan at his company.
- xet7 does not have time to answer those, he just fixes the issue - usually at the same day, makes new release, closes all related issues with last comment "Please try Wekan (version-number-here)".
- There is only one comment that says "This resolved things for me. Thanks for such a quick fix. This is an invaluable piece of software for me!"
- xet7 thinks this is great normal development day: Got some features added, got some bugs fixes, and happily goes to sleep well. This is because above 1-5 has happened many times before, it's just normal.
ChangeLog
https://github.com/wekan/wekan/blob/main/CHANGELOG.md
Backup before testing. And backup daily in production.
Why? Well, Wekan has no undo yet. If you delete Swimlane/List/Card, it's gone. That's why it's harder to reach in submenu. It's better to Arhive those, and unarchive.
https://github.com/wekan/wekan/wiki/Backup
You could test at other computer than your production.
Snap
Snap has automatic update, or you can update manually:
sudo snap refresh
You see at https://snapcraft.io/wekan what are current versions.
To change to Edge:
sudo snap refresh wekan --edge --amend
And back to stable:
sudo snap refresh wekan --stable --amend
Docker
docker-compose.yml
is at https://github.com/wekan/wekan .
Latest development version from master branch
Quay:
image: quay.io/wekan/wekan
Docker Hub:
image: wekanteam/wekan
Example of using release tags
image: quay.io/wekan/wekan:v3.55
image: wekanteam/wekan:v3.55
How to change Docker version
- Backup first https://github.com/wekan/wekan/wiki/Backup
docker-compose stop
docker rm wekan-app
- Change version tag. Then:
docker-compose up -d
Build Docker version from source
At docker-compose.yml is these lines:
#-------------------------------------------------------------------------------------
# ==== BUILD wekan-app DOCKER CONTAINER FROM SOURCE, if you uncomment these ====
# ==== and use commands: docker-compose up -d --build
#build:
# context: .
# dockerfile: Dockerfile
# args:
# - NODE_VERSION=${NODE_VERSION}
# - METEOR_RELEASE=${METEOR_RELEASE}
# - NPM_VERSION=${NPM_VERSION}
# - ARCHITECTURE=${ARCHITECTURE}
# - SRC_PATH=${SRC_PATH}
# - METEOR_EDGE=${METEOR_EDGE}
# - USE_EDGE=${USE_EDGE}
#-------------------------------------------------------------------------------------
Uncomment from those this way:
build:
context: .
dockerfile: Dockerfile
args:
- NODE_VERSION=${NODE_VERSION}
- METEOR_RELEASE=${METEOR_RELEASE}
- NPM_VERSION=${NPM_VERSION}
- ARCHITECTURE=${ARCHITECTURE}
- SRC_PATH=${SRC_PATH}
- METEOR_EDGE=${METEOR_EDGE}
- USE_EDGE=${USE_EDGE}
Then start Wekan to http://localhost this way:
docker-compose up -d --build
Sandstorm
-
Install local development version of Sandstorm to your laptop from https://sandstorm.io/install
-
Download and install experimental version to your local Sandstorm: https://github.com/wekan/wekan/wiki/Sandstorm Local sandstorm is at http://local.sandstorm.io:6080/ .
-
Download your production Wekan grain .zip file with down arrow button. Upload to your dev local Sandstorm. Try does it work.
Wekan
General
- Deep Dive Into WeKan
- Meteor WeKan Roadmap - board at Wekan demo
- Multiverse WeKan Roadmap
- Docs/Manual
- Change Language
- Forgot Password
- About
- Test Edge
- WeKan Design Principles
- FAQ
- IRC FAQ - answers to questions asked at IRC
- Team
- Press
- Blog
- Wekan vs Trello vs Restyaboard
- Results of Survey 2020-01
Fake: Not WeKan kanban
Security
- Allow private boards only: Disable Public Boards
- Security Disclosure and details of Security in Wekan
- Security issues
- Password Hashing
Scaling
- Cron: Hourly restart WeKan, because of memory leaks
- Maybe: Add more RAM to Node.js to prevent crash
- Clustering AWS etc
- Scaling
- Kubernetes
- Redis Oplog
- Meteor Scaling at Meteor Cloud
- Scaling at Meteor forums
Migrating
- From Previous Export, paste big WeKan JSON
- Progress: Import/Export/Sync
- From CSV/TSV
- From Trello
- From Jira
- From Asana
- From Zenkit
- From old Wekan manually
- Converting Meteor Stylus to CSS
Support priorities for new features and bugfixes
Backup
Repair
- Repair MongoDB
- Using Meteor MongoDB to repair files
- If board does not open and keeps loading
- Repair Docker
Themes
Markdown Syntax
- Wekan Markdown
- Emoji
- Mermaid Diagram DOES NOT WORK ANYMORE
- Numbered text
Login Auth
- Automatic login
- Disable Password Login
- Forgot Password
- Admin: Impersonate user
- Adding Users
- Active users Presence
- Accounts Lockout: Brute force login protection
- LDAP
- LDAP AD Simple Auth
- Keycloak
- Google login
- Azure
- OAuth2, Auth0, GitLab, RocketChat
- Oracle OIM on premise using OAuth2
- ADFS 4.0 using OAuth2 and OpenID
- Azure AD B2C using OAuth2
- Nextcloud
- CAS Please test
- SAML Please test
- Zitadel
Metrics, Logs, Stats
Integrations
Time
Features
- Multiline
- Linked Cards
- Drag Drop on Mobile and Desktop
- Rclone: Store attachments to cloud storage like S3, MinIO, etc
- Python based features
- Burndown and Velocity Chart
- Wait Spinners
- Translations
- Default Language for All Users
- Roadmap
- Features
- Planning Poker
- Scaling
- Custom Logo
- Subtasks <== Has fix
- Templates
- Cover
- Archive and Delete
- Custom Fields
- Fix Export board menu not visible on some boards
- RAM usage
- Demo
- Swimlane Documentation
- Customize Translations
Required Settings
Download
- Download Wekan for various Platforms: Supported by xet7, Operating Systems, NAS, Cloud
- Helm Chart for Kubernetes
Webservers
- Caddy
- Nginx
- Apache
- OpenLiteSpeed
- Local self signed TLS
- Let's Encrypt and Google Auth
- TLS with Node.js
- Traefik and self-signed SSL certs
REST API Docs
REST API issue
REST API client code
- Example: New card with Python3 and REST API
- Python client to REST API
- Go client to REST API
- Java
- Wekan Sandstorm cards to CSV using Python
- Excel and VBA
Webhooks
- Global Webhook
- Limiting Webhook data
- Receiving Webhooks
- Outgoing Webhook to Discord/Slack/RocketChat/Riot
- Outgoing Webhook to NodeRed
- Outgoing Webhook to PowerShell
- Security: Webhook and CA
- Outgoing Webhooks Data
- Outgoing Webhooks and Let's Encrypt
- Outgoing Webhooks Original Pull Request, multiple Webhooks, more parameters and response order
Case Studies
Development
- Kadira integration
- Debugging
- Developer Docs for Standalone Wekan
- Developer Docs for Sandstorm Wekan
- Adding new Snap setting to code
- Directory Structure
- Building Wekan for Sandstorm
- Docs - Sandstorm etc
- Beginner
- Maintainer FAQ
Issues
Wekan - OpenSource Kanban