-
Notifications
You must be signed in to change notification settings - Fork 1.4k
instance-specific config capability needed #941
Comments
You could modify this line to load the DIGITS config file (in which the location of the jobs directory is configured) to a location in your users' home directory therefore allowing every user to have their own config file (and thus jobs directory). Would that work for you? |
Would it help to do configuration through environment variables instead of a config file? Here's an argument for storing the config in the environment for webapps: |
Or an environment variable that points to the config file :-) |
Haha good point - that would be a quick hack. @steevmi1 would that be helpful for you? |
@steevmi1 any feedback please? |
Closing due to inactivity. |
Re-opening this. I'd like to address this (and/or #180). |
We work in a Linux-based HPC cluster environment. Users will use the queueing system to gain access to systems/resources, then run software out of a central installation (NFS mount). When we attempt to run digits-devserver, we run into errors because individual users can't create a jobs directory as they don't have write permissions into the software install. We've worked around this short-term by creating the digits/jobs directory (and opening it up for full read/write access), but to be able to support this in our environment we need the ability to have instance-specific configurations.
The text was updated successfully, but these errors were encountered: