Choosing the stack

[wordpad25]

Blog post here answers a lot of questions:
https://dev.to/mpiorowski/breaking-the-myth-scalable-multi-region-low-latency-app-exists-and-will-not-cost-you-a-kidney-537a

[cmjoseph07]

@mpiorowski

Can I ask what your IDE setup looks like? Currently I just attach to the container through vscode but have to bring up a wsl instance initially. What would you suggest?

[mpiorowski]

Hmmm, strange one. It shouldn't be a problem, cos I've removed the node_modules from volumes in docker-compose, so its build and used only inside linux container :/ But the WSL part is a little bit tricky for me, don't know it well.

If this is still a problem, can you open a separate discussion? Maybe i can help somehow.

For reference:

services:
  client:
    container_name: sgsg-client
    build:
      context: ./client
      target: dev
    volumes:
      - ./client/src:/client/src
      - ./client/.svelte-kit:/client/.svelte-kit
    ```

[cmjoseph07]

If node_modules is only being built in the container how are you editing the code in the local file system via your ide without errors? If I dont run npm install locally my env goes crazy with errors unless I attach to the container. Additionally I am unable to see any git updates from the container since the git file lives outside of it in the parent file.

This happens on my mac as well after just checking.

[mpiorowski]

I just npm i inside client folder, and cos its not connected to docker in any way, it doesnt affect me

[mpiorowski]

So the local node_modules is a totally sepearate and not connected node_modules that are beeing used for docker. The local one is used for ide to not throw errors everywhere, the one in docker is used for libs ;p

[cmjoseph07]

Ahhh I ended up updating the docker-compose and Dockerfile to wait check node_modules after the volume is mounted:

'''
CMD [ -d "node_modules" ] && npm run dev || ( npm install && npm run dev)
'''

This allows us to not have to do any weird copying of node_modules or having to have node locally to run npm i in client. Additionally we do no weird volume binding that some suggest when dealing with this so if you have new deps you only need to erase node_modules. This also ensure your ide is error free from typing/def issues.