Replies: 2 comments 1 reply
-
Further - here's a Dockerfile that works:
..... that's - messy and 'orrible |
Beta Was this translation helpful? Give feedback.
-
I do not understand your question. If you do not want to upload the artifacts from If your extension is frontend-only (does not contain server component) you could just drop the compiled (prebuilt) assets into appropriate
Where is the question here? Does it appear in the right path but the extension does not load up?
Are you asking how to build the extension to get PyPI tarball/wheel files? You should be able to do that by running |
Beta Was this translation helpful? Give feedback.
-
I have created an extension for jupyterlab 4 [using
copier
, the extension-examples, and the develop extensions) documentation.]It works just lovely when I test it from within the extension folder..... but I can not figure out how to install it into a dockerised jupyter image.
I have zero desire to publish an in-house, bespoke, targetted extension in a public repository like pypi.org
I have two questions:
RUN pip install git+https://github.com/perllaghu/noteable-laf
, the code appears in the image:(I've followed the instructions that
copier
puts into the RELEASE.md file... up to the.... and yes, I've put a copy of my code on github, so the actual code can be seen
Beta Was this translation helpful? Give feedback.
All reactions