INSTALL / BUILD instructions for Apache Airflow

Basic installation of Airflow from sources and development environment setup
============================================================================

This is a generic installation method that requires minimum standard tools to develop Airflow and
test it in a local virtual environment (using standard CPython installation and `pip`).

Depending on your system, you might need different prerequisites, but the following
systems/prerequisites are known to work:

Linux (Debian Bookworm):

    sudo apt install -y --no-install-recommends apt-transport-https apt-utils ca-certificates \
    curl dumb-init freetds-bin krb5-user libgeos-dev \
    ldap-utils libsasl2-2 libsasl2-modules libxmlsec1 locales libffi8 libldap-2.5-0 libssl3 netcat-openbsd \
    lsb-release openssh-client python3-selinux rsync sasl2-bin sqlite3 sudo unixodbc python3-dev \
    libkrb5-dev gcc libldap2-dev libsasl2-dev

Linux (Ubuntu Noble):

    sudo apt install -y --no-install-recommends apt-transport-https apt-utils ca-certificates \
    curl dumb-init freetds-bin krb5-user libgeos-dev \
    ldap-utils libsasl2-2 libsasl2-modules libxmlsec1 locales libffi8 libldap2 libssl3 netcat-openbsd \
    lsb-release openssh-client python3-selinux rsync sasl2-bin sqlite3 sudo unixodbc python3-dev \
    libkrb5-dev gcc libldap2-dev libsasl2-dev


You might need to install MariaDB development headers to build some of the dependencies

    sudo apt-get install libmariadb-dev libmariadbclient-dev

or
    sudo apt-get install libmariadb-dev libmariadb-dev-compat


On Linux you might also want to install postgres and mysql servers:


   sudo apt install postgresql mysql-server


MacOS (Mojave/Catalina) you might need to install XCode command line tools and brew and those packages:

    brew install sqlite mysql postgresql

The `pip` is one of the build packaging front-ends that might be used to install Airflow. It's the one
that we recommend (see below) for reproducible installation of specific versions of Airflow.

As of version 2.8, Airflow follows PEP 517/518 and uses `pyproject.toml` file to define build dependencies
and build process, and it requires relatively modern versions of packaging tools to get airflow built from
local sources or sdist packages, as PEP 517 compliant build hooks are used to determine dynamic build
dependencies. In the case of `pip` it means that at least version 22.1.0 is needed (released at the beginning of
2022) to build or install Airflow from sources. This does not affect the ability to install Airflow from
released wheel packages.

Downloading and installing Airflow from sources
-----------------------------------------------

While you can get Airflow sources in various ways (including cloning https://github.com/apache/airflow/), the
canonical way to download it is to fetch the tarball (published at https://downloads.apache.org), after
verifying the checksum and signatures of the downloaded file.

When you download source packages from https://downloads.apache.org, you download sources of Airflow and
all providers separately. However, when you clone the GitHub repository at https://github.com/apache/airflow/
you get all sources in one place. This is the most convenient way to develop Airflow and Providers together.
Otherwise, you have to install Airflow and Providers separately from sources in the same environment, which
is not as convenient.


Content of the source archive
-----------------------------

The archive contains a complete snapshot of the whole "apache-airflow" repository, including all
distributions that can be built from the sources: `apache-airflow` meta-distribution (that you can use to install
all other distributions, `apache-airflow-core`, `apache-airflow-task-sdk`, `apache-airflow-ctl`,
`apache-airflow-go-sdk`, more than 90 `apache-airflow-providers-<provider>` distributions, and
all the other distributions that are part of the monorepo and are needed to build other packages,
their documentation and also allows to run tests for all those distributions.

We are using `uv` and workspace tooling to build and manage the packages together, see below for more details.
Whatever distribution you choose to install, you need to localise the right `pyproject.toml` file in the
repository and this is the one that you should use to build the distribution you need.`

Using ``uv`` to manage your Python, virtualenvs, and install airflow for development (recommended)
==================================================================================================

While you can manually install airflow locally from sources, Airflow committers recommend using
uv - https://docs.astral.sh/uv/) as a build and development tool. It is a modern,
recently introduced popular packaging front-end tool and environment managers for Python.
It is an optional tool that is only really needed when you want to build packages from sources, you can use
many other packaging frontends (for example ``hatch``) but ``uv`` is very fast and convenient to manage
also your Python versions and virtualenvs.

Installing ``uv``
-----------------

You can install uv following the instructions: https://docs.astral.sh/uv/getting-started/installation/


Using ``uv`` to manage your project dependencies
------------------------------------------------

You can sync to latest versions of airflow dependencies using:

    uv sync

This will download and install appropriate python version, create a virtual environment in `.venv`
folder and installs all necessary dependencies needed to run tests for airflow and import providers.
This is the recommended way to install Airflow for development. You can repeat `uv sync` command any time
to synchronize your environment with the latest dependencies.

You can also synchronize all packages, including development dependencies of some providers, you can do it
by running the following command:

    uv sync --all-packages

With `uv` you can also install tools that are needed for other tasks described later - breeze,
prek, hatch, cherry-picker etc. It is highly recommended to install breeze and prek, hatch
and flit are useful to build packages (so might be useful by release managers), and cherry-picker is
useful for backporting changes to previous versions of Airflow.

    uv tool install -e ./dev/breeze
    uv tool install prek

    uv tool install hatch
    uv tool install flit

    uv tool install cherry-picker

Those are all tools useful for Airflow development.

It is recommended to run `prek install` after installing `prek` to install the git hooks - they
will take care about running airflow prek checks automatically.

    prek install

You can run any command in the virtual environment created by `uv` by prefixing it with `uv run`:

    uv run pytest
    uv run airflow standalone

This will automatically synchronize your dependencies to latest dependencies needed.


Compiling front-end assets for Airflow Core
-------------------------------------------

In order to see UI in Airflow, you need to compile front-end assets first.

In case you already installed `breeze` and `prek`, you can build the assets with
the following commands:

    prek --stage manual compile-ui-assets --all-files

or simply:

    breeze ui compile-assets

Both commands will install node and pmpm under the hood, to a dedicated prek
node environment and then build the assets.

If you want to manually run the build check for node and pnpm version in `.pre-commit-config.yaml` file,
and there are those manual ways to build the assets.

    pnpm install -frozen-lockfile --config.confirmModulesPurge=false
    pnpm run build

Finally, you can also clean and recompile assets with `custom` build target when running the Hatch build for
the ``airflow-core`` package.

    cd airflow-core
    hatch build -c -t custom

This will also clean-up the generated files,update `git_version` file in the Airflow package (used to display
it in the UI) that should contain the git commit hash of the build and it will generate the assets.

The result of this command is airflow sdist package built in the `dist` folder of `airflow-core`
package as well. It requires ``prek`` to be installed in your system.

There are also similar ``prek`` commands for other packages in the repository - for example:

```
compile-edge-assets    -- Compile Edge provider assets
compile-fab-assets     -- Compile FAB provider assets
```

However, the compiled, generated assets for those are checked in the repository and you do not need to
compile them manually before building the packages - you only need to do it when you modify the original
UI files for those packages.

Using pip and manually managing your virtualenv
===============================================

While `uv` manages dependencies and venv automatically and manage workspace automatically, you might want
to manage both manually with pip and virtualenv. You need to have Python installed in your preferred
way for that to work. It is also way slower than with `uv` and you need to manage your environment manually
and sometimes install several distributions together to make tests and documentation work - emulating what
workspace tooling does automatically.

Creating virtualenv
-------------------

Airflow pulls in quite a lot of dependencies to connect to other services. You generally want to
test or run Airflow from a virtualenv to ensure those dependencies are separated from your system-wide
 versions. Using system-installed Python installation is strongly discouraged as the versions of Python
shipped with the operating system often have some limitations and are not up to date. It is recommended
to install Python using the official release (https://www.python.org/downloads/), or Python project
management tools such as Hatch. See later for a description of `Hatch` as one of the tools that
is Airflow's tool of choice to build Airflow packages.

Once you have a suitable Python version installed, you can create a virtualenv and activate it:

    python3 -m venv PATH_TO_YOUR_VENV
    source PATH_TO_YOUR_VENV/bin/activate

Building airflow packages with Hatch
====================================

While building packages will work with any compliant packaging front-end tool, for reproducibility, we
recommend using ``hatch``. It is a modern, fast, and convenient tool to build packages from sources managed
by the Python Packaging Authority. It is also used by Airflow to build packages in CI/CD as well as by
release managers to build locally packages for verification of reproducibility of the build.

Installing ``hatch``
--------------------

More information about hatch can be found in https://hatch.pypa.io/

We recommend to install ``hatch`` using ```uv tool`` command which will make hatch available as a CLI
command globally:

    uv tool install hatch

You can still install ``hatch`` using ``pipx`` if you prefer:

    pipx install hatch


It's important to keep your hatch up to date. You can do this by running:

    uv tool upgrade hatch


Using Hatch to build packages
-----------------------------

You can use Hatch to build installable packages from the Airflow sources. Such package will
include all metadata configured in `pyproject.toml` and will be installable with ``pip`` and and any other
PEP-compliant packaging front-end. You can run those commands in:

* root folder of the repository to build "meta" airflow distribution that install other distribution
* `airflow-core` folder to build the core airflow distribution
* any of the `providers` folders that has a pyproject.toml file to build the provider distribution
* task-sdk to build the task-sdk distribution
* airflow-ctl to build the airflow-ctl distribution
* task-go-sdk to build the task-go-sdk distribution

The packages will have pre-installed dependencies for providers that are available when Airflow is i
onstalled from PyPI. Both `wheel` and `sdist` packages are built by default.

    hatch build

You can also build only `wheel` or `sdist` packages:

    hatch build -t wheel
    hatch build -t sdist

In the `airflow-core` folder, you should also build the package with the `custom` target that will clean
the build directory, update the `git_version` file, and build the assets (in case you have not built
them already manually with `prek`):

    hatch build -t custom -t wheel -t sdist


Installing recommended version of dependencies
==============================================

Whatever virtualenv solution you use, when you want to make sure you are using the same
version of dependencies as in main, you can install the recommended version of the dependencies by using
constraint-python<PYTHON_MAJOR_MINOR_VERSION>.txt files as `constraint` file. This might be useful
to avoid "works-for-me" syndrome, where you use different versions of dependencies than the ones
that are used in main CI tests and by other contributors.

There are different constraint files for different Python versions. For example, this command will install
all basic devel requirements and requirements of Google provider as last successfully tested for Python 3.10:

   pip install -e ".[devel,google]"" \
      --constraint "https://raw.githubusercontent.com/apache/airflow/constraints-main/constraints-3.10.txt"

Using the 'constraints-no-providers' constraint files, you can upgrade Airflow without paying attention to the provider's dependencies. This allows you to keep installed provider dependencies and install the latest supported ones using pure Airflow core.

  pip install -e ".[devel]" \
     --constraint "https://raw.githubusercontent.com/apache/airflow/constraints-main/constraints-no-providers-3.10.txt"

Note that you can also use `uv pip install` if you use `uv`.

Airflow extras
==============

Airflow has several extras that you can install to get additional dependencies. They sometimes install
providers, sometimes enable other features where packages are not installed by default.

You can read more about those extras in the extras reference:
https://airflow.apache.org/docs/apache-airflow/stable/extra-packages-ref.html