In general, services will benefit from, or even require, access to a file system/server.
One approach is to include an storage_location parameter with service requests. This location would be automatically mounted to containers and allow users to access files in the specified location. If they decide they want to use a file elsewhere, they would need to create a new service.
An alternative approach is to add "storage locations" to profiles and automatically mount all storage locations. For example,
In general, services will benefit from, or even require, access to a file system/server.
One approach is to include an
storage_location
parameter with service requests. This location would be automatically mounted to containers and allow users to access files in the specified location. If they decide they want to use a file elsewhere, they would need to create a new service.An alternative approach is to add "storage locations" to profiles and automatically mount all storage locations. For example,
Now, then a service is launched, we mount all these locations:
Users then have access to all of their storage locations from within the container by using the appropriate container path.