-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extension-based logic for fds add
#94
Comments
@pwoolvett Thank you for the interesting idea! About confs - it's definitely something to consider. Everything should be overridable using env variables without editing conf files, but using dotenv seems like a decent common choice to combine the approaches - conveniently storing env variables in a file if that's what you want. |
Its quite common for our use case that files which should go into dvc have the same extension (and that extension should not go into git according to our guidelines). For example: HDF5, pickle, etc.
Is that something you'd like to incorporate? eg via
fds.domain.constants
$REPO_ROOT
, or~/.config/fds
(or any combination of them, maybe overriding defaults given a preference order)
If it is, I'd like to take a shot at it, starting from here https://github.com/DAGsHub/fds/search?q=MAX_THRESHOLD_SIZE
While we're at it, is a configuration file in your horizon somewhere?
The text was updated successfully, but these errors were encountered: