Some Ideas regarding shared folders and home assistant task card

[Mr.Red]

Hi Cris ( @cladv ) and welcome,

I didn't wanted to spam the Introduction Topic but I wanted to respond to some of your "missing" features, with some ideas and workarounds.

@cladv

Here some of my whishlist (TODOs):

• Multiple SB instances with shared and up-to-date content. Basically all except personal notes/journaling. I believe docker mounts will allow me this.

Although not natively supported out of the box by silverbullet, but I found a workaround to use "shared files/foders" with my wife in silverbullet, and still each of us has also their "private" files too. The workaround I use is to have two space folders and two instances of silverbullet running using two different ports (:3000 and :3001 for example) and in one of the space folders to have a folder with the pages you want to share with another space, and in the other space-folder you create a SymLink to that folder. so basically the other person can see and edit/modify the files too. so basically they are synced between two separate spaces/instances. The only thing is that the two persons shouldn't edit/modify the files at the same time, otherwise you'll end up with conflicted files. although i don't know if you can spin up two instances in in the same docker container, i run my silverbullet instances inside a proxmox LXC container.

@cladv

Here some of my whishlist (TODOs):

• STT(Speech-to-Text) from my Galaxy Watch to SB. I found that the OEM recording app provide up to 10min of STT, so why not learn and build a WearOS app integrated with the SB APIs?

No Comment - I don't own a Galaxy watch

@cladv

Here some of my whishlist (TODOs):

• Again the watch, but this time powered-by the great Home Assistant. Showing a simple “tile” from a markdown sensor looks interesting and easy (ie: today tasks on my watch).

i think this is possible to create a space-lua script which updates the "sensor" using http request, and in homeassistant you can simply integrate this in your Dashboard. And from there i think it shouldn't be a problem displayinh that sensor-card on your watch.
when i will have some spare time (not in the near feature) i might take a spin at this. it sounds quiet simple to implement.

[cladv]

Thank you for your response and for your work on SB.

In my case, Im running SB as docker container. In overall I was thinking on a similar approach with the volume mounts because the symlinks created at host level are tricky inside the containers.

Regarding to the watch, build a app is new effort that at this moment I can not prioritize. But maybe in a few months depending how much I needed to improve my workflow.

In case of Home Assistant, I also think is simple.

[PeriodicallyPedantic]

Fwiw, that's the set up I have: I have actually 3 separate NFS shares (one for me, one for my wife, and one shared), and SB running twice in different docker containers. I mount our shares are our spaces, and I mount the shared share as a subdirectory of each of our spaces.

I think I might switch to using a single compose file for both SB instances, but for now they're separate, each run separately in portainer.

It works well, but my wife honestly doesn't use it much so I haven't run into a situation where we have file conflicts so idk how that gets handled.

[cladv]

Thank you. Working right now on my space but I did not try yet. (I will go as a single compose stack).

Q: Do you have the Library/zefhemel/Git available on all the containers or other from of version control?

PD: From other self-hosted sites I learn about the "wife-factor" aproval. Very important factor