You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you start all of the services with pnpm run services:start, you will also start up planet.
However, there are some configuration issues related to the planet container, since accessing it through localhost:9876/planet gives some errors.
A few hints:
one error (ECONNECTIONREFUSED when connecting to supabase) is due to the SUPABASE_URL being pointing to localhost/v1/supabase (picked up from the .env file). We want to point to http://kong:8000, written directly in the docker/development.yml file.
another error (ECONNECTIONREFUSED when connecting to posts service), may be to a similar issue.
The text was updated successfully, but these errors were encountered:
If you start all of the services with
pnpm run services:start
, you will also start upplanet
.However, there are some configuration issues related to the
planet
container, since accessing it throughlocalhost:9876/planet
gives some errors.A few hints:
ECONNECTIONREFUSED
when connecting tosupabase
) is due to theSUPABASE_URL
being pointing tolocalhost/v1/supabase
(picked up from the.env
file). We want to point tohttp://kong:8000
, written directly in thedocker/development.yml
file.ECONNECTIONREFUSED
when connecting toposts
service), may be to a similar issue.The text was updated successfully, but these errors were encountered: