eric-maynard commented on code in PR #700:
URL: https://github.com/apache/polaris/pull/700#discussion_r1917195422


##########
README.md:
##########
@@ -57,36 +78,76 @@ insert into db1.table1 values (1, 'a');
 select * from db1.table1;
 ```
 
-Apache Polaris supports the following optional build options:
-- `-PeclipseLink=true` – Enables the EclipseLink extension.
-- `-PeclipseLinkDeps=[groupId]:[artifactId]:[version],...` – Specifies one or 
more additional dependencies for EclipseLink (e.g., JDBC drivers) separated by 
commas.
-
 ### More build and run options
-Running in Docker
-- `docker build -t localhost:5001/polaris:latest .` - To build the image.
-  - Optional build options:
-    - `docker build -t localhost:5001/polaris:latest --build-arg 
ECLIPSELINK=true .` - Enables the EclipseLink extension.
-    - `docker build -t localhost:5001/polaris:latest --build-arg 
ECLIPSELINK=true --build-arg 
ECLIPSELINK_DEPS=[groupId]:[artifactId]:[version],... .` – Enables the 
EclipseLink extension with one or more additional dependencies for EclipseLink 
(e.g. JDBC drivers) separated by commas.
-- `docker run -p 8181:8181 localhost:5001/polaris:latest` - To run the image 
in standalone mode.
-
-Running in Kubernetes
-- `./run.sh` - To run Polaris as a mini-deployment locally. This will create 
one pod that bind itself to ports `8181` and `8182`.
-  - Optional run options:
-    - `./run.sh -b "ECLIPSELINK=true"` - Enables the EclipseLink extension.
-    - `./run.sh -b 
"ECLIPSELINK=true;ECLIPSELINK_DEPS=[groupId]:[artifactId]:[version],..."` – 
Enables the EclipseLink extension with one or more additional dependencies for 
EclipseLink (e.g. JDBC drivers) separated by commas.
-- `kubectl port-forward svc/polaris-service -n polaris 8181:8181 8182:8182` - 
To create secure connections between a local machine and a pod within the 
cluster for both service and metrics endpoints.
-  - Currently supported metrics endpoints:
-    - localhost:8182/metrics
-    - localhost:8182/healthcheck
+
+#### Running in Docker
+
+Please note: there are no official Docker images for Apache Polaris yet. For 
now, you can build the
+Docker images locally.
+
+To build the Polaris server Docker image locally:
+
+```shell
+./gradlew clean :polaris-quarkus-server:assemble 
-Dquarkus.container-image.build=true
+```
+
+To run the Polaris server Docker image:
+
+```shell
+docker run -p 8181:8181 -p 8182:8182 apache/polaris:latest
+```
+
+#### Running in Kubernetes
+
+- `./run.sh` - To run Polaris as a mini-deployment locally. This will create a 
Kind cluster, 
+  then deploy one pod and one service. The service is available on ports 
`8181` and `8182`.
+- `kubectl port-forward svc/polaris-service -n polaris 8181:8181 8182:8182` - 
To create secure 
+  connections between a local machine and a pod within the cluster for both 
service and metrics 
+  endpoints.
+  - Currently supported metrics and health endpoints:
+    - http://localhost:8182/q/metrics
+    - http://localhost:8182/q/health
 - `kubectl get pods -n polaris` - To check the status of the pods.
 - `kubectl get deployment -n polaris` - To check the status of the deployment.
 - `kubectl describe deployment polaris-deployment -n polaris` - To 
troubleshoot if things aren't working as expected.
 
-Running regression tests
-- `./regtests/run.sh` - To run regression tests in another terminal.
-- `docker compose up --build --exit-code-from regtest` - To run regression 
tests in a Docker environment.
+#### Running regression tests
+
+Regression tests can be run in a local environment or in a Docker environment.
+
+To run regression tests locally, you need to have a Polaris server running 
locally, with the 
+`test` Authenticator enabled. You can do this by running Polaris in Quarkus 
Dev mode, as explained
+above:
+
+```shell
+./gradlew polarisServerDev

Review Comment:
   Nice!



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to