Configure the Fileupload Connector¶

Caution - do not turn off

Do not deactivate the Fileupload (scratch) connector. Otherwise, other connectors do not work!

The Fileupload (scratch) connector represents the panel My Documents in the user interface. After the installation, the connector is already activated. To ensure this has been done correctly and to specify the connection keys, execute the following steps.

Export the complete configuration of SEAL Operator from Consul to a YAML file. This ensures that you edit the current configuration.
```
operator config export <filename>.yml --insecure
```
Edit the exported file <filename>.yml.

In the section of the Fileupload (scratch) connector, check if cstatus is set to on.

operator:
  connectors:
  ...
    scratch:
      cstatus: 'on'
      serviceName: operator-fileupload
      url: 'https://localhost:3009'
  ...

In the env section, specify the following keys for the seal-operator-fileupload service in the operator-fileupload section:
- MONGO_FILEUPLOAD_URL: URL of the MongoDB for file uploads into My Documents
```
env:
  service:
    ...
    operator-fileupload:
      tag:
        any:
          MONGO_FILEUPLOAD_URL: 'mongodb://<mongodb_server>:27017/operator-fileupload'
    ...
```
Literature - keys

For further information about available keys, refer to the Key Reference.
Save the <filename>.yml file.

Re-import the file to Consul.

operator config import <filename>.yml --insecure

Large Files and High-Throughput Scenarios¶

SEAL Operator itself enforces no hard limit on the maximum file size. Some scenarios must handle large files, for example multi-GB uploads. Others must handle a high number of concurrent uploads. For these scenarios, the recommended backend for file contents is Simple Storage Service (S3) instead of MongoDB. For details on how to configure S3, refer to Simple Storage Service (S3).

Next Step¶

Continue with: Connect a Backend System