Arch Linux User Repository

Thanks. I forgot to move it from depends=() after they stopped depending on deno at run time.

This is missing make dependencies to be able to build properly.

It seems to work with:

makedepends=('go' 'deno' 'git')

I had a problem starting silverbullet after the update to deno 2.0. It crashes with this message:

TypeError: Deno.openKv is not a function

Further up in the logs I found the reason:

The `--unstable` flag has been removed in Deno 2.0. Use granular `--unstable-*` flags instead.

So in the systemd service file in ExecStart= we have to replace --unstable with --unstable-kv.

@unwitting, I see the appeal of being able to manage your notes through both the web interface and a local text editor.

Wouldn't a simpler solution work for you, like the combination of:

# /etc/systemd/system/silverbullet.service.d/mode.conf
[Service]
Umask=007
StateDirectoryMode=0770

, adding yourself to the silverbullet group, and symlinking /var/lib/silverbullet to e.g. ~/doc?

Or even just:

# /etc/systemd/system/silverbullet.service.d/user.conf
[Service]
User=my-user

I can of course add the user service, but I won't be using it and it will bitrot over time. Since most of us have many secrets accessible to our primary UNIX users, along with access to sudo/polkit/etc, it's best to avoid running network daemons under it.

And if you have to switch to a different UNIX user to edit your notes, you might as well switch to silverbullet.

Maybe there's something else I'm missing?

Hi, @unwitting,

Thanks for the write up.

I upgrade to 0.9.4 with @tarball's PKGBUILD, and /etc/default/silverbullet is not overwritten by default. So I think my problem is solved.

@showgood163 To have my own config and custom folder I did:

• copy /usr/lib/systemd/system/silverbullet.service to /usr/local/lib/systemd/user/silverbullet.service

• change ExecStart line to

ExecStart=/usr/bin/deno run --allow-all --unstable /usr/lib/silverbullet/silverbullet.js --hostname ${HOST} --port ${PORT} ${SB_FOLDER}

• change EnvironmentFile line to:

EnvironmentFile=%h/.config/silverbullet/config.env

• change WantedBy line to:

WantedBy=default.target

• remove DynamicUser=yes

• create ~/.config/silverbullet/config.env file with your config

HOST=localhost
PORT=3001
SB_FOLDER=/path/to/your/notes/folder

• enable and start the service as user

$ systemctl --user enable silverbullet.service
$ systemctl --user start silverbullet.service

@tarball - Can --user unit file in /usr/lib/systemd/user/silverbullet.service be part of the package?

Thanks for the report, it should be fixed now.

Hi there!

Is it possible to keep the modified /etc/default/silverbullet by default during installation? The current installation directly replaces the this with the one in the package, and you have to manually redo the configuration after updating the silverbullet.

Thanks for your testing.

Yes, I got 0 errors caused by build() in all pikaur -S runs.

I've updated my response to reflect the RAM limitation in that github issue.

I ran a few more tests on a 512 MB VM, and on a more beefy system with memory limited through cgroups:

$ systemd-run --user --scope --property MemoryMax=256M makepkg -srifc

There were no problems with memory limits down to 90 MBs (below that it starts crashing with out of memory errors — but no test failures because it doesn't even get to running tests).

It might be worth mentioning in that github issue that you're doing this on a resource-constrained system anyway.