Developing Wekan for Sandstorm

So it seems like the new version is too heavy for our sandstorm server

** SANDSTORM SUPERVISOR: Starting up grain. Sandbox type: privileged
** Starting Mongo...
2019-08-20T01:07:31.289+0000 I STORAGE  Engine custom option: log=(prealloc=false,file_max=200KB)
about to fork child process, waiting until server is ready for connections.
forked process: 10
child process started successfully, parent exiting
** Starting Meteor...
Presence started serverId=gaFBDgwtcjdPDfTwG
Meteor APM: completed instrumenting the app
** SANDSTORM SUPERVISOR: Grain still in use; staying up for now.

Grain log

Say that, I have wekan source code on my sandstorm machine.

Is it possible for me to use spk dev to run wekan sandstorm version in development mode?

Too heavy? How much RAM is at Sandstorm server?

Is server swapping?

I don't think using development mode would bring any difference. It just builds Wekan and starts it as it would start current version of Wekan.

I think command is meteor-spk dev

before that you should ./rebuild-wekan.sh with option 2

more info is at Wekan GitHub wiki sandstorm dev docs

The server was swapping

My object is to find what's the difference between standalone and sandstorm version

So I'll write many logs, thus I need development mode for efficiency.

I succeed using meteor-spk dev, I need to Ctrl-C and rebuild everytime when I change code, right?

Yes I think so

If server is swapping, it does not have enough RAM

that makes everything super slow

You should run Wekan on server that has enough RAM

rebooting server can help temporarily, but when loading big board, most likely it starts swapping again, if you don't change to server that has more RAM

But the old version works well

That from June or July

So I think my code or some new code has some wrong memory usage

That old version uses Meteor 1.6.x and new version uses Meteor 1.8.1 so there are very many updates and security fixes to all dependencies. Currently all Wekan platforms use Meteor 1.8.1, I don't think it would make any sense to go some older version.

Instead, I plan to continue updating dependencies to newer versions where possible.