portal

Stephan Renatus 2024-07-18T19:02:38.140099Z

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.

✅ 1
seancorfield 2024-07-18T19:04:09.799189Z

Use portal.api/start instead of portal.api/open

Stephan Renatus 2024-07-18T19:04:28.047299Z

that’s it? 😮

Stephan Renatus 2024-07-18T19:04:29.262899Z

thanks!

Stephan Renatus 2024-07-18T19:04:34.342669Z

😃

seancorfield 2024-07-18T19:05:49.106069Z

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.

Stephan Renatus 2024-07-18T19:06:31.396749Z

it works beautifully

Stephan Renatus 2024-07-18T19:06:37.966259Z

thanks again

👍🏻 1