Local mounts docker install (with UID/GID 1000) starts with typesense only in docker volume

[alexk7110]

I've updated to the latest 0.9.1 version, without reading the release notes first... I know, I know... of course I went through the steps that you luckily mention and fixed the whole thing while I noticed that typesense would throw an error at startup while on a bind mount to a directory that has owner of 1000:1000 and of course the same env var on docker compose.
Later I figured that a docker volume would be appropriate for any permission hurdles, and sure enough that worked so now I get proper search results.
Should bind mounts work or is the typesense dir different. Or maybe is it just me ?
I'm posting here first before submitting a proper issue since I feel that messing the proper upgrade could have messed a step along the way.

[brufdev]

It's always important to back up before updates, but there are no breaking changes in v0.9.0.

You can use bind mounts for Typesense data too. That's how I have it here. The only thing I'm intrigued by is that Typesense error you got, but let's ignore it for now and do a clean upgrade process:

1. Stop and remove the container with docker compose down
2. Create the typesense folder or remove all its contents if the folder still exists
3. Make sure it has correct permissions
4. Update your compose.yaml to use bind mount for Typesense data
5. Start the container with docker compose up -d
6. Open a container shell and run php artisan upgrade:reimport-data-into-typesense

This should work, but let me know how it goes.