node version - mongo - api - best practice examples

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?

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

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 ?

is this the solution in the code you sent?

cd bundle/programs/server npm uninstall fibers node-gyp node-pre-gyp npm install [email protected] node-pre-gyp fibers npm install npm uninstall fibers node-gyp node-pre-gyp npm install node-pre-gyp npm install fibers npm install [email protected]

Hmm, are you trying to install bundle or build from source?

For building from source, you create directory /home/wekan/repos and there clone https://github.com/wekan/wekan (or your own fork) so it will be at /home/wekan/repos/wekan

Bundle is prebuilt https://github.com/wekan/wekan/wiki/Platforms#not-exposed-to-internet-bundle-for-raspi-3-arm64-windows-and-any-nodemongo-cpu-architectures-no-automatic-updates-no-sandboxing

bundle is not full source

for x64 Linux, bundle is at https://releases.wekan.team with name wekan-VERSIONNUMBER.zip and RasPi3/4 versio is at https://releases.wekan.team/raspi3/

Bundle only needs node.js and mongodb - it does not need meteor

Meteor development can only be done at x64 Linux, because officially Meteor does not support ARM etc. But bundle can be run at any OS/CPU that has node.js and mongodb

at this point was looking for something that does not break :)

was just following this before its started going sideways

https://community.vanila.io/wekan/general/node-version-mongo-api-best-practice-examples~68ad1340-1c48-430c-a3cf-90158056eb81

Are you coding new features for Wekan? Or why you build from source?