Great update @zef .
One minor edit in the first section the sentence "I think what’s there is prety solid and what it needs most now is tuning and polish" should probably read as "I think what’s there is pretty solid and what it needs most now is tuning and polish"
Haven't tried the multi-space setup yet, but I'm curious: is this supposed to enable me to spawn only one SB server instance and serve many spaces at possibly distinct locations simultaneously? Or, is the emphasis on my being able to create many spaces and many accounts but all within the same folder on my machine?
By the way @zef , in those ADR pages on the silverbullet.md website, are you using some sort of agent harness to verifiably control development and create context? Is this standard practice from any famous workflow or a consequence of any specific harness / context tool?
The automatic update (using the latest tag) failed on both of my instances, so I went back to 2.9.0. I've tried a fresh install with docker compose, but nothing I do will bring up any kind of configuration page. It looks like it automatically defaults to single-space mode. I'm looking forward to the updates, and really appreciate your work. I just hope somebody here can advise on any needed docker compose changes for the new version.
@jeff this post is probably not the best place for support. Can you create a topic in Troubleshooting or a GitHub issue? For sure I’d be interested in server log output, the server should clearly state what it’s running in. What COULD be an issue is old service workers (if you’re deploying SB in multi space mode whereas there was single server running previously), in that case try incognito mode to see if that changes things.
Thank you for responding so quickly. I managed to get it working by doing a fresh install, and removing the SB_INDEX_PAGE environment variable. I then ran through the setup wizard to create my first space. I couldn't figure out how to create the second space, but eventually just modified the spaces.json file and restarted. I then migrated all my files into the new spaces, and everything seems to work fine. I'm sorry I didn't get the logs from the failed upgrade before it was too late.
I use Authentik for authentication, so I'm actually one of the few people who wish there was a way to disable the new integrated authentication. But I've been using SilverBullet for a couple of weeks now, and it's been exactly what I needed for my work. I had used Obsidian for years before this, and was always frustrated by the UI, and their attempt to do too many things. SilverBullet does just what I need it to do. Thank you for all your work on the app.
Great release !
Thanks for the job and I still love the minimalist and distraction free tool while improving productivity.
As mentionned above, would it be possible to keep some SB variable in the space
(SB_INDEX_PAGE, SB_DISABLE_SERVICE_WORKER).
Also 
,it would be nice to have a kind of limited privilege management per space :
One can imagine Admin has always access to read/write even if a space is configured as read only, while other acess are restricted in RO.
I put a work around with two instance pointing at the same data with docker and RO and RW instance, but I find space management more in integrated and transparent.
I guess this is not on the track but maybe this would be first step if one day you decide to do it....
great update! 
No issues with upgrade (Docker Image). Web and Mobile all fine.
btw: The Document Explorer looks really nice. I don´t now when he got the update, but i love it.
I don't know how multiple spaces pointing to one folder would help, so the answer is the first one: you can create multiple spaces pointing to different folders (any location available to your SilverBullet process, so if you're using docker you have to make sure they're volume mounted).
I'm using the docs/ folder in the SilverBullet repo as a kind of "show case" or test bed for the docs as code approach (for which I think SB is a great editor). One part is that I indeed retroactively extracted ADRs for past architectural decision and put them in there, as you can see. I didn't use any particular agent harness for this, just standard tools.
Have a look at Space%20Manager as you can see there, you can mark a space as public, which would remove any SB-level authentication (only leaving any additional authentication layer you put on top, so in your case Authentik).
Also, as mentioned there, you can always access your spaces list/admin area via https://yourhost/.spaces
Sounds like a good feature suggestion for you to create as a Github issue 
Thanks so much for the update! I have some questions for how to do stuff in the new version with SB_ environment variables. These will still work in multi-space mode?
SB_LOCKOUT_LIMIT=5
SB_LOCKOUT_TIME=21600
SB_REMEMBER_ME_HOURS=9999
Are there plans to let us configure these in a json file like the per-space settings?
Those were broken for the release, but have since been readded at a server level (still as env variables). You can try it on the edge releases.