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
So if i do a docker compose like below, the containers will all spin up and postgres is happy (at least i'm able see migrations ran and the tables are there), but when i go to the playground, I see the page, but can't do anything.
as far as i can tell it's because, when i'm creating a new store for instance, i see network call trying to POST to http://127.0.0.1:8080/stores which should really be http://127.0.0.1:6749/stores in the config below.
maybe it's a bug or maybe this just needs to be an OPENFGA_ var to pass the info in, but there's not really any guidance on how this should be handled, which seems especially problematic given the commonality of the example ports.
So if i do a docker compose like below, the containers will all spin up and postgres is happy (at least i'm able see migrations ran and the tables are there), but when i go to the playground, I see the page, but can't do anything.
as far as i can tell it's because, when i'm creating a new store for instance, i see network call trying to POST to
http://127.0.0.1:8080/stores
which should really behttp://127.0.0.1:6749/stores
in the config below.maybe it's a bug or maybe this just needs to be an
OPENFGA_
var to pass the info in, but there's not really any guidance on how this should be handled, which seems especially problematic given the commonality of the example ports.The text was updated successfully, but these errors were encountered: