Code Studio Templates: What is studio host?

yashpuranik

Hi,

I am looking at building a code studio template with a custom entry point that is not exposed to DSS UI.

https://doc.dataiku.com/dss/latest/code-studios/code-studio-templates.html#add-an-entry-point suggests that in this situation, the URL is built as below. Where do I find what the studio-host should be?

"http[s]://studio-host:port/dip/code-studios/<project-key>/<code-studio-id>/<exposed-port>/"

Thanks,

Yash

fchataigner2

Hi,

the "studio-host:port" is merely the URL you use to access DSS. You don't need to put that in the entrypoint settings in the code studio template, though; DSS will build most of it, the only part you need to provide is the Proxied subpath one. The URL mentioned in the doc is what you'll see in the network tab of your browser, it's the url of the iframe showing the exposed http server (note: you can pop-out the code studio tab to see the url in the location bar, too)

attached is an example of how to do it for a Voila app. It's made by piggybacking on a Jupyterlab block, and the entrypoint script is hardcoded to use a Untitled.ipynb file you create in code_studio-versioned/

yashpuranik

Thanks@fchataigner2
! Co-incidentally, the use case I am working on is indeed deploying a Voila app within Dataiku!

Would you be able to share a full project zip and/or the Untitled.ipynb file you used to test this out? I keep getting a 404 error when I try using this code studio template

fchataigner2

Hi,

the attached template actually automatically adds a dummy Untitled.ipynb in the code_studio-versioned/ folder of the Jupyterlab workspace, so you shouldn't need to add it manually nor need an export of the project. If the file is absent, maybe create one manually and try. If it still doesn't work, you should open a support ticket with a diagnostic of the instance (from Administration > Maintenance > Diagnostic tool) and the full log from the Logs tab of the code studio (to start investigating the issue)

yashpuranik

Adding a "/" to the BASE_URL resolved the issue. Thank you!