This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch v3-0-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/v3-0-test by this push:
new cae60bbf4ad [v3-0-test] Add user facing docs for running a separate
Task Execution API-server (#53789) (#53794)
cae60bbf4ad is described below
commit cae60bbf4ad7738ac751f5ba11e053725a285eb8
Author: github-actions[bot]
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Sun Jul 27 13:06:40 2025 +0200
[v3-0-test] Add user facing docs for running a separate Task Execution
API-server (#53789) (#53794)
(cherry picked from commit 97549587cdefb4ab9ea6c08dc8a30023e00ccb9f)
Co-authored-by: LIU ZHE YOU <68415893+jason810...@users.noreply.github.com>
---
.../administration-and-deployment/web-stack.rst | 27 ++++++++++++++++++++++
1 file changed, 27 insertions(+)
diff --git a/airflow-core/docs/administration-and-deployment/web-stack.rst
b/airflow-core/docs/administration-and-deployment/web-stack.rst
index 9a16906ab6a..5f2159649b3 100644
--- a/airflow-core/docs/administration-and-deployment/web-stack.rst
+++ b/airflow-core/docs/administration-and-deployment/web-stack.rst
@@ -20,6 +20,10 @@
Web Stack
=========
+
+Configuration
+-------------
+
Sometimes you want to deploy the backend and frontend behind a
variable url path prefix. To do so, you can configure the url
:ref:`config:api__base_url`
for instance, set it to ``http://localhost:28080/d12345``. All the APIs routes
will
@@ -30,3 +34,26 @@ and served successfully.
You will also need to update the execution API server url
:ref:`config:core__execution_api_server_url` for tasks to be able to reach the
API
with the new prefix.
+
+Separating API Servers
+-----------------------
+
+By default, both the Core API Server and the Execution API Server are served
together:
+
+.. code-block:: bash
+
+ airflow api-server
+ # same as
+ airflow api-server --apps all
+ # or
+ airflow api-server --apps core,execution
+
+If you want to separate the Core API Server and the Execution API Server, you
can run them
+separately. This might be useful for scaling them independently or for
deploying them on different machines.
+
+.. code-block:: bash
+
+ # serve only the Core API Server
+ airflow api-server --apps core
+ # serve only the Execution API Server
+ airflow api-server --apps execution
