shahar1 commented on code in PR #60982:
URL: https://github.com/apache/airflow/pull/60982#discussion_r2723863227


##########
contributing-docs/03_contributors_quick_start.rst:
##########
@@ -553,6 +551,11 @@ Using Breeze
              alt="Accessing local airflow">
       </div>
 
+- To exit in breeze start-airflow in mprocs terminal
+
+  .. code-block:: bash
+
+    q
 
 - Alternatively you can start the same using the following commands

Review Comment:
   Before mprocs was introduced, this section used to show manual start-up 
instead of automated start-up using tmux. Now it seems out of context - I'd 
either show the equivalent manual process in mprocs (if such exists), or just 
dedicate this section entirely to tmux. 
   Please try to refine it and reorder the headers and screenshots to it would 
be clearer to the user what goes where.



##########
contributing-docs/03_contributors_quick_start.rst:
##########
@@ -562,7 +565,7 @@ Using Breeze
 
     breeze --python 3.10 --backend postgres
 
-  2. Open tmux
+  2. For Open tmux terminal

Review Comment:
   ```suggestion
     2. For tmux terminal
   ```



##########
contributing-docs/03_contributors_quick_start.rst:
##########
@@ -511,9 +511,7 @@ Using Breeze
 
 1. Starting the Breeze environment using ``breeze start-airflow`` starts the 
Breeze environment with last configuration run(
    In this case Python version and backend are picked up from last execution 
``breeze --python 3.10 --backend postgres``)
-   It also automatically starts the API server (FastAPI api and UI), 
triggerer, dag processor and scheduler. It drops you in tmux with triggerer to 
the right, and
-   Scheduler, API server (FastAPI api and UI), Dag processor from left to 
right at the bottom. Use ``[Ctrl + B] and Arrow keys`` to navigate.
-
+   It also automatically starts the API server (FastAPI api and UI), 
triggerer, dag processor and scheduler. It drops you in mprocs terminal.

Review Comment:
   The screenshot right below it is from tmux, which is rather confusing :)



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