Twake
Twake copied to clipboard
setup for twake in development environment
Is there any update documentation to setup twake in development environment because the one given here seems outdated and is not following correctly.
Hi ! This one seems to be up to date, could you tell me what is blocking for you ? :)
the only thing that changed is the backend port, it's 4000 now instead of 3000.
for the setup here are the steps:
1 - clone the repository and switch to the develop branch:
git clone https://github.com/linagora/Twake.git
cd Twake
git checkout develop
export TWAKE_HOME=$(pwd)
2 - install the frontend dependencies ( you should use node 14+ ):
cd $TWAKE_HOME/twake/frontend
npm install
3 start the mongo dev container:
cd $TWAKE_HOME/twake/
docker-compose -f docker-compose.dev.mongo.yml up -d
4 change the frontend environment file:
create or edit the following file $TWAKE_HOME/twake/frontend/src/app/environment/environment.ts
export default {
env_dev: true,
env_dev_auth: 'internal',
sentry_dsn: false,
front_root_url: (document.location.protocol || 'http') + '//' + document.location.host,
api_root_url: (document.location.protocol || "http") + '//' + document.location.host,
websocket_url: 'ws://localhost:4000'
};
5 - start twake
cd $TWAKE_HOME/twake/frontend
npm run dev:frontend
I tried the same above steps again but this error on docker came up and after running thisnpm run dev:frontend
this error came up : FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
.
I tried running export NODE_OPTIONS=--max-old-space-size=8192
this but no luck
This problem relevant. There is no way to help with the development of this product. Because there is no actual instruction on how to run it.
Could you indicate your machine specifications ? I don't see any reason why nor the frontend nor the backend would start, we are not using very big machines ourselves to develop on Twake :)
i use Windows + docker proc: i7 10700 ram: 32 gb
7:20:48 PM - Found 0 errors. Watching for file changes.
[nodemon] 2.0.4
[nodemon] to restart at any time, enter `rs`
[nodemon] watching path(s): *.*
[nodemon] watching extensions: js,mjs,json
[nodemon] starting `node --inspect=0.0.0.0 ./dist/server.js`
Debugger listening on ws://0.0.0.0:9229/ea0b2a96-a535-491b-8b70-58e3f43808a6
For help, see: https://nodejs.org/en/docs/inspector
node:internal/modules/cjs/loader:1239
return process.dlopen(module, path.toNamespacedPath(filename));
^
Error: /usr/src/app/node_modules/bcrypt/lib/binding/napi-v3/bcrypt_lib.node: invalid ELF header
at Object.Module._extensions..node (node:internal/modules/cjs/loader:1239:18)
at Module.load (node:internal/modules/cjs/loader:1033:32)
at Function.Module._load (node:internal/modules/cjs/loader:868:12)
at Module.require (node:internal/modules/cjs/loader:1057:19)
at require (node:internal/modules/cjs/helpers:103:18)
at Object.<anonymous> (/usr/src/app/node_modules/bcrypt/bcrypt.js:6:16)
at Module._compile (node:internal/modules/cjs/loader:1155:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1209:10)
at Module.load (node:internal/modules/cjs/loader:1033:32)
at Function.Module._load (node:internal/modules/cjs/loader:868:12) {
code: 'ERR_DLOPEN_FAILED'
}
[nodemon] app crashed - waiting for file changes before starting...
Could you indicate your machine specifications ? I don't see any reason why nor the frontend nor the backend would start, we are not using very big machines ourselves to develop on Twake :)
I am using a laptop with ryzen 5 3500U , 8gb ram
For this error in particular it looks like you did a « npm install » from your host machine and not from the docker container (so some libs are built for windows instead of Linux which is the OS inside the docker container).Try removing node_modules and then do this:docker-compose run node npm install
On 19 Nov 2022, at 21:01, Harshdeep @.***> wrote:
Could you indicate your machine specifications ? I don't see any reason why nor the frontend nor the backend would start, we are not using very big machines ourselves to develop on Twake :)
I am using a laptop with ryzen 5 3500U , 8gb ram
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
For this error in particular it looks like you did a « npm install » from your host machine and not from the docker container (so some libs are built for windows instead of Linux which is the OS inside the docker container).Try removing node_modules and then do this:
docker-compose run node npm install
On 19 Nov 2022, at 21:01, Harshdeep @.> wrote: Could you indicate your machine specifications ? I don't see any reason why nor the frontend nor the backend would start, we are not using very big machines ourselves to develop on Twake :) I am using a laptop with ryzen 5 3500U , 8gb ram —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.>
Thanks, it worked. When do you plan to add Calendar and Tasks ?
For now we are working on the documents / drive feature. Then Tasks will follow.The calendar is built by an other team outside of Twake, this same team is also working on an email app (Team Mail).On 19 Nov 2022, at 21:52, laktarik @.***> wrote:
For this error in particular it looks like you did a « npm install » from your host machine and not from the docker container (so some libs are built for windows instead of Linux which is the OS inside the docker container).Try removing node_modules and then do this:docker-compose run node npm installOn 19 Nov 2022, at 21:01, Harshdeep @.> wrote: Could you indicate your machine specifications ? I don't see any reason why nor the frontend nor the backend would start, we are not using very big machines ourselves to develop on Twake :) I am using a laptop with ryzen 5 3500U , 8gb ram —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.>
Thanks, it worked. When do you plan to add Calendar and Tasks ?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>