Would it make sense to proceed to activate if the user summons lookup rather than requiring a specific workspace name?

oh yeah, we did 😓 our activation logic was actually a little more convoluted then that before, now we just check for

dendron.code-workspace

file to be present. i'll update it to be case insensitive! for activating dendron without workspace, it makes sense especially since dendron can be launched separately as a standalone server. there's still a fair bit of work involved to make that work smoothly but feel free to kick it off by submitting a feature request 🙂

You got it, thanks. I don't mind the change, it would make sense to call it out in the changelog though 😅

Has anyone gone through the vulnerabilities we need for Dendron and checked if they're okay? 26 are classified as "high".

most of the vulnerabilities are duplicates of the same packages. they all fall into the category of "if dendron were a remote service, they could potentially cause denial of service due to improper checking of file size/regex"

the fix is to upgrade to the newest package versions. will be doing that end of this month

Also, running through dev setup was super easy way to go @User! The only thing I'm confused about is ... how do I use my local install of dendron in another workspace o_0

I thought it'd be in the testing section - but I can't find it in other places either: https://www.dendron.so/notes/cb22bd36-d45a-4ffd-a31e-96c4b39cb7fb

use your local install of dendron... can you elaborate? like run a local build on an existing workspace?

if that's the case, you can run

change workspace

after launching the test version

Yeah, like I have my dendron vault workspace but now I have a dendron code workspace. I don't want to install the public dendron extension at all. Is that possible - I want it to use the local version of Dendron.

Is this even possible because ... what initializes dendron in my vault workspace?

hmm, i think this will be faster through talking. want to hop on to the #748936364283920495-talk channel?

@User https://www.dendron.so/notes/45cfb9f2-46cf-4f67-a41e-834818fbd06e.html

Ah, found what the problem was earlier. The build script is failing. Will try to figure out why tomorrow ...

> Specifically for dendron-cli

> 5 error code ELIFECYCLE > 26 error errno 2 > 27 error @dendronhq/dendron-cli@0.17.0 build:

npm run compile

> 27 error Exit status 2 > 28 error Failed at the @dendronhq/dendron-cli@0.17.0 build script. > 28 error This is probably not a problem with npm. There is likely additional logging output above.

Ah ... pods-core is missing

Had to swap the build lines and now dendron-cli can compile:

> npx lerna run build --parallel --scope @dendronhq/pods-core --scope @dendronhq/seeds-core || exit 1 > npx lerna run build --scope @dendronhq/dendron-cli || exit 1

This proposal for Multi Vault support looks great to me. I would love the ability to compose a workspace from a number of vaults and keep each of those vaults as a separate repo. I would probably need two features that I can't see in this proposal: - The ability to target to a particular tag, commit or branch of a vault repo, so that I can control which version of a vault is imported into my workspace - The ability to include vaults that are hosted as private repos and require some kind of authentication to access them From the proposal, I think it is clear how multi-vaults would work inside the Dendron workspace. I am less clear about how a publishing model would work. - A user includes

vault1

and

vault2

inside a workspace and makes a lot of wiki-links between notes in each vaults. - The user wants to publish each vault separately to different locations, for example

vault1.mycompany.com

and

vault2.mycompany.com

- When publishing the vaults, would Dendron be aware that links between notes in

vault1

that point to notes in

vault2

should resolve to different domains? Hope that makes sense!

great questions. here are my thoughts > The ability to target to a particular tag, commit or branch of a vault repo, so that I can control which version of a vault is imported into my workspace we'll add an optional

branch

parameter for the vault so you can specify a particular branch to track > The ability to include vaults that are hosted as private repos and require some kind of authentication to access them this will be done using either ssh, https, or token based auth depending on how your hosting your remote repo > From the proposal, I think it is clear how multi-vaults would work inside the Dendron workspace. I am less clear about how a publishing model would work. multi-vault publishing is still evolving. one way of handling multiple domains is for each domain to have its own site configuration. a site configuration specifies the vaults and hiearchies that are published for a particular site. for notes in a separate vault/site, the behavior can either be a tooltip that says the note is unavailable (because it isn't published) or it can turn into a link to another site

something to be aware of for compatibility with the obsidian conversion thing is their intro of aliases and tags in the YAML https://publish.obsidian.md/help/How+to/Add+aliases+to+note

we've actually had this as an issue in our backlog for a little bit 😅 https://github.com/dendronhq/dendron/issues/92

The way Obsidian's aliases works actually makes compatibility really easy - in Obsidian, aliases only make the link auto-complete generate a link with display text

[[original name|alias]]

as opposed to requiring the app to resolve

[[alias]]

to

original file.md

So in essence, Dendron doesn't need to do anything extra as long as the import already works on

[[filename|display]]

links

hot damn @Licat is everywhere

Now EVERYONE knows I am two-timing Obsidian with Dendron! ARGH the humanity!

What do you use both Obsidian and Dendron for? @User

that's a quite strange combination for me