diff --git a/404.html b/404.html index 82be08b0..55c365dd 100644 --- a/404.html +++ b/404.html @@ -4,7 +4,7 @@
uvx, run uvx openrag.
After installation, the TUI can deploy, manage, and upgrade your OpenRAG containers.
-Click Start All Services to start the OpenRAG containers.
-The TUI automatically detects your container runtime, and then checks if your machine has compatible GPU support by checking for CUDA, NVIDIA_SMI, and Docker/Podman runtime support. This check determines which Docker Compose file OpenRAG uses.
-The TUI then pulls the images and deploys the containers with the following command.
docker compose up -d
If images are missing, the TUI runs docker compose pull, then runs docker compose up -d.
The Diagnostics menu provides health monitoring for your container runtimes and monitoring of your OpenSearch security.
The Status menu displays information on your container deployment. Here you can check container health, find your service ports, view logs, and upgrade your containers.
-To view streaming logs, select the container you want to view, and press l. -To copy your logs, click Copy to Clipboard.
-To upgrade your containers, click Upgrade.
-Upgrade runs docker compose pull and then docker compose up -d --force-recreate.
-For more information, see Upgrade OpenRAG containers with the TUI.
To reset your containers, click Reset. -Reset gives you a completely fresh start. -Reset deletes all of your data, including OpenSearch data, uploaded documents, and authentication. -Reset runs two commands. -It first stops and removes all containers, volumes, and local images.
-docker compose down --volumes --remove-orphans --rmi local
When the first command is complete, OpenRAG removes any additional Docker objects with prune.
docker system prune -f
A native service in OpenRAG refers to a service run locally on your machine, and not within a container.
-The docling serve process is a native service in OpenRAG, because it's a document processing service that is run on your local machine, and controlled separately from the containers.
To start or stop docling serve or any other native services, in the TUI Status menu, click Stop or Restart.
To view the status, port, or PID of a native service, in the TUI main menu, click Status.
+Logs: To view streaming logs, select the container you want to view, and press l. +To copy the logs, click Copy to Clipboard.
+Upgrade: Check for updates. For more information, see upgrade OpenRAG.
+Reset: This is a destructive action that resets your containers.
+Native services: From the Status menu, you can view the status, port, and process ID (PID) of the OpenRAG native services. +You can also click Stop or Restart to stop and start OpenRAG native services.
+A native service in OpenRAG is a service that runs locally on your machine, not within a container. For example, the docling serve process is an OpenRAG native service because this document processing service runs on your local machine, separate from the OpenRAG containers.
This is a destructive action that destroys and recreates all of your OpenRAG containers.
To destroy and recreate your OpenRAG containers, go to the TUI Status menu, and then click Reset.
+The Reset function runs two commands. First, it stops and removes all containers, volumes, and local images:
+docker compose down --volumes --remove-orphans --rmi local
Then, it removes any additional Docker objects with docker system prune -f.
If you reset your containers as part of reinstalling OpenRAG, continue the reinstallation process after resetting the containers.
+On the TUI main page, click Start All Services to start the OpenRAG containers and launch OpenRAG itself.
+When you start all services, the following processes happen:
+OpenRAG automatically detects your container runtime, and then checks if your machine has compatible GPU support by checking for CUDA, NVIDIA_SMI, and Docker/Podman runtime support. This check determines which Docker Compose file OpenRAG uses.
OpenRAG pulls the OpenRAG container images with docker compose pull if any images are missing.
OpenRAG deploys the containers with docker compose up -d.
To upgrade OpenRAG, upgrade the OpenRAG Python package, and then upgrade the OpenRAG containers using the OpenRAG TUI.
-Upgrading the OpenRAG Python package updates the TUI and Python code, but container versions are controlled separately by environment variables in your .env file.
Use the following steps to upgrade the OpenRAG Python package to the latest version from PyPI. -After upgrading the Python package, you should also upgrade your OpenRAG containers.
-If you installed OpenRAG using the automatic installer or uvx, follow these steps to upgrade:
To upgrade OpenRAG, upgrade the OpenRAG Python package, and then upgrade the OpenRAG containers.
+This is a two part process because upgrading the OpenRAG Python package updates the TUI and Python code, but the container versions are controlled by environment variables in your .env file.
Stop your OpenRAG containers: In the OpenRAG TUI, go to the Status menu, and then click Stop Services.
+Upgrade the OpenRAG Python package to the latest version from PyPI.
+Use these steps to upgrade the Python package if you installed OpenRAG using the automatic installer or uvx:
Navigate to your OpenRAG workspace directory:
cd openrag-workspace
uvx --from openrag==0.1.33 openrag
After upgrading the Python package, upgrade your containers.
-Use these steps to upgrade the Python package if you installed OpenRAG in a Python project with uv add:
Navigate to your project directory:
cd YOUR_PROJECT_NAME
uv run openrag
After upgrading the Python package, upgrade your containers.
-Use these steps to upgrade the Python package if you installed OpenRAG in a venv with uv pip install:
Activate your virtual environment.
uv run openrag
After upgrading the Python package, upgrade your containers.
-After upgrading the OpenRAG Python package, upgrade your containers to ensure they match the latest version.
-Upgrade runs docker compose pull, which pulls container images based on versions specified in your .env file.
-OPENRAG_VERSION is set to latest by default, so it pulls the latest available container images.
Start the upgraded OpenRAG containers: In the OpenRAG TUI, click Start All Services, and then wait while the containers start.
+After upgrading the Python package, OpenRAG runs docker compose pull to get the appropriate container images matching the version specified in your OpenRAG .env file. Then, it recreates the containers with the new images using docker compose up -d --force-recreate.
In the .env file, the OPENRAG_VERSION environment variable is set to latest by default, which it pulls the latest available container images.
+To pin a specific container image version, you can set OPENRAG_VERSION to the desired container image version, such as OPENRAG_VERSION=0.1.33.
However, when you upgrade the Python package, OpenRAG automatically attempts to keep the OPENRAG_VERSION synchronized with the Python package version.
+You might need to edit the .env file after upgrading the Python package to enforce a different container version.
+The TUI warns you if it detects a version mismatch.
If you get an error that langflow container already exists error during upgrade, see Langflow container already exists during upgrade.
When the upgrade process is complete, you can close the Status window and continue using OpenRAG.
+If you encounter a langflow container already exists error during upgrade, see Langflow container already exists during upgrade in the troubleshooting guide.
To pin container versions to a specific release other than latest, set the OPENRAG_VERSION in your .env file:
OPENRAG_VERSION=0.1.33
For more information, see System settings environment variables.
-The Diagnostics menu provides health monitoring for your container runtimes and monitoring of your OpenSearch security.
To reinstall OpenRAG with a completely fresh setup:
Reset your containers using the Reset button in the TUI status menu. -This removes all containers, volumes, and data.
+In the TUI Status menu, reset your containers to destroy the existing OpenRAG containers and their data.
Optional: Delete your project's .env file.
-The Reset operation doesn't remove your project's .env file, so your passwords, API keys, and OAuth settings can be preserved.
-If you delete the .env file, run the Set up OpenRAG with the TUI process again to create a new configuration.
Optional: Delete your project's .env file.
The Reset operation doesn't remove your project's .env file, so your passwords, API keys, and OAuth settings can be preserved.
+If you delete the .env file, you must run the Set up OpenRAG with the TUI process again to create a new configuration file.
In the TUI Setup menu, follow these steps from Basic Setup:
+Optional: Delete your OpenSearch knowledge base by deleting the contents of the ./opensearch-data folder in your OpenRAG installation directory.
In the TUI Setup menu, repeat the Basic Setup process:
.env file, run the Set