-
Notifications
You must be signed in to change notification settings - Fork 73
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
Server execution of jobs (custom execution backend) #1186
Comments
brollb
added a commit
that referenced
this issue
Nov 23, 2018
brollb
added a commit
that referenced
this issue
Nov 23, 2018
brollb
added a commit
that referenced
this issue
Mar 17, 2019
brollb
added a commit
that referenced
this issue
Mar 17, 2019
brollb
added a commit
that referenced
this issue
Sep 5, 2019
brollb
added a commit
that referenced
this issue
Sep 9, 2019
brollb
added a commit
that referenced
this issue
Sep 10, 2019
brollb
added a commit
that referenced
this issue
Sep 16, 2019
brollb
added a commit
that referenced
this issue
Sep 17, 2019
brollb
added a commit
that referenced
this issue
Sep 17, 2019
brollb
added a commit
that referenced
this issue
Sep 17, 2019
brollb
added a commit
that referenced
this issue
Sep 17, 2019
brollb
added a commit
that referenced
this issue
Sep 17, 2019
brollb
added a commit
that referenced
this issue
Sep 18, 2019
brollb
added a commit
that referenced
this issue
Sep 19, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As a simple new custom execution backend (#1185), we should support executing jobs on the server - similar to jupyter notebook.
This form of execution would be useful for demos and users running deepforge locally (trying it out).
The text was updated successfully, but these errors were encountered: