Merge pull request #14723 from filamentphp/export-dynamically-swap-pu…

…blic-for-local-disk

docs/01-installation.md

@@ -112,6 +112,12 @@ class User extends Authenticatable implements FilamentUser
 
 Learn more about [users](users).
 
+### Using a production-ready storage disk
+
+Filament has a storage disk defined in the [configuration](#publishing-configuration), which by default is set to `public`. You can set the `FILAMENT_FILESYSTEM_DISK` environment variable to change this.
+
+The `public` disk, while great for easy local development, is not suitable for production. It does not support file visibility, so features of Filament such as [file uploads](../forms/fields/file-upload) will create public files. In production, you need to use a production-ready disk such as `s3` with a private access policy, to prevent unauthorized access to the uploaded files.
+
 ## Publishing configuration
 
 You can publish the Filament package configuration (if needed) using the following command:

docs/15-upgrade-guide.md

@@ -193,7 +193,7 @@ When using simple resources, remove the `CanCreateRecords`, `CanDeleteRecords`,
 
 We also deprecated type-specific relation manager classes. Any classes extending `BelongsToManyRelationManager`, `HasManyRelationManager`, `HasManyThroughRelationManager`, `MorphManyRelationManager`, or `MorphToManyRelationManager` should now extend `\Filament\Resources\RelationManagers\RelationManager`. You can also remove the `CanAssociateRecords`, `CanAttachRecords`, `CanCreateRecords`, `CanDeleteRecords`, `CanDetachRecords`, `CanDisassociateRecords`, `CanEditRecords`, and `CanViewRecords` traits from relation managers.
 
-To learn more about v2.13 changes, read our [blog post](https://filamentphp.com/blog/v2130-admin-resources).
+To learn more about v2.13 changes, read our [blog post](https://v2.filamentphp.com/blog/v2130-admin-resources).
 
 #### Blade components