I’ve had a chance to put portal into a docker file today, to add some visibility into what’s going on in a demo setup (non-clojure whatsoever). For that use case, is it possible to suppress the error on portal.api/open? I don’t want to open anything, since it’s running in a container, and I rely on the user browsing to http://127.0.0.1:5678 themselves…. the https://github.com/StyraInc/opa-sdk-demos/pull/11/files#diff-b101f1873adeb531c8e7308cf6731ea325f33e20788504a3a521c4c37d274855 is here.
https://gist.github.com/srenatus/fc8431336ab5d4807bfde51720ae6f25
Use portal.api/start instead of portal.api/open
that’s it? 😮
thanks!
😃
We do this at work for one of our processes (in dev, QA, and production), along with an nREPL server, so we can connect VS Code over a VPN to production and have Portal open inside VS Code connected to the remote server.
it works beautifully ✨
thanks again