Replies: 1 comment
-
It would be cool to respect Probably would be a good idea for us to remove that line from the docs and only list exactly the parts of the XDG spec we support. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
In this particular instance, I'm trying to pre-install libraries into a docker image... an image where a users home-directory is then volume-mounted by the image at run-time.
The FAQ says:
The downside to a single directory is that one cannot have pre-installed extensions baked into the image and allow the user to persistently install their own extensions.
Reading the spec (https://specifications.freedesktop.org/basedir-spec/latest/), it talks about
$XDG_DATA_DIRS
, so I should be able to do something like:I can build an image, and that image will have valid files under
/usr/share/code-server/extensions
, however the code-server doesn't list them as installed packages... The
my-local/configuration/extensions
directory contains anextensions.json
file, and three directories:mikoz.black-py-1.0.3-universal
,ms-python.debugpy-2025.0.1-linux-x64
, andms-python.python-2025.0.0-universal
..... and yes, if I install images in a running docker image, they get installed in
~/.local/share/code-server/extensions
- which is fine, and gives persistent user configuration..... but does not provide any pre-configurationAm I miss-understanding XDG?
Am I using XDG incorrectly?
Am I on a hiding to nothing?
Beta Was this translation helpful? Give feedback.
All reactions