66bac259a8
The ${env:XDG_DATA_HOME} variable is not used, as this variable resolves
to the current working directory within Visual Studio Code's development
container. By manually specifying the file path, it is possible to use
Visual Studio Code's development container.
The "mkdir" command uses the "-p" flag. This flag creates the parent
directories, as well. Should they already exists, the command moves
down to the next folder to create without throwing an error.
The "-r" parameter of the "cp" is required to recursively copy all
files and directories within the "publish" directory.
19 lines
1020 B
JSON
19 lines
1020 B
JSON
{
|
|
// jellyfinDir : The directory of the cloned jellyfin server project
|
|
// This needs to be built once before it can be used
|
|
"jellyfinDir": "${workspaceFolder}/../jellyfin/Jellyfin.Server",
|
|
// jellyfinWebDir : The directory of the cloned jellyfin-web project
|
|
// This needs to be built once before it can be used
|
|
"jellyfinWebDir": "${workspaceFolder}/../jellyfin-web",
|
|
// jellyfinDataDir : the root data directory for a running jellyfin instance
|
|
// This is where jellyfin stores its configs, plugins, metadata etc
|
|
// This is platform specific by default, but on Windows defaults to
|
|
// ${env:LOCALAPPDATA}/jellyfin
|
|
// and on Linux, it defaults to
|
|
// ${env:XDG_DATA_HOME}/jellyfin
|
|
// However ${env:XDG_DATA_HOME} does not work in Visual Studio Code's development container!
|
|
"jellyfinWindowsDataDir": "${env:LOCALAPPDATA}/jellyfin",
|
|
"jellyfinLinuxDataDir": "$HOME/.local/share/jellyfin",
|
|
// The name of the plugin
|
|
"pluginName": "Jellyfin.Plugin.Template",
|
|
} |