Access Controls

General
1

I am aware there are basically 2 ways to run SB:

  • locally (fully private, no-brainer)
  • online (needs some sort of access control, i.e. dead simple htpassword or something like that)

But here it comes:
Is is somehow possible to control certain areas and open up other areas?
For example, could a tag public be added to some entries, and those be made accessible to the public?
Having thus basically the option to keep (most) of the notes private, but also publish some to the www for everyone to access?

I can see the main site of silverbullet.md is public but read-only (which I still have to dig in as to how that is achieved), however - the idea would be to have that, while some of the notes would still require perhaps a password (probably the only feasible as there are no ā€œusersā€ or ā€œrolesā€ afaik in SB)

I did find Authentication. However that (as I understand it) puts it all under protection, and is not controllable by, lets say, tags?

2

See Run mode

Yes, thatā€™s correct (for now)

1 Like
3

There is a longer discussion about multiple users in the Multi-tenancy thread.

If your use-case is publishing specific pages only, maybe Share will be more relevant for you?

I was also considering running a second instance of SilverBullet in read-only mode forpublic/ subfolder of my main space, but this would break [[wikilinks]] inside it

4

Also see the silverbullet-pub plug. It basically lets you export a set of notes to a static site that can be hosted separately. You donā€™t get all of the features of silverbullet, but itā€™s kind of like a built-in static site generator.

5

Thanks guys - I will explore these optionsā€¦!

6

You can read more thinking in the threads references, but hereā€™s my current state of mind:

There is a reason I called SilverBullet silver bullet. I hoped that this would be the one and only ultimate tool anybody could ever need for anything. Perhaps a bit of a high expectation. It also meant that initially I thought: at some point I need to scale this up, so that it can be used for teams for instance. For a while I tried to solve all problems at once, but it wasā€¦ too much.

Therefore Iā€™m now actively trying to limit scope. The way Iā€™m look at it now is this:

SilverBullet is a single-user personal knowledge system. You host it on a server so that you can have access to it from wherever you need it. This may be purely on localhost, or in your local network, or on the Internet. Itā€™s up to you. However, itā€™s not designed to be accessible to other people. You can get content in various ways (primarily via your keyboard, probably :wink: ) but to give other people access you have to push it out.

This may happen in various ways. There are some plugs that support this in some capacity, like GitHub - silverbulletmd/silverbullet-mastodon: Mastodon plug for SilverBullet, GitHub - silverbulletmd/silverbullet-ghost: Ghost plug for Silver Bullet, GitHub - silverbulletmd/silverbullet-pub: Publish your Silver Bullet space to the Internet and indeed Plugs/Share I donā€™t feel this nut has completely been cracked, though and Iā€™m looking at how to improve the story here next.

1 Like
7

I think it is OK as is actually.
If someone wants, the GitHub way is probably the way to go even for Multi Tenancy, since you could basically just let people push and pull from the same repo.

Presumably a note taking app shouldnā€™t become a ā€œgroup editing softwareā€, I totally follow that.

1 Like