Skip to content
This repository has been archived by the owner on Jan 7, 2025. It is now read-only.

instance-specific config capability needed #941

Closed
steevmi1 opened this issue Jul 29, 2016 · 7 comments · Fixed by #1091
Closed

instance-specific config capability needed #941

steevmi1 opened this issue Jul 29, 2016 · 7 comments · Fixed by #1091

Comments

@steevmi1
Copy link

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.

@gheinrich
Copy link
Contributor

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?

@lukeyeager
Copy link
Member

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:
http://12factor.net/config

@gheinrich
Copy link
Contributor

Or an environment variable that points to the config file :-)

@lukeyeager
Copy link
Member

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?

@gheinrich
Copy link
Contributor

@steevmi1 any feedback please?

@gheinrich
Copy link
Contributor

Closing due to inactivity.

@lukeyeager
Copy link
Member

Re-opening this. I'd like to address this (and/or #180).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants