docs: studios config for enterprise #815
Conversation
✅ Deploy Preview for seqera-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
gwright99
left a comment
gwright99
left a comment
There was a problem hiding this comment.
Only change that needs to happen in Rstudio to Ride.
Other comments are thoughts only.
|
|
||
| To use your own Wave instance for data studio management, you must configure both the Wave instance and the custom image registry settings to point to your infrastructure. | ||
|
|
||
| ### Container Registry Configuration |
There was a problem hiding this comment.
Do we need to call out the difference between this setting and the mostly-not-talked-about settings here: https://github.com/seqeralabs/wave/blob/5585f9c37200f1f8ca5d12f50927c7d70cee0abe/src/main/resources/application.yml#L49-L59
| - `data-studio/xpra` | ||
| - `data-studio/custom` | ||
|
|
||
| **Note**: Some cloud providers (like AWS) may not support dynamic registry creation, requiring manual pre-creation of these repositories. |
There was a problem hiding this comment.
Should we add pointer to https://github.com/aws-samples/amazon-ecr-dynamic-repository-creation as an example of how they could try to get some automation in place or leave it out based on the expectation that the tag/hash naming will be available by Oct 2025?
| icon: "jupyter" | ||
| tool: "jupyter" | ||
| rstudio: | ||
| repository: "registry.example.com/data-studio/rstudio:<TAG>" |
There was a problem hiding this comment.
I think this needs to be called data-studio-ride now (licensing).
| The following tools are available for Studio sessions: | ||
|
|
||
| - **jupyter**: Jupyter notebook environment | ||
| - **rstudio**: RStudio IDE environment |
The following is a POC PR to help end users configure and manage studios using self-hosted wave along with some more functionality to help with trials.