Skip to content

Multi site RFC#339

Closed
sureyeaah wants to merge 3 commits intosrid:masterfrom
sureyeaah:multi-site
Closed

Multi site RFC#339
sureyeaah wants to merge 3 commits intosrid:masterfrom
sureyeaah:multi-site

Conversation

@sureyeaah
Copy link
Copy Markdown

@sureyeaah sureyeaah commented Aug 14, 2020

Rendered

Addresses #222

@srid
Copy link
Copy Markdown
Owner

srid commented Aug 15, 2020

A third way of solving this is to consider #50 but in local context. Suppose there are two local zettelkastens -- private & public -- we could make it possible for one zettelkasten to (cross) link to another (but not vice versa). So "public" zettelkasten would be independent; but the "private" zettelkasten can cross link to the "public" zettels. Coming up with a spec to make this work doesn't seem exactly easy though.

EDIT: The main advantage of this approach is that the two zettelkastens are generally decoupled; any coupling that happens is done via one-way cross-linking, and there is no risk of private zettels leaking into the public zettelkasten.

@srid srid added the proposal Proposal with exact spec yet to be fleshed out label Aug 15, 2020
@srid
Copy link
Copy Markdown
Owner

srid commented Aug 16, 2020

Thinking more about cross-linking ... instead of having sub-zettelkastens, we now think in terms of composing (otherwise independent) zettelkastens.

So, if you have a zettelkasten called "public" -- and it exists as a sub-directory (or git submodule) as ./public/neuron.dhall -- then you can have another zettelkasten's neuron.dhall "point" to it as { "public" = ./public }. This another zettelkasten can now link to the public zettelkasten using an ID prefix. For example, to link to ./public/foo.md - you would write <public:foo>. Its graph would include the zettels from "public" but with this ID prefix. The generated HTML would go in a sub-directory, i.e., public/foo.html.

This also solves the problem of public/index.html being in conflict with the master zettelkasten's zettel of same ID.

And it solves the constraint of "public" zettelkasten being allowed only to link to itself (unless it is configured to have cross-links)

@sureyeaah
Copy link
Copy Markdown
Author

How does this affect querying? If I query by a tag, is it supposed to query cross-links as well or is there a special syntax for choosing an ID prefix?

@srid
Copy link
Copy Markdown
Owner

srid commented Aug 18, 2020

Since both the zettelkastens will be part of the same graph, if you say query by tag - it will include zettels from both of them.

To be more precise, it is not exactly cross-linking - rather, more of "embedding" another zettelkasten into your graph ... but with IDs namespaced. Here, you would be embedding your blog zettelkasten onto your private zettelkasten.

@sureyeaah sureyeaah mentioned this pull request Aug 20, 2020
@srid
Copy link
Copy Markdown
Owner

srid commented Aug 20, 2020

Closing in favour of #355

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

proposal Proposal with exact spec yet to be fleshed out

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants