https://www.dendron.so/ logo
Not a silly question at all - for working with the...
# questions
j
Not a silly question at all - for working with the Dendron code base, we have a setup where we include the Dendron Wiki and Dev Docs as folders in the
*.code-workspace
file of our src code project (if that makes sense). That way, we can use Dendron and lookup notes in our developer docs while we work on...Dendron haha. If you wanna see the setup of the
code-workspace
file, take a look at the
folders
setup here: https://github.com/dendronhq/dendron/blob/master/dendron-main.code-workspace Not sure if this answers your question.
c
Thanks for answering. I understand that this issue is something others (like you, at dendron) are facing, too. And that you found a way to overcome that, so you can use code and notes together, but without mixing them. Regretfully, I didn't understand how did you do it. I can see your workspace config in github, but I do not fully understand it, neither I can with your explanation (soo sorry! 😦 )
j
my example was a bit complicated - what you can do is to start with having your coding workspace/folder(s) open - then from there, try running the vscode
Workspaces: Add Folder to Workspace
command, and then pick the folder of your dendron vault/notes you want to have open (you should pick the directory that contains the
dendron.yml
- then it should work. You may need to reload the window afterward
c
Oh, I see... you have several folders: one for the project you're coding and another one with dendron notes (I guess that folder contains several vaults, not just the notes related to the project?), and then, you create a VS Code workspace and then add the two folders to it. Am I right?
(this might have a follow-up question 😉 )
j
yep - give it a try, let me know if you have issues
c
Great, thanks for pointing me to the right path, @jyeung ! I now have the anticipated follow-up question: By reading that, I realised that I may not be managing dendron in the best possible way. Currently I have a workspace with several folders, all related to dendron: * dendron folder: this contains the config and is a git repo, too * one subfolder per vault. Each vault is a remote vault (git repo). Some vaults are shared with others, whereas others are private. Is there a more rational way to manage this?
j
@ccamara - for your follow up question, we actually do something similar as well to the setup you mentioned. We have separate workspaces for when we're doing some company stuff (i.e. planning exercises, etc) versus the coding workspace. We use Dendron in both workspaces - the coding one has vaults that can help while coding (Dendron wiki, developer docs), while the company-stuff workspace contains those 2 vaults + additional vaults for work related stuff.
c
Thanks for your answer @jyeung ! Still processing it
I'm a little bit confused. You say that you use dendron in both workspaces, but Dendron in workspace A has different vaults than Dendron in workspace B. How is that possible? I thought "Dendron" was a folder containing different vaults (folders). I thought the dendron root had the setup of those vaults (and other stuff), so If I added that root folder, I'd have the same setup and vaults. Obviously, I'm wrong
j
workspaces are a bit too complicated. When I say 'Dendron' - I'm referring to the application/extension, not a particular folder or workspace. So you can have VS Code (and hence Dendron) open to a vs code workspace or folder- Dendron the app will then process notes specified by that code-workspace file if it exists, otherwise if it doesn't exist, it'll process any notes in the open folder or subfolder. The requirement is that a
dendron.yml
file exists, this is how we tell if you're in a 'Dendron' compatible folder or not. > so If I added that root folder, I'd have the same setup and vaults. That's true - but from workspace B, you can just add an existing vault without adding the root folder. https://wiki.dendron.so/notes/24b176f1-685d-44e1-a1b0-1704b1a92ca0/ for some more info Hope this helps and I'm not just making it more confusing 😅
2 Views