Andreas/wekan
1
0
Fork 0
mirror of https://github.com/wekan/wekan.git synced 2025-12-16 15:30:13 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions 5

Updated AWS (markdown)

Lauri Ojansivu 2018-02-15 16:36:10 +02:00
parent 8942b4650f
commit 04b4f0ed21
1 changed files with 3 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

11
AWS.md

@ -5,16 +5,11 @@
This setup runs very well for thousands of users.
To improve scalability even more, add Redis Oplog support using AWS ElastiCache, see https://github.com/cult-of-coders/redis-oplog and https://forums.meteor.com/t/meteor-scaling-redis-oplog-status-prod-ready/30855/479
To improve scalability even more, add [Redis Oplog support](https://github.com/cult-of-coders/redis-oplog), also see related [Redis Oplog discussion forum post](https://forums.meteor.com/t/meteor-scaling-redis-oplog-status-prod-ready/30855/479). At AWS you can use AWS ElastiCache that has Redis support.
If there is other ideas to improve scalability, add info to existing issue https://github.com/wekan/wekan-mongodb/issues/2 or forum post https://discourse.wekan.io/t/cpu-utilization-problems-with-large-userbase/579/15 , there is also mentioned that smart-disconnect is already in Wekan.
For Enterprises using Wekan I really recommend participating in Wekan development, with submitting features and performance bugfixes etc upstream, having your own developers working on Wekan daily, and using Commercial Support at https://wekan.team . With the benefits you get by using Wekan, it’s time well spent.
https://blog.wekan.team/2018/02/benefits-of-contributing-your-features-to-upstream-wekan/index.html
https://blog.wekan.team/2018/02/time-well-spent/index.html
If there is other ideas to improve scalability, add info to [existing scalability issue](https://github.com/wekan/wekan-mongodb/issues/2) or [scalability forum post](https://discourse.wekan.io/t/cpu-utilization-problems-with-large-userbase/579/15) , there is also mentioned that smart-disconnect is already in Wekan.
For Enterprises using Wekan I really recommend participating in Wekan development, see [Benefits of contributing your features to Upstream Wekan](https://blog.wekan.team/2018/02/benefits-of-contributing-your-features-to-upstream-wekan/index.html), having your own developers working on Wekan daily, and using Commercial Support at https://wekan.team , as Wekan Team [already has access to high performance bare metal servers at CNCF / Packet for running high load stress tests additional testing](https://blog.wekan.team/2018/01/wekan-progress-on-x64-and-arm/index.html). With the benefits you get by using Wekan, it’s [time well spent](https://blog.wekan.team/2018/02/time-well-spent/index.html).
## Single Server Install for small teams