From 91b033dd0bf5d5fbdf2b150a6a1d2e8f6e9eaa55 Mon Sep 17 00:00:00 2001 From: Kaxil Naik Date: Sun, 9 Aug 2020 11:45:37 +0100 Subject: [PATCH] Add Syntax Highlights to code-blocks in docs/best-practices.rst --- docs/best-practices.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/best-practices.rst b/docs/best-practices.rst index ec0a07ef9295a0..858cd7d663421f 100644 --- a/docs/best-practices.rst +++ b/docs/best-practices.rst @@ -261,7 +261,7 @@ Once you have changed the backend, airflow needs to create all the tables requir Create an empty DB and give airflow's user the permission to ``CREATE/ALTER`` it. Once that is done, you can run - -.. code-block:: +.. code-block:: bash airflow db upgrade @@ -305,14 +305,14 @@ Airflow comes bundled with a default ``airflow.cfg`` configuration file. You should use environment variables for configurations that change across deployments e.g. metadata DB, password, etc. You can accomplish this using the format :envvar:`AIRFLOW__{SECTION}__{KEY}` -.. code-block:: +.. code-block:: bash AIRFLOW__CORE__SQL_ALCHEMY_CONN=my_conn_id AIRFLOW__WEBSERVER__BASE_URL=http://host:port Some configurations such as the Airflow Backend connection URI can be derived from bash commands as well: -.. code-block:: +.. code-block:: ini sql_alchemy_conn_cmd = bash_command_to_run