dimas-b commented on code in PR #829:
URL: https://github.com/apache/polaris/pull/829#discussion_r1922787336


##########
site/content/in-dev/unreleased/quickstart.md:
##########
@@ -97,42 +97,60 @@ To start using Polaris in Docker, launch Polaris while 
Docker is running:
 
 ```shell
 cd ~/polaris
-docker compose -f docker-compose.yml up --build
+./gradlew clean :polaris-quarkus-server:assemble 
-Dquarkus.container-image.build=true
+docker run -p 8181:8181 -p 8182:8182 apache/polaris:latest
 ```
 
-Once the `polaris-polaris` container is up, you can continue to [Defining a 
Catalog](#defining-a-catalog).
+You should see output for some time as Polaris builds and starts up. 
Eventually, you won’t see any more logs and should see messages that resemble 
the following:
+
+```
+INFO  [io.quarkus] [,] [,,,] (Quarkus Main Thread) Apache Polaris Server 
<version> on JVM  (powered by Quarkus <version>) started in 2.656s. Listening 
on: http://localhost:8181. Management interface listening on 
http://0.0.0.0:8182.
+INFO  [io.quarkus] [,] [,,,] (Quarkus Main Thread) Profile prod activated.
+INFO  [io.quarkus] [,] [,,,] (Quarkus Main Thread) Installed features: [...]
+```
+
+Once the container is up, you can continue to [Defining a 
Catalog](#defining-a-catalog).
 
-### Building Polaris
+### Running Polaris from Sources
+
+The easiest way to run Polaris locally is to start the Polaris service in [Dev
+mode](https://quarkus.io/guides/dev-mode-differences):
+
+```shell
+cd ~/polaris
+./gradlew :polaris-quarkus-service:quarkusDev

Review Comment:
   nit: IMHO, this mode is too low-level and risky for a "quick start" guide. 
It's probably good for developers working on the codebase, but I'd personally 
not advertise it to users that are just getting started.



-- 
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