can anyone help with local setup
ive successfully installed postgres,redis,etc. and im also able to run the setup commands without any errors . but when i ran npx nx start, it says to go to localhost:3001, but when i went there it says unable to connect. what am i doing wrong?
28 Replies
no problems with firewalls, ive tried running my other nodejs project and it works on the browser, also the backend for twenty at 3000 gives cannot get / which means the problem isn't with backend ?
what is your configration, like os?
i tried it on ubuntu vm, and also wsl
on the vm, when i went to the front end it load indefinitely, no errors in borwser console or in terminal
and when i tried on wsl, this happens
@danny.3.
getting same issue
is it resolved ? if its resolved could you please help me to resolve it
no not yet
Hi @r, do you see any error when you run
npx nx start?no errors
is this how its supposed to look like?
`
should end with that if your front is running
it does have that, but it has other things after it
it ends with worker
looks working
you are still using a VM setup? may come from there
i used both wsl and ubuntu vm
same result
does these mean its working?
those are from the docs
but frontend at 3001 never worked
I wonder if that could come from the VM setup. Do we agree wsl is not in a vm ?
Could you provide all steps you followed in wsl?
I followed the exact steps in the documentation. Also I just found out what the problem is
This is on an ubuntu vm (8GB,2cpu), as you can see it's using almost all of the ram and this one never worked even though I waited for like an hour
My wsl also has 8gb of ram, same result
Then I tried giving it more resources, 16 gb of ram, and now it works perfectly
Turns out it wasn't having enough resources this whole time π
Does it also take around 6-7 gb to run on your machine?
front alone takes 6-7 gb yes
you can set VITE_DISABLE_TYPESCRIPT_CHECKER VITE_DISABLE_ESLINT_CHECKER in your env, that would drop to ~3gb
server is not that huge, neither the worker (you may not need it, depending on what you wanna test locally)
I tried this but it never went down to 3gb, but still less memory usage
Thanks a lot though
Maybe it's good to have this in documentation as there were no errors at all about the memory issue
Having the same issue I think, htop shows 100% memory usage. Is it really not possible to host on less than 16gb?
You can use the 1 click docker compose script to host, uses way less resources but if you plan to do local setup for development im not too sure the lowest I got so far was around 5gb memory usage
I had similar issue, I tried to increase wsl ram to 12gb but still not able to work. At the it eats up all the available memory.
If any one got it working locally?