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
Copy file name to clipboardExpand all lines: README.md
+10-4Lines changed: 10 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,12 +28,12 @@ Before you can use this library you'll need:
28
28
29
29
The API access information is normally placed in a `.servicex` file (to keep this confidential information form accidentally getting checked into a public repository). The `servicex` library searches for configuration information in several locations to determine what end-point it should connect to, in the following order:
30
30
31
-
1. A `.servicex` file in the current working directory
31
+
1. A `.servicex` file in the current working directory (it can also be named `servicex.yaml` or `servicex.yml`)
32
32
1. A `.servicex` file in the user's home directory (`$HOME` on Linux and Mac, and your profile
33
33
directory on Windows).
34
34
1. The `config_defaults.yaml` file distributed with the `servicex` package.
35
35
36
-
If no endpoint is specified, then the library defaults to the developer endpoint, which is `http://localhost:5000` for the web-service API, and `localhost:9000` for the `minio` endpoint. No passwords are required.
36
+
If no endpoint is specified, then the library defaults to the developer endpoint, which is `http://localhost:5000` for the web-service API. No passwords are used in this case.
37
37
38
38
Create a `.servicex` file, in the `yaml` format, in the appropriate place for your work that contains the following (for the `xaod` backend; use `uproot` for the uproot backend):
39
39
@@ -136,15 +136,21 @@ do_query(ds) # Cache is not ignored
136
136
As mentioned above, the `.servicex` file is read to pull a configuration. The search path for this file:
137
137
138
138
1. Your current working directory
139
-
2. Your home directory
139
+
2. Any working directory above your current working directory.
140
+
3. Your home directory
141
+
142
+
The file can be named any of the following (ordered by precedence):
143
+
144
+
- `servicex.yaml`
145
+
- `servicex.yml`
146
+
- `.servicex`
140
147
141
148
The file can contain an `api_endpoint` as mentioned above. In addition the other following things can be put in:
142
149
143
150
- `cache_path`: Location where queries, data, and a record of queries are written. This should be an absolute path the person running the library has r/w access to. On windows, make sure to escape `\` - and best to follow standard `yaml` conventions and put the path in quotes - especially if it contains a space. Top level yaml item (don't indent it accidentally!). Defaults to `/tmp/servicex` (with the temp directory as appropriate for your platform) Examples:
- `minio_endpoint`, `minio_username`, `minio_password` - these are only interesting if you are using a pre-RC2 release of `servicex` - when the `minio` information wasn't part of the API exchange. This feature is depreciated and will be removed around the time `servicex` moves to RC3.
148
154
- `backend_types`- a list of yaml dictionaries that contains some defaults for the backends. By default only the `return_data` is there, which for `xaod` is `root` and `uproot` is `parquet`. Allows `servicex` to convert to `pandas.DataFrame` or `awkward` if requested by the user.
149
155
150
156
All strings are expanded using python's [os.path.expand](https://docs.python.org/3/library/os.path.html#os.path.expandvars) method - so `$NAME` and `${NAME}` will work to expand existing environment variables.
0 commit comments