Skip to content
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

📝 README gains documentation on how to run with docker compose and .env #38

Open
jdhoffa opened this issue Dec 4, 2024 · 2 comments · May be fixed by #54
Open

📝 README gains documentation on how to run with docker compose and .env #38

jdhoffa opened this issue Dec 4, 2024 · 2 comments · May be fixed by #54

Comments

@jdhoffa
Copy link
Member

jdhoffa commented Dec 4, 2024

          > I have a `.env` file that contains:
analysis_output_dir: /PATH/TO/pacta_analysis_outputs
benchmarks_dir: /PATH/TO/pacta-data/2023Q4
dashboard_data_dir: /PATH/TO/json_assets_outputs 

hmmm, ok I don't really know how that works and don't see it documented anywhere... I'll try and see if I can run it somehow and maybe get a similar result as to what you're getting

Originally posted by @cjyetman in #36 (comment)

@cjyetman
Copy link
Member

cjyetman commented Dec 4, 2024

maybe most importantly, what is the benchmarks_dir for, since I had been running it bunch before it was dockerized and that was not needed at all. I can guess what the others used to point to.

@jdhoffa
Copy link
Member Author

jdhoffa commented Dec 4, 2024

For all intents and purposes benchmarks_dir can just point to pacta-data/2023Q4.
It is named more precisely because the only datasets actually required are the benchmark datasets (I believe?)

But indeed, must be documented

@AlexAxthelm AlexAxthelm linked a pull request Dec 19, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants