-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Activate wolfram engine from the WLJS #192
Comments
Probably it is a bug. It should be possible to activate Engine from WLJS, a special form should appear in such case. Could you, please, show the screenshot from the launcher? Docker, yes, we also tried in this direction. Good idea. Another possibility would be to also implement automatic activation using somewhat like temp-mail API… |
I will post here the current state of Docker image We have now a Docker file made by Roman Dyakov
and a configuration file
The only problem we have now is how to activate WL. There is a solution from WRI, but it is quite cumbersome (see Activate Using Node-Locked Licensing). I am not an expert on Docker, but I believe the process of activation can be automated with a user dialog somehow... |
stale |
Is your feature request related to a problem? Please describe.
I want to package the wolfram engine and WLJS into a docker image that I can share with some friends. Unfortunately, this is not currently possible as wljs cannot launch until the engine has been activated. At least that happens to me when following the instructions on this repo.
Describe the solution you'd like
Ideally they would just docker run my image, and go to the specified port on their browser, from where they could activate the engine with their id.
The text was updated successfully, but these errors were encountered: