File storages

File storages

On this page

File storages (fájltárolók) decide where WorkSmartHub keeps ticket attachments and component images. You can use the server's own disk or a cloud service.

Two levels#

Level Menu Who manages Used by
Workspace Adminisztráció → Fájltárolók Fájltároló Admin role in the workspace Tickets of that workspace
Application Alkalmazás → App Fájltárolók Application permission File storage admin Tickets of every workspace, and component images

Who can open the application-level page is described on Permissions and roles.

Tickets use a workspace or an application-level storage; component images use an application-level one.
The file storage of the Szerviz workspace.
An application-level storage, usable by every workspace and by component images.

Storage types#

The types offered in the dialog are those enabled in App Konfiguráció → Fájltárolók.

Type (as shown) Settings
Szerver merevlemez (server disk, Physical) No settings. Files go under the root folder set in App configuration (default FileStorage), in a subfolder per storage. Not suitable for more than one server.
Azure Blob Tároló Storage account name, account key, container name, optional root path.
Amazon S3 Bucket region, bucket name, storage class for new files, access key, secret key, optional root path.
Minio Host and port, SSL, bucket name, access key, secret key, optional root path.
Box Client ID, client secret, enterprise ID, public key ID, private key, passphrase, root folder ID.
SharePoint Site URL, document library name, tenant ID, client ID, client secret, work folder path.
Google Cloud Tároló Bucket name, project ID, client e-mail, private key, optional root path.
Fájltároló szolgáltató hozzáadása (Add file storage) with the Amazon S3 type.

Teszt checks the connection. Secrets (keys, client secrets, private keys) are write-only, exactly as for notification channels: leaving the field empty keeps the stored value; changing the target (for example the S3 region, the Azure storage account, the MinIO server, the SharePoint tenant or the type) needs the secret again in the same save; testing an edited storage needs it too. Google Cloud Storage keeps its key when the project or account changes.

Using a storage on a ticket#

In the ticket editor, Mellékletek → Fájltároló → Kiválaszt picks an application-level storage or one of the ticket's workspace that you can read. Then Fájlok kiválasztása uploads the files when the ticket is saved. Uploads are sent in chunks (25 MB by default, TicketAttachment:UploadChunkSize); a reverse proxy in front of the application must accept requests of that size.

If you change the storage of a ticket, earlier attachments stay in the old storage and can still be downloaded; new files go to the new storage. Saving a ticket deletes only the attachments the user removed. Download links stop working once the attachment is removed.

Notes for operators#

  • With Docker, keep the server disk storage's root at the default relative path FileStorage, so the files are on the data volume.
  • For several application servers, use a cloud storage: the server disk is local to one machine.
  • Invoice PDFs are kept in the ticket's storage, or in the automatic storage Számlák (automatikus); a storage that holds invoice PDFs cannot be deleted (Invoices).
  • Backups of the server disk storage are part of the data folder or volume (Upgrading, backup and restore).
Did not find what you need?

Write to us or book a call. We answer questions about features, installation and licensing.

Contact us