Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 13 additions & 4 deletions docs/start.rst
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,9 @@ The installation is quick and straightforward.
airflow scheduler

# visit localhost:8080 in the browser and use the admin account you just
# created to login. Enable the example dag in the home page
# created to login. Enable one of the example dags in the home page.
# example_bash_operator might be the most straightforward. Visit the page
# of the DAG you activated to monitor the status of its runs.

Upon running these commands, Airflow will create the ``$AIRFLOW_HOME`` folder
and lay an "airflow.cfg" file with defaults that get you going fast. You can
Expand All @@ -61,9 +63,7 @@ only run task instances sequentially. While this is very limiting, it allows
you to get up and running quickly and take a tour of the UI and the
command line utilities.

Here are a few commands that will trigger a few task instances. You should
be able to see the status of the jobs change in the ``example_bash_operator`` DAG as you
run the commands below.
Here are a few commands that will trigger a few task instances.

.. code-block:: bash

Expand All @@ -72,6 +72,15 @@ run the commands below.
# run a backfill over 2 days
airflow dags backfill example_bash_operator -s 2015-01-01 -e 2015-01-02

On running these commands, stdout should inform you of the status of the
task instances and DAG runs triggered.

You can also monitor the states of these from the web UI. After running
the ``airflow tasks run`` command, you can visit localhost:8080 and go to
``Browse->Task Instances`` to see the status of the task instance created.
After running the ``airflow dags backfill`` command, you can go to the page of
the ``example_bash_operator`` DAG, to see the status of the DAG runs created.

What's Next?
''''''''''''
From this point, you can head to the :doc:`tutorial` section for further examples or the :doc:`howto/index` section if you're ready to get your hands dirty.