Income Sources :: Jobs :: 2022 :: HP :: Lens :: Repos :: poly-glass :: team-mo :: match-maker :: .env
⪼ Made with 💜 by realpolyglot.com
ENVIRONMENT_NAME=local-development
LOG_LEVEL=debug
MY_IP=192.168.0.59
MY_PORT=4014
API_GATEWAY_URL=http://127.0.0.1:8888
RABBITMQ_URL=amqp://127.0.0.1/lens
DEBUG=@poly/gateway*
DB_NAME=matchmaker
DB_USER=matchmaker
DB_PASS=matchmaker
DB_HOST=127.0.0.1
DB_MASTER_USER=postgres
DB_MASTER_PASS=pg-local-dev-pw
DB_LOGGER='@poly/log'
DB_LOGGING=all
MY_ENDPOINT=http://192.168.0.59:4014
MY_GRAPHQL_QUERY_URL=http://192.168.0.59:4014/graphql
MY_GRAPHQL_SCHEMA_URL=http://192.168.0.59:4014/graphql
MY_GRAPHQL_HEALTH_URL=http://192.168.0.59:4014/.well-known/apollo/server-health
JWT_PUBLIC_KEY=/Users/wmoore/Documents/polycom-labs/poly-glass/team-mo/tooling/silica-local-cloud/certs/authorizer/public/authorizer.pem.pub
[9:48 AM] Achelis, Eric
The IP in there looks like a public IP that likely doesn't route-back to an interface on your machine that can reach your containers. There is some scripting logic that attempts to determine the correct IP in the ./run.sh script in silica-local-cloud, if you look at the output of that on startup it should show which IP to use here.
[9:49 AM] Achelis, Eric
Also it may be best to set the DB_NAME to matchmaker (instead of matchmaker2), this is what I had locally because I was testing different datastores locally from from the local-cloud.
[9:50 AM] Achelis, Eric
Oh, in the local-cloud the DB_PASS is matchmaker too.
[9:50 AM] Achelis, Eric
(I think the db library will fix this, by constantly resetting the password for the user to the one you passed in, but it's probably best if they align between local-cloud and local-development.
[9:53 AM] Moore, Wil
Making all of the changes you just mentioned seemed to do the trick. I ended up finding the correct IP by going into the docker desktop and going into the "inspect" tab on the mercator container and grabbing the IP from there.