Tigris setting bucket path in client

Hi – I'm reading through the Tigris examples and I'm a bit confused by how they implemented their multipart upload strategy. It seems that the path is sent from the client to the server in their example. Is this not something that should be set server‑side for security (e.g. tenants/tenantId/files/content)? Maybe I'm missing something, but I ran into errors when I tried to set the path from the server. Thanks!

Solution

Answering my own question here (2 min later of course!). You can set it on the server side. I made a user error when I was trying it out before. The first param named path was tripping me up in the client‑side upload function.

Prof. Hertha Jacobson OP•1/21/26, 3:12 PM

I am glad you figured it out. Is there something you think we can improve to prevent anyone else from tripping?

Dr. Jarred Schneider OP•1/21/26, 3:12 PM

Hi – Thanks for getting back to me. I think the docs could just be a bit clearer on this (e.g. calling out that it’s the file name as the first param, not the path that you are uploading to).

Also, saw the episode on the Database School podcast – super interesting to hear about the journey!

Dr. Reece Feeney OP•1/21/26, 3:12 PM

Thanks for the suggestion, I have updated the documentation to make it easier to follow. We have also simplified server logic to handle the client uploads. You can check the example here:

Dr. Jarred Schneider OP•1/21/26, 3:12 PM

Looks great! Thank you.