Prefix for filesystem directory does not apply into Storage::url about laravel-azure-storage HOT 3 CLOSED

As mentioned in the linked PR, I think the best solution is to use separate containers for each environment. This is definitely considered best practice with S3, and logically I see no reason why it shouldn't also be best practice with Azure Blob Storage.

from laravel-azure-storage.

As mentioned in the linked PR, I think the best solution is to use separate containers for each environment. This is definitely considered best practice with S3, and logically I see no reason why it shouldn't also be best practice with Azure Blob Storage.

Yes, separate containers for each environment should be the proper way and this is my first proposed solution, but from my company perspective, there is no reason to extra pay for local development & staging development, the best approach they provided would be local & staging sharing one container, and production for one, or else is my problem, so i got limited resources and business logic limitation to archive my goal.

Of course there is many hardcoded way can make it worked. From my perspective, I am trying to make all code standard as possible and this is the only way I able figure out. Too bad because of my client internal policy. They didn't allow any services from AWS, so S3 not the alternative option anymore.
BTW if you look into S3 adapter, they do allow the full path control because I get the idea from there.

Anyway is ok the PR is not accepted. I will fork it and point to my branch. Thanks for reply and good work.

from laravel-azure-storage.

As far as I know you shouldn't have to pay extra for separate containers within the same account - you can have as many containers as you like on any one account and the cost is based on the total size of the stored files - it's not affected in any way by the number of containers.

from laravel-azure-storage.