If you are currently using a arm64 or x86_32 only cpu other than Apple Silicon on MacOS, please manage your own way to do this development.
The content below is not recommended and is no longer being maintained.
This guide outlines the steps to set up and run the WatAIOliver project on Windows (VS Code environment).
Please note:
- Lines surrounded by "<>" should be replaced with relevant lines specific to your computer
- Please ensure that you have included a .env file in the backend folder and in the machine_learning folder with the right setup info. If you have not or are not sure if you have written your .env file correctly, please ask for help
cd <Path to project route>
python3.12 -m venv venv
.\venv\Scripts\activatepython -m pip install --upgrade pippip install -r backend/requirements.txtpip install -r machine_learning/pdf_processor/requirements.txtpip install -r machine_learning/rag_system/requirements.txt -c constraints.txt --upgrade --upgrade-strategy eagerpip install -r machine_learning/ai_agents/requirements.txtNote: If there are package conflicts, resolve them manually by installing the correct versions as shown by pip error messages.
cd frontend
npm installEnsure the marked package is installed:
npm list markedIf not installed:
npm install markedcd <Path to project root>\frontend
npm run devcd <Path to project root>\backend
..\venv\Scripts\python.exe -m uvicorn src.main:app --reload --host 0.0.0.0 --port 8000cd <Path to project root>\machine_learning\pdf_processor
& "<Path to project root>\venv\Scripts\python.exe" -m uvicorn main:app --reload --host 0.0.0.0 --port 8001cd <Path to project root>\machine_learning\rag_system
& "<Path to project root>\venv\Scripts\python.exe" -m uvicorn app.main:app --reload --host 0.0.0.0 --port 8002cd <Path to project root>\machine_learning\ai_agents
& "<Path to project root>\venv\Scripts\python.exe" -m uvicorn app.main:app --reload --host 0.0.0.0 --port 8003- Always cd into the correct directory for backend, PDF processor, and RAG system before running Uvicorn.
- Always use the absolute path to Python executable inside your venv to avoid path issues.
- If you see import errors, double-check your working directory.
- Run each service in its own VS Code terminal tab.
- Ensure your
.envis correctly placed and loaded for services requiring credentials. - Always activate the virtual environment before running any commands:
.\venv\Scripts\activate