Julia Ostheimer commited on
Commit
58cb840
·
1 Parent(s): 74539b9

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +25 -18
README.md CHANGED
@@ -7,23 +7,25 @@ This is the code repository for the DEval project "Durchführung und Unterstütz
7
 
8
  - **[Get Started](#get-started)**
9
 
10
- - [Setting-up the environment](#setting-up-the-environment)
11
- - [Load EPD Data](#load-epd-data)
12
- - [PostGres](#postgres)
13
-
14
- - [Contribute](#contribute)
15
- - [Unit Tests](#unit-tests)
16
- - [Deploy to Heroku](#deploy-to-heroku)
17
- - [Support](#support)
18
- - [License](#license)
19
 
20
  ---
21
 
22
  ## Get started
23
 
24
- To run, the project expects secret keys from a `.env` file.
 
 
 
25
 
26
- ### Setting-up the environment
 
 
 
 
 
27
  We use `uv` as a python and our package dependency manager. Follow these [instructions](https://docs.astral.sh/uv/getting-started/installation/) to install with the standalone installer and `curl`
28
 
29
  Next, to set up the local dependencies. You can find further information [here](https://docs.astral.sh/uv/guides/projects/#managing-dependencies)
@@ -31,16 +33,19 @@ Next, to set up the local dependencies. You can find further information [here](
31
  uv sync
32
  ```
33
 
34
- This should give you a package structure like this with a `.venv` file
35
  ```
36
  .
37
  ├── .venv
38
  ├── .python-version
 
 
39
  ├── README.md
40
- ── main.py
41
- └── pyproject.toml
42
  ```
43
 
 
 
44
 
45
  Alternatively, with a different dependency manager such as `venv` install directly from `pyproject.toml`.
46
  ```Bash
@@ -49,10 +54,12 @@ Alternatively, with a different dependency manager such as `venv` install direct
49
  **Note**: the dependencies then need to be documented manually in the `pyproject.toml`.
50
 
51
 
 
52
 
53
- ## To-Do
54
- - create bsaic set-up with Qdrant in memory, ingestion pipeline
55
- - create basic set-up where retrieval is not yet having an llm call
56
- - connect to frontend with "invoke" and deletion of memory
57
 
 
 
 
58
 
 
 
7
 
8
  - **[Get Started](#get-started)**
9
 
10
+ - [Set up `.env` file](#set-up-env-file)
11
+ - [Set up the environment](#set-up-the-environment)
12
+ - [Run the code](#run-the-code)
 
 
 
 
 
 
13
 
14
  ---
15
 
16
  ## Get started
17
 
18
+ ### Set up `.env` file
19
+ To run, the project expects secret keys from a `.env` file. Due to security reasons, this file should not be committed to version control!
20
+
21
+ Here how the `.env` file should look like:
22
 
23
+ ```
24
+ # OPENAI_API_KEY
25
+ OPENAI_API_KEY= # Your OpenAI API key
26
+ ```
27
+
28
+ ### Set up the environment
29
  We use `uv` as a python and our package dependency manager. Follow these [instructions](https://docs.astral.sh/uv/getting-started/installation/) to install with the standalone installer and `curl`
30
 
31
  Next, to set up the local dependencies. You can find further information [here](https://docs.astral.sh/uv/guides/projects/#managing-dependencies)
 
33
  uv sync
34
  ```
35
 
36
+ This should give you a package structure like this with a `.venv` directory:
37
  ```
38
  .
39
  ├── .venv
40
  ├── .python-version
41
+ ├── app.py
42
+ ├── pyproject.toml
43
  ├── README.md
44
+ ── uv.lock
 
45
  ```
46
 
47
+ #### uv.lock
48
+ `uv.lock` is a cross-platform lockfile that contains exact information about the project's dependencies. Unlike the `pyproject.toml` which is used to specify the broad requirements of the project, the lockfile contains the exact resolved versions that are installed in the project environment via `uv`. This file should be checked into version control, allowing for consistent and reproducible installations across machines. `uv.lock` is a human-readable TOML file but is managed by `uv` and should NOT be edited manually.
49
 
50
  Alternatively, with a different dependency manager such as `venv` install directly from `pyproject.toml`.
51
  ```Bash
 
54
  **Note**: the dependencies then need to be documented manually in the `pyproject.toml`.
55
 
56
 
57
+ ### Run the code
58
 
59
+ After installing the needed dependencies for the project and setting up the environment, execute the code from the root of the repository by running the `app.py` script via `uv` with the following command:
 
 
 
60
 
61
+ ```Bash
62
+ uv run app.py
63
+ ```
64
 
65
+ You will see the logging in the terminal and receive a link to access the currently locally hosted Gradio User Interface.