Join the conversation

Sign in to join this conversation, and others like it, in the communities you care about.

Wekan

Wekan is an open-source kanban board (Trello like) which allows a card-based task and to-do management.

More active conversations

Wekan / General

node version - mongo - api - best practice examples

node version - mongo - api - best practice examples

Wekan/General · January 2, 2020 at 5:45pm

Paul Verdone

1.5k

node version - mongo - api - best practice examples

Wekan / General · January 2, 2020 at 5:45pm (Edited 4 years ago)

Is there any reason that I cannot run wekan on Node 10.15.3?

Can I just use an existing mongo server and just create a new user?

Is best practice for "development only" to use mongo as localhost or do what you would normally and keep wekan on it own server and remote access mongo?

If main use case is to populate and retrieve via another app (through api) and just use wekan to display cards/lists/tasks and perhaps just signal that a task is completed, is there any best practice configurations you would suggest?

If I already have an existing invitation/registration/login/authentication/two factor in place, is it easy to just populate the user tables direct? Is there an example on how best to do this with the api? if not, directly into mongo?

Load previous messages

January 2, 2020 at 10:51pm

Lauri Ojansivu@xet7

Team

There are also more API examples at https://wekan.github.io/api/

Paul Verdone@pvcon13

instructions for installing current version of wekan said use NVM to pull in version instructions for installing current version of wekan said use NVM to pull in version 4.8

Lauri Ojansivu@xet7

Team

And Wekan-Gogs integration at https://github.com/wekan/wekan-gogs

Paul Verdone@pvcon13

which complains that fibers needs version 10.0.0

Lauri Ojansivu@xet7

Team

Hmm, I only use nvm if n does not work

Paul Verdone@pvcon13

I build node from source usually

Lauri Ojansivu@xet7

Team

There could be some current production fibers version mentioned at Dockerfile or snapcraft.yaml , that works

Paul Verdone@pvcon13

meteor whats which version of node 8.x?

8.13?

Lauri Ojansivu@xet7

Team

raspi version seems to install newest fibers https://releases.wekan.team/raspi3/maintainer-make-bundle.sh

https://github.com/wekan/wekan/blob/master/.meteor/release

also there is meteor packages of https://atmospherejs.com listed at wekan/.meteor/packages and version numbers at wekan/.meteor/versions and then npm packages of https://www.npmjs.com are at wekan/package.json and wekan/package-lock.json

And local modified packages at wekan repo directly included at wekan/packages/* for example ldap etc

https://github.com/wekan/wekan/wiki/Directory-Structure

Paul Verdone@pvcon13

do ou know a clean bash for ubuntu? I am just trying to build a test version and document it so next time I do not have to screw around with it just to make it run?

Lauri Ojansivu@xet7

Team

Current is Node 8.17.0

it's visible at Dockerfile, snapcraft.yaml etc

steps 3-5 https://github.com/wekan/wekan-maintainer/wiki/Developing-Wekan-for-Sandstorm#3-fork-wekan-and-clone-your-fork

you may need to edit rebuild-wekan.sh if you already have Node 8.17.0 and newest npm installed

Paul Verdone@pvcon13

yeah selected nvm 8.17.0

ran npm install

getting

npm install

[email protected] install /home/wekan/bundle/programs/server/node_modules/fibers node build.js || nodejs build.js

make: Entering directory '/home/wekan/bundle/programs/server/node_modules/fibers/build' CXX(target) Release/obj.target/fibers/src/fibers.o CXX(target) Release/obj.target/fibers/src/coroutine.o CC(target) Release/obj.target/fibers/src/libcoro/coro.o SOLINK_MODULE(target) Release/obj.target/fibers.node COPY Release/fibers.node make: Leaving directory '/home/wekan/bundle/programs/server/node_modules/fibers/build' Installed in /home/wekan/bundle/programs/server/node_modules/fibers/bin/linux-x64-57-glibc/fibers.node

[email protected] install /home/wekan/bundle/programs/server node npm-rebuild.js

events.js:183 throw er; // Unhandled 'error' event ^

Error: spawn npm ENOENT at Process.ChildProcess._handle.onexit (internal/child_process.js:190:19) at onErrorNT (internal/child_process.js:362:16) at _combinedTickCallback (internal/process/next_tick.js:139:11) at process._tickCallback (internal/process/next_tick.js:181:9) at Function.Module.runMain (module.js:696:11) at startup (bootstrap_node.js:204:16) at bootstrap_node.js:625:3 npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! [email protected] install: node npm-rebuild.js npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! /home/wekan/.npm/_logs/2020-01-02T23_02_09_994Z-debug.log

...

is that fiber or meteor ?