docs: clarify installation instructions

Author: uptickmetachu

README.md

@@ -16,7 +16,6 @@ The tool has two halves:
 - Gitops Server - an instance of this gets deployed to each of your kubernetes clusters, listening on changes made to your gitops cluster repo. The server's responsibility is to update the deployments on the cluster it lives on to match the app specifications in the repo.
 - Gitops CLI - this is a tool that you can use to interact comfortably with your cluster repo. It allows listing all deployed applications, what images they're presently running on, and which clusters they live on. It also provides numerous operations that can be applied to one or more apps at a time, such as bumping to a newer version of an image, or running a particular command across your app cohort.
 
-You can install the CLI tool with: `pip install gitops`
 
 Currently Kubernetes/Helm is the only supported cluster interface. All app deployments are performed as applications of Helm charts.
 
@@ -36,13 +35,17 @@ This is a git repository that you set up, where you list out all of your applica
 +- jobs
 </pre>
 
-## Installation
+## Gitops CLI Installation
 
-Secrets should be placed in `secrets.env`. The example file `secrets.example.env` has the environment variables you will need to supply.
+1. Install the CLI tool with: `uv tool install gitops` and upgrade it with `uv tool upgrade gitops`.
+
+2. Set up the environment variable `GITOPS_APPS_DIRECTORY` to invoke gitops from any directory.
 
-Add `export GITOPS_APPS_DIRECTORY=~/<cluster-apps-folder>` to invoke gitops from any directory.
+## Gitops Server Installation
+
+Secrets should be placed in `secrets.env`. The example file `secrets.example.env` has the environment variables you will need to supply.
 
-Ensure that gitops has `edit` access to the namespace it is deploying to. An example RoleBinding is:
+Ensure that the gitops service account has `edit` access to the namespace it is deploying to. An example RoleBinding is:
 
 ```
 apiVersion: rbac.authorization.k8s.io/v1