Skip to content

Commit 9754958

Browse files
authored
Add user facing docs for running a separate Task Execution API-server (#53789)
1 parent f83fe19 commit 9754958

1 file changed

Lines changed: 27 additions & 0 deletions

File tree

‎airflow-core/docs/administration-and-deployment/web-stack.rst‎

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,10 @@
2020
Web Stack
2121
=========
2222

23+
24+
Configuration
25+
-------------
26+
2327
Sometimes you want to deploy the backend and frontend behind a
2428
variable url path prefix. To do so, you can configure the url :ref:`config:api__base_url`
2529
for instance, set it to ``http://localhost:28080/d12345``. All the APIs routes will
@@ -30,3 +34,26 @@ and served successfully.
3034
You will also need to update the execution API server url
3135
:ref:`config:core__execution_api_server_url` for tasks to be able to reach the API
3236
with the new prefix.
37+
38+
Separating API Servers
39+
-----------------------
40+
41+
By default, both the Core API Server and the Execution API Server are served together:
42+
43+
.. code-block:: bash
44+
45+
airflow api-server
46+
# same as
47+
airflow api-server --apps all
48+
# or
49+
airflow api-server --apps core,execution
50+
51+
If you want to separate the Core API Server and the Execution API Server, you can run them
52+
separately. This might be useful for scaling them independently or for deploying them on different machines.
53+
54+
.. code-block:: bash
55+
56+
# serve only the Core API Server
57+
airflow api-server --apps core
58+
# serve only the Execution API Server
59+
airflow api-server --apps execution

0 commit comments

Comments
 (0)