This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-07-18
Channels
- # babashka (9)
- # beginners (47)
- # cider (4)
- # clerk (3)
- # clojure (89)
- # clojure-australia (2)
- # clojure-europe (38)
- # clojure-india (2)
- # clojure-losangeles (3)
- # clojure-nl (1)
- # clojure-norway (6)
- # clojure-uk (30)
- # conjure (1)
- # cursive (3)
- # datomic (7)
- # figwheel-main (2)
- # fulcro (2)
- # helix (9)
- # honeysql (31)
- # humbleui (5)
- # hyperfiddle (19)
- # inf-clojure (12)
- # jobs (2)
- # lsp (4)
- # malli (10)
- # missionary (5)
- # off-topic (17)
- # portal (9)
- # releases (1)
- # remote-jobs (22)
- # scittle (14)
- # tools-deps (7)
- # uncomplicate (11)
- # xtdb (2)
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.
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 ✨