Fix/docker compose

[lmarini]

To run the full stack standalone (versus for development with frontend/backend/worker on host):

1. Checkout git submodules
   git submodule update --init --recursive --remote
2. Create a .env and populate with required secrets. As of now you will need your own LLM's for chatting and creation of embeddings
   cp .env.secrets .env
3. Start the docker stack
   docker compose up -d
4. Initiate all databases
   sh init-db.sh
5. Take down stack and comment out ports for the following services: postgres-illinois-chat, qdrant, minio admin port 9001
   docker compose down
6. Restart stack
   docker compose up -d

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
23248099	Triggered	Redis Server Password	c3e12e9	docker-compose.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[drshika]

once I was able to get the whole stack running, I was getting issues with the Auth token being invalid:

	http://localhost:3000/api/UIUC-api/[email protected]
	{"error":"Invalid token","message":"The provided token is invalid"}

so I changed the keycloak URL in docker. I also had to make changes in the illinois-chat branch in the frontend to make the internal networking function properly. I think someone else should verify that keycloak networking is a problem on new setups.

[drshika]

See comments above.