But my teammates should basically be creating thei...
# questionsi
idan
02/17/2022, 6:28 PMBut my teammates should basically be creating their own workspaces and adding the vault? Why should I want to share a workspace as opposed to just a vault? (not rhetorical, I'm trying to understand)
k
kevins8
02/17/2022, 6:31 PMso you can share a public workspace and then your teammates can download that workspace. when dendron initializes a workspace, it will pull in any vaults associated with the workspace.
the reason for this extra step of indirection was to better let you mix and match vaults depending on context
i
idan
02/17/2022, 6:33 PMHrm, I kinda grok it! But in our case we are only ever going to share the one vault
idan
02/17/2022, 6:34 PMI guess my question now is what, if anything, we would want to share in terms of a workspace
k
kevins8
02/17/2022, 6:34 PMfor that case, you can commit the whole workspace to git. (you'll need to remove the vault from .gitignore since we add it there by default)
kevins8
02/17/2022, 6:36 PMself contained vaults is us addressing your question (since sharing a single vault is the common case). moving forward (mid march), a vault will be a workspace and vice versa.
kevins8
02/17/2022, 6:37 PMyou can think of the current dendron workspace as a git submodule (except instead of going the submodule route, we implemented our own logic to pull in un-initialized git repos)
the next iteration of dendron workspaces (self contained vaults) will function more like a npm package (a vault is all you need and a vault can declare dependencies on other vaults)
i
idan
02/17/2022, 6:37 PMGot it. I think, the rest of the team might not adopt Dendron for their personal lives like I have, so I'm leaning towards making the repo be the vault and not the workspace, so I can use just the vault in my existing workspace, and they can do as they please
idan
02/17/2022, 6:40 PM@User I guess given that it's somewhat clear what direction this is going in, does ☝️ make sense?
k
kevins8
02/17/2022, 6:41 PMi believe so - to make sure i understand, you're using the vault in your personal workspace (which has multiple vaults?) and you want to share just this one vault with your team
i
idan
02/17/2022, 6:41 PMcorrect
idan
02/17/2022, 6:42 PMRather, I want the team to share a vault, and I would selfishly like to be able to use said vault from inside my existing workspace 😄 But if I have to fall back to multiple workspaces, I would do that too
k
kevins8
02/17/2022, 6:42 PMgot it. in that case, something to make it more convenient for your team is to convert the vault to a repo and then create a oneoff workspace for your team which pulls in that repo. you can share that workspace repo with your team which will pull in the repo on initialization.
this also lets you pull in that vault in your own workspace. this workflow [here](https://wiki.dendron.so/notes/6DZiBObwhZNYRjnokQ422.html) walks through a similar setup
kevins8
02/17/2022, 6:44 PMthis would look like the following:
- one-off workspace repo (repo)
- shared vault (repo)
- your workspace
- shared vault (repo)
- your other vaults
i
idan
02/17/2022, 6:48 PMGot it. Trying to work out what, if anything, would be configured at the workspace level that we would actually need to share
k
kevins8
02/17/2022, 6:55 PMprobably nothing intentional - currently, its just the mechanism that dendron needs in order to initialize (otherwise your team members would have to create their own workspace and then import the vault)
idan
02/17/2022, 6:56 PMThank you! Appreciate you unforking my brain!
k
kevins8
02/17/2022, 6:57 PMhaha, happy to help 🙂