You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 9754958
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: airflow-core/docs/administration-and-deployment/web-stack.rst
+27Lines changed: 27 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,10 @@
20
20
Web Stack
21
21
=========
22
22
23
+
24
+
Configuration
25
+
-------------
26
+
23
27
Sometimes you want to deploy the backend and frontend behind a
24
28
variable url path prefix. To do so, you can configure the url :ref:`config:api__base_url`
25
29
for instance, set it to ``http://localhost:28080/d12345``. All the APIs routes will
@@ -30,3 +34,26 @@ and served successfully.
30
34
You will also need to update the execution API server url
31
35
:ref:`config:core__execution_api_server_url` for tasks to be able to reach the API
32
36
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.
0 commit comments