-
-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Headless serving mode #21
Comments
Hi @djomphe-elyada, Does portal try to open a browser window or basically do nothing? I could add a url to the returned data which would let you know where to go. Thanks! |
Thanks djblue, I should have provided some context, here are two screenshots. I tried to configure a X server and had success through the command line with gvim, but anyways if we could use a headless mode and browse ourselves, it would ease so much more our setup! So yes, if you provide a URL and portal's server is still up to serve its UI, it would be next to perfect. |
Thanks for the specific details. I think 683c911 should fix your issue. It will catch the exception and print the url. I don't know when I'll release this fix but it will probably be soon. |
Thanks again. Browsing the provided URL resulted in a logged error:
|
Hi @djomphe-elyada, using portal via git-deps doesn't currently work because I include the clojurescript client build in the release jar but not in the git repo. I just release |
Hi, thanks a lot, this is superb, it now works for us as of |
I had a similar problem but an error wasn't thrown. I was able to figure out where to browse by evaluating |
Hi, (this looks awesome!)
I would like to know if it would make sense to launch the portal web server in headless mode, delegating to the user the responsibility of opening it up in their browser themselves.
I'm asking because we're trying to use it from a Windows WSL 2 Ubuntu image. Those images don't have windowing capabilities, only terminal capabilities. If they could just spit up the served url and port, I think we'd be fine to use portal from our Windows host chrome.
Thanks for any answer!
The text was updated successfully, but these errors were encountered: