possibility start parametrized notebook server instead of only headless execution / write parametrized notebook to *.ipynb about papermill HOT 6 OPEN

Thinking of this in another way, I think without papermill we could do this with a frontend that was dedicated to doing it rather than making it part of a CLI tool.

Basically, a workflow of "click template notebook, fill in params, open". Which would also mean that you could probably write a CLI tool around this service itself.

from papermill.

A frontend is useful if you want to have users determining parameters, but say I want to run a servie, where I spin up a notebook for the user, but the parameters are determined server-side. I'd like to grab a parametrized notebook, contextualize it for the user and point her to a URL where they can access the already-contextualized notebook

from papermill.

asked in another way: say I wanted to write such a service, could I use papermill to do the heavy-lifting?

https://github.com/nteract/papermill/blob/master/papermill/execute.py#L186

seems like the right method, but it looks like it's supposed to be internal.

from papermill.

I think we could make it externally facing, then you'd probably be able to build a server extension for the notebook that does this.

from papermill.

Yes, I think having that as part of the API would be great.

from papermill.

I think we'd need to add a target-kernel option, though there's complexity with adding this. I'd like to work towards making notebook execution abstracted to executor= options where one could register a new executor option. If we start down that road I can add back to this thread with possible options based on that.

from papermill.