You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now users have individual workspaces used by jupyterhub that are used to store notebooks. This makes it easy to apply permissions on these workspaces per-user.
However, wps services generated for a specific user are stored in a flat structure (files for one user are stored in the same directory as any other user). This makes setting permissions on these files complex. For example, if the wps service outputs are served by a thredds server we need to set permissions on each file according to which user generated the file (this is done by cowbird).
If we could place the wps output files in directories for each user, we could simplify the permissions process, potentially meaning we don't need cowbird for this at all.
For example:
current output dir for finch and user 'misha': /data/wps_outputs/finch/
proposed output dir for finch and user 'misha': /data/wps_outputs/misha/finch or simply /data/wps_outputs/misha
I don't think that this is supported by pywps and so isn't supported by most of the WPS birds. In order to implement this we could:
update pywps to support setting the outputdir based on a value in the request header (and update all existing birds to use the newer version of pywps)
run all birds through weaver (which does support setting the outputdir based on a value in the request header)
The text was updated successfully, but these errors were encountered:
Right now users have individual workspaces used by jupyterhub that are used to store notebooks. This makes it easy to apply permissions on these workspaces per-user.
However, wps services generated for a specific user are stored in a flat structure (files for one user are stored in the same directory as any other user). This makes setting permissions on these files complex. For example, if the wps service outputs are served by a thredds server we need to set permissions on each file according to which user generated the file (this is done by cowbird).
If we could place the wps output files in directories for each user, we could simplify the permissions process, potentially meaning we don't need cowbird for this at all.
For example:
/data/wps_outputs/finch/
/data/wps_outputs/misha/finch
or simply/data/wps_outputs/misha
I don't think that this is supported by pywps and so isn't supported by most of the WPS birds. In order to implement this we could:
The text was updated successfully, but these errors were encountered: