The Universal Data Tool can be run and customized on your own infrastructure easily. This is best for users who want to keep their version of Universal Data Tool stable, and don't need new features from weekly releases. You may also want to keep your data within your network.
The Universal Data Tool builds docker containers on every new release. You can run the Universal Data Tool using...
# Starts the Universal Data Tool on port 3000 and a collaborative server on 3001docker run -d -p 3000:3000 -p 3001:3001 \-e UDT_collaborationServer_url=http://localhost:3001 \universaldatatool/universaldatatool
You can provide different options to the docker container to control various aspects of Universal Data Tool. Below is a table of a few of the configuration parameters can customize. You'll know if a configuration value is used because it will appear in the starting logs like the following image...
Collaboration server URL
Comma-delimited URLs to plugins that should be loaded by default
Proxy to use for CORS requests, e.g. to make api requests that are disallowed by CORs
Access Key for uploading/importing from AWS S3 buckets
Secret Access Key for uploading/importing from AWS S3 buckets
Region of S3 Bucket
Cognito Identity Pool Id
Cognito user pool id
Cognito user pool web client id
Bucket to use for Cognito object storage
Region of bucket to use for Cognito
Disable remote paid collaboration requests
API Key for requesting work from Label Help
These are the most common configuration values, but you can also customize hotkeys or any other attribute the appears in the AppConfig.
Sometimes, you may want to run the Collaboration Server on a different machine than the Client Application, you can do this by using the npm module.
# via npmnpm install -g udt-collaboration-serverudt-collaboration-server --port 3001