Closed ashishkarki closed 2 weeks ago
I had an English test last Monday and haven't had a chance to come back to this and any coding till today, Saturday, late morning.
That being said, I have been looking at the stacks of various jobs, especially the backend ones that I like and comparing it with the stack here and doing some thinking in terms of if:
focus on completing an end-to-end MVP first with nest, next, GraphQL,
etcSo, i gave up on the idea of running localstack with docker-container based nestjs or any other service since i can running to connection issues.. uninstall localstack and its deps from my machine. Might look into doing this with MinIO, OpenFaas etc
toolset
How LocalStack Works Locally (Without Docker)
You can install LocalStack directly on your machine without Docker by following these steps:
Step 1: Install LocalStack via pip LocalStack can be installed as a Python package via pip:
pip install localstack
Step 2: Start LocalStack Locally
Once installed, you can start LocalStack directly on your machine:
localstack start
This will run LocalStack and expose services like S3, DynamoDB, and Lambda on localhost:4566, which can be accessed by your locally running NestJS app.
Step 3: Update .env File
Update your NestJS environment to point to localhost:
AWS_ENDPOINT=http://localhost:4566
Now, the NestJS app running locally can directly connect to LocalStack at http://localhost:4566, avoiding any Docker-related networking issues.
Would This Have Prevented Issues?
http://host.docker.internal:4566
(which routes Docker containers to the host machine).