-
Notifications
You must be signed in to change notification settings - Fork 105
Description
Context
Hello, we want to provide our users with a robust jupyterlab experience with a full login, analytics, logging, users with separate resources, etc... Nebari looked like exactly what we needed, however we use a specific version of jupyterlab called jupyterlab-cadquery. This allows our users to render cad objects in jupyterlab. We also have custom magic functions along with our base python code that is used behind the scenes. We have everything working locally, outside of nebari.
We've noticed that nebari allows you to override the docker images. So we've looked into documentation and various repositories on nebari-dev. We did find some dockerfiles and believed we found what we need to do to roll our own image. However, there is one thing that eludes us. The dockerfiles do not include an entrypoint, which could mean that when the image is instantiated, it is given a command. What this command is we have no clue, and we can not find anything in source to indicate how this is done, nor is there any documentation hinting at this.
Value and/or benefit
If this is possible to do, it would be great to get some direction or proper documentation. Our needs require this custom jupyterlab and it feels like we are most of the way there to solving this, but there is missing information preventing us from moving quickly on this.
Anything else?
Any information would be extremely helpful.
Thank you.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status