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
When using tools to sync the vault, it could be annoying to have a giant configuration file. In my case, saving 30 images (150mb) in base64 in the data.json file is a problem, for syncing and debugging. Therefore my question:
If you already have a separation between "Local Images" and "Vault Images" - why not just link Vault images, because they're gonna be there anyways instead of importing and encoding them? CSS should make that fairly simple, right?
The text was updated successfully, but these errors were encountered:
When using tools to sync the vault, it could be annoying to have a giant configuration file. In my case, saving 30 images (150mb) in base64 in the data.json file is a problem, for syncing and debugging. Therefore my question:
If you already have a separation between "Local Images" and "Vault Images" - why not just link Vault images, because they're gonna be there anyways instead of importing and encoding them? CSS should make that fairly simple, right?
The text was updated successfully, but these errors were encountered: