These settings define the file upload limits within the system and indicate which of the File Systems is used as the primary permanent storage location.
Note: This feature is only available with the Enterprise Edition license.
Primary File Storage page
File Upload Limits
These settings govern the size of files that can be uploaded to the application:
These options usually affect Model, since users upload large data files for processing. Buffering governs the size of the chunks that the uploader will accept each time a piece of the source file is uploaded.
Note: Setting the file size too high can overload the web servers and client browser. If large files need to be imported, it is typically better to use a network reference to those files instead.
Permanent Storage
The Permanent Storage location is where content from the modeling and publication engines is stored PERSISTENTLY. This location does not handle temporary files or those used in transit. Those are handled automatically and internally by the platform. The "default" option (internal file system) is created on install and selected by default.
This functionality is key in elastic deployments (like Kubernetes), where servers are added and removed consistently.
Permanent Storage Type
To change which File System is used as the Permanent Storage location:
- Select a different option from the Permanent Storage Type drop-down and click Apply.
If the File System you want is not available on the drop-down, you may need to add it on the File Systems page. Note that File Systems with the Secure by Tenant option selected cannot be used as the Permanent Storage Type.
Warning: In Kubernetes deployments, you must use an AWS S3, Azure Blog, FTP, or NFS file system as your permanent storage location.
Transitioning File Systems
If the file system is transitioned, old files are NOT migrated to the new destination. As such, its recommended that the file system is setup as soon as possible when deploying Pyramid.