I've tried reloading vscode and dendron.

It looks like it has an uncaught error and VSCode kills it for taking too long

It's weird that the error refs v0.47.0 since I'm on 0.48.0

Could you try "Dendron:Dev: Diagnostic Report" command? You could message that to me if it works, and I can take a look at it.

thanks @User for helping solve the issue. Turns out it was a git conflict in a dendron.yml file I didn't know existed.

Is there an easy way to clean out the assets folder? I’ve been using the image paste extension, but I’d like to be able to ‘purge’ files that are in assets but not referenced

not currently if you submit a feature, we can track it on the roadmap 🙂 https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=feature_request.md&title=

I'm getting an error when I try to look at backlinks:

Cannot destructure property 'start' of 'e.position' as it is undefined.

Any idea why this might be?

what version of dendron are you using? (latest version is 0.48.1). you can run lookup to see the version

What is the best or reasonable way to setup Git? (I did look at the Team and Git notes on the Wiki but I am confused about them: e.g., what are the 'workspace vaults' and why would one have them?) At the moment, I have two only vaults, one is a GitHub repo, the other one is not yet. So, I thought I would ask before make it into one (also how? are there any dendron-specific setting one needs to know about?). dendron.yml now looks like this (by the way, it says 0.47 when the version is 0.48.1, it should be updated on upgrate, no?)

version: 1
vaults:
    -
        fsPath: vone
    -
        fsPath: vtwo

This seems incorrect as vone is on GitHub but it syncs OK. These and future vaults will be used collaboratively, possibly by different people, some might become public. Should I have a separate repo for each vault and stop at that? Should I also have one repo for the whole workspace? Is it needed? Will this lead to problems? Any tips?

It would be great to have this a bit more detailed on the Wiki. Maybe some short videos?

Also, what should the contents of .gitignore be for vaults. We have '.dendron.cache.json node_modules' because we had sync problems with the cash file. Is this right?

@User Just hoping someone can comment on the above. 🙂 Might be useful as a way to improve the docs and onboarding... Thanks

I'm on 0.48.1 - I updated and reloaded and the issue was still there

yeah, this is because we changed the cache format in 0.47.x. we have an migration script that updates the format but it’s been flaky. you can manually trigger it by deleting .dendron.cache.json from inside your vault

yeah, we have a guide on converting a local vault to a remote vault here -> https://wiki.dendron.so/notes/401c5889-20ae-4b3a-8468-269def4b4865.html#converting-a-local-vault-to-a-remote-vault the process is not as straightforward as it should be so something we're working on 😅

Thanks. I have read that. I the questions above remained after reading. So, I am keen to hear what the best path forward is

This seems incorrect as vone is on GitHub but it syncs OK. > this will work. the reason you want to add a git url to

dendron.yml

is so that when someone else clones the workspace, dendron is able to clone the vaults automatically These and future vaults will be used collaboratively, possibly by different people, some might become public. Should I have a separate repo for each vault and stop at that? > that's the normal setup for multivault. see [here](https://wiki.dendron.so/notes/45cfb9f2-46cf-4f67-a41e-834818fbd06e.html#file-layout-for-multi-vault-workspace) for the file layout Should I also have one repo for the whole workspace? Is it needed? Will this lead to problems? > the idea is to have a repo for just the top level workspace. if you have the git urls in the

dendron.yml

, someone that clones the workspace and has access to the subrepos will have them initialize automatically upon cloning the owrkspace Any tips? It would be great to have this a bit more detailed on the Wiki. Maybe some short videos? > hear you on this. will be putting out more guidelines on this over the next week Also, what should the contents of .gitignore be for vaults. We have '.dendron.cache.json node_modules' because we had sync problems with the cash file. Is this right? > yep, that's correct

super, thanks

generally, it would be great to add these 'why' and 'what for' lines to the Wiki throughout. bare settings are sometimes not enough without the context and purpose

yep, agreed. moving forward, we're looking to automate some of these steps so you could initialize in a multi vault context or convert a normal vault to a remote vault by command

A different question, can one rename an asset and have the links updated? Automated names can be enough but if one wants to give meaningful names it could be handy. This can follow the note naming principles... Not sure if needed but just thinking aloud

not currently. we have plans to make note references asset aware

![[{img}]]

. this would make it possible to rename as well since we do renames for references. this has yet to be implemented though

I just did this

and got this on reload window

what is missing?

i did not have any cross-vault links

ok, the instruction to rename the folder on the hard drive is missing here between 1 and 2

or before 1

also, this looks like a broken reference