Closed fonsp closed 1 year ago
On windows this creates issues when users try to open the app, since Julia will try to write to the depot directory. When installed the depot directory is located in C:\Program Files
, which is readonly. Perhaps we move the depot into AppData or another writable directory.
ah shitty. But electron has API to achieve this sort of thing, right?
Yeah I created #69 to hopefully fix this issue by copying the packaged depot to AppData, it takes an extra second or two the first run but after that everything works the same.
Instead of generating a sysimage (250MB) we could also create a Julia depot dedicated to launching Pluto, prepopulate it during our build phase, and include it as our assets.
This will also really improve the app's stability: people can safely mess with their own
.julia
folder and the Pluto app will still work.We need to make sure that the Pluto notebooks still use the original DEPOT_PATH setting.
This depot is about 100MB, split down into these subfolders:
(the
compiled/Pluto
folder is 56MB)We can safely delete the
registries
folder (I tested), which will save some storage and a large number of files on Windows. Julia will not download the registries on launch.You cannot delete
packages
.You can delete
compiled
(70MB), but this will mean a slow launch.With
registries
deleted, the depot is 94MB, or 41MB after compression.