You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Manually adding a config file generated once by vuegen would be overwritten once the directory path is reselected. We should avoid this per default.
Regarding opening a streamlit report from anywhere
currently config path contain absolute paths. If report files are checked out in a shared folder which is mounted on different users file system (e.g. with user name), we need to deal with this in the shared streamlit report somehow.
I guess the easiest option would be to add to the UI or cli a pointer to a new base path and resolve the paths (/home/newuser/shareddrive/folder)
Manually adding a config file
config files will be after Os standalone installers (with a GUI) #73 is merged be saved where the report is generated, not along the folder where the used components are stored (to avoid read-only issues).
if a user extends a config, we should check that if the configpath already exist, the information is not overwritten accidentally somehow.
Regarding the generation of config paths based on a directory, I think it would be nice to enable some more features:
streamlitreport on some shared drive (e.g. OneDrive).vuegenwould be overwritten once the directory path is reselected. We should avoid this per default.Regarding opening a streamlit report from anywhere
I guess the easiest option would be to add to the UI or cli a pointer to a new base path and resolve the paths (
/home/newuser/shareddrive/folder)Manually adding a config file