If you are using this app to manage software across multiple teams on a Fleet instance, five additional configuration values are required:
-`sails.config.uploads.bucket` The name of an AWS s3 bucket where unassigned software installers will be stored.
-`sails.config.uploads.secret` The secret for the S3 bucket where unassigned software installers will be stored.
-`sails.config.uploads.region` The region the AWS S3 bucket is located.
-`sails.config.uploads.bucketWithPostfix`: The name of the s3 bucket with the directory that the software installers are stored in on appended to it. If the files will be stored in the root directory of the bucket, this value should be identical to the `sails.config.uploads.bucket` value
-`sails.config.uploads.prefixForFileDeletion`: The directory path in the S3 bucket where the software installers will be stored. If the installers will be stored in the root directory, then this value can be set to ' '.
2.`sails_custom__fleetApiToken`: An API token for an [API-only user](https://fleetdm.com/docs/using-fleet/fleetctl-cli#create-api-only-user) on your Fleet instance.
3. Open the `ee/bulk-operations-dashboard/` folder in your terminal.
4. Run `docker compose up --build` to build the bulk operations dashboard's Docker image.
> The first time the bulk operations dashboard starts it will Initalize the database aby running the `config/bootstrap.js` script before the server starts.
5. Once the container is done building, the bulk operations dashboard will be available at http://localhost:1337