This is an automated email from the ASF dual-hosted git repository. kaxilnaik pushed a commit to branch v1-10-test in repository https://gitbox.apache.org/repos/asf/airflow.git
commit 046eb6a6a77daf1e60063a796d9416221ecae3dd Author: Kaxil Naik <[email protected]> AuthorDate: Sun Aug 9 12:18:58 2020 +0100 Add Syntax Highlights to code-blocks in docs/best-practices.rst (#10258) (cherry picked from commit e0548706892216a2883afacd3dd00ca66add3d32) --- 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 fe25977..2ffb052 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 upgradedb @@ -305,14 +305,14 @@ Airflow comes bundles with a default ``airflow.cfg`` configuration file. You should use environment variables for configurations that change across deployments e.g. metadata DB, password. You can do it using the format ``$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 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
