This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch gh-pages
in repository https://gitbox.apache.org/repos/asf/airflow-site.git
The following commit(s) were added to refs/heads/gh-pages by this push:
new 26e4962897 Deploying to gh-pages from @
f29dc4f4b48882f4dba3dd831d173ae072c76563 🚀
26e4962897 is described below
commit 26e49628976d4d5f43e1cb99517798aa1562e458
Author: potiuk <[email protected]>
AuthorDate: Tue May 23 11:12:02 2023 +0000
Deploying to gh-pages from @ f29dc4f4b48882f4dba3dd831d173ae072c76563 🚀
---
blog/airflow-1.10.10/index.html | 4 +-
blog/airflow-1.10.12/index.html | 4 +-
blog/airflow-1.10.8-1.10.9/index.html | 4 +-
blog/airflow-2.2.0/index.html | 4 +-
blog/airflow-2.3.0/index.html | 4 +-
blog/airflow-2.4.0/index.html | 4 +-
blog/airflow-2.5.0/index.html | 4 +-
blog/airflow-2.6.0/index.html | 4 +-
blog/airflow-survey-2020/index.html | 4 +-
blog/airflow-survey-2022/index.html | 4 +-
blog/airflow-survey/index.html | 4 +-
blog/airflow-two-point-oh-is-here/index.html | 4 +-
blog/airflow_summit_2021/index.html | 4 +-
blog/airflow_summit_2022/index.html | 4 +-
blog/announcing-new-website/index.html | 4 +-
blog/apache-airflow-for-newcomers/index.html | 4 +-
.../index.html | 4 +-
.../index.html | 4 +-
.../index.html | 4 +-
.../index.html | 4 +-
.../index.html | 4 +-
.../index.html | 4 +-
docs/docker-stack/_modules/index.html | 1 +
docs/docker-stack/_sources/build.rst.txt | 55 ++++++++++
docs/docker-stack/build.html | 112 ++++++++++++++++-----
docs/docker-stack/recipes.html | 6 +-
docs/docker-stack/searchindex.js | 2 +-
index.html | 32 +++---
search/index.html | 4 +-
sitemap.xml | 102 +++++++++----------
use-cases/adobe/index.html | 4 +-
use-cases/adyen/index.html | 4 +-
use-cases/big-fish-games/index.html | 4 +-
use-cases/dish/index.html | 4 +-
use-cases/experity/index.html | 4 +-
use-cases/onefootball/index.html | 4 +-
use-cases/plarium-krasnodar/index.html | 4 +-
use-cases/seniorlink/index.html | 4 +-
use-cases/sift/index.html | 4 +-
39 files changed, 280 insertions(+), 158 deletions(-)
diff --git a/blog/airflow-1.10.10/index.html b/blog/airflow-1.10.10/index.html
index 06f3838ea2..7ba9c625a8 100644
--- a/blog/airflow-1.10.10/index.html
+++ b/blog/airflow-1.10.10/index.html
@@ -34,11 +34,11 @@
<meta property="og:type" content="article" />
<meta property="og:url" content="/blog/airflow-1.10.10/" /><meta
property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="blog" />
<meta property="article:published_time" content="2020-04-09T00:00:00+00:00" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Apache Airflow 1.10.10">
<meta itemprop="description" content="We are happy to present Apache Airflow
1.10.10"><meta itemprop="datePublished" content="2020-04-09T00:00:00+00:00" />
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="1143"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="release," /><meta name="twitter:card"
content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/blog/airflow-1.10.12/index.html b/blog/airflow-1.10.12/index.html
index 5510d41193..b0d2d9638f 100644
--- a/blog/airflow-1.10.12/index.html
+++ b/blog/airflow-1.10.12/index.html
@@ -34,11 +34,11 @@
<meta property="og:type" content="article" />
<meta property="og:url" content="/blog/airflow-1.10.12/" /><meta
property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="blog" />
<meta property="article:published_time" content="2020-08-25T00:00:00+00:00" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Apache Airflow 1.10.12">
<meta itemprop="description" content="We are happy to present Apache Airflow
1.10.12"><meta itemprop="datePublished" content="2020-08-25T00:00:00+00:00" />
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="911"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="release," /><meta name="twitter:card"
content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/blog/airflow-1.10.8-1.10.9/index.html
b/blog/airflow-1.10.8-1.10.9/index.html
index b1d35932ad..062c1a4fa4 100644
--- a/blog/airflow-1.10.8-1.10.9/index.html
+++ b/blog/airflow-1.10.8-1.10.9/index.html
@@ -34,11 +34,11 @@
<meta property="og:type" content="article" />
<meta property="og:url" content="/blog/airflow-1.10.8-1.10.9/" /><meta
property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="blog" />
<meta property="article:published_time" content="2020-02-23T00:00:00+00:00" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Apache Airflow 1.10.8 & 1.10.9">
<meta itemprop="description" content="We are happy to present the new 1.10.8
and 1.10.9 releases of Apache Airflow."><meta itemprop="datePublished"
content="2020-02-23T00:00:00+00:00" />
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="437"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="release," /><meta name="twitter:card"
content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/blog/airflow-2.2.0/index.html b/blog/airflow-2.2.0/index.html
index d98ef22024..3c31298f72 100644
--- a/blog/airflow-2.2.0/index.html
+++ b/blog/airflow-2.2.0/index.html
@@ -34,11 +34,11 @@
<meta property="og:type" content="article" />
<meta property="og:url" content="/blog/airflow-2.2.0/" /><meta
property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="blog" />
<meta property="article:published_time" content="2021-10-11T00:00:00+00:00" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="What's new in Apache Airflow 2.2.0">
<meta itemprop="description" content="We're proud to announce that Apache
Airflow 2.2.0 has been released."><meta itemprop="datePublished"
content="2021-10-11T00:00:00+00:00" />
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="658"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="Release," /><meta name="twitter:card"
content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/blog/airflow-2.3.0/index.html b/blog/airflow-2.3.0/index.html
index 8330035eec..8c733228ab 100644
--- a/blog/airflow-2.3.0/index.html
+++ b/blog/airflow-2.3.0/index.html
@@ -34,11 +34,11 @@
<meta property="og:type" content="article" />
<meta property="og:url" content="/blog/airflow-2.3.0/" /><meta
property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="blog" />
<meta property="article:published_time" content="2022-04-30T00:00:00+00:00" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Apache Airflow 2.3.0 is here">
<meta itemprop="description" content="We're proud to announce that Apache
Airflow 2.3.0 has been released."><meta itemprop="datePublished"
content="2022-04-30T00:00:00+00:00" />
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="708"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="Release," /><meta name="twitter:card"
content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/blog/airflow-2.4.0/index.html b/blog/airflow-2.4.0/index.html
index da110638d0..a3fbd93ad5 100644
--- a/blog/airflow-2.4.0/index.html
+++ b/blog/airflow-2.4.0/index.html
@@ -34,11 +34,11 @@
<meta property="og:type" content="article" />
<meta property="og:url" content="/blog/airflow-2.4.0/" /><meta
property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="blog" />
<meta property="article:published_time" content="2022-09-19T00:00:00+00:00" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Apache Airflow 2.4.0: That Data Aware Release">
<meta itemprop="description" content="We're proud to announce that Apache
Airflow 2.4.0 has been released with many exciting improvements."><meta
itemprop="datePublished" content="2022-09-19T00:00:00+00:00" />
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="848"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="Release," /><meta name="twitter:card"
content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/blog/airflow-2.5.0/index.html b/blog/airflow-2.5.0/index.html
index 51a7ebb2a6..ccb8d23dc8 100644
--- a/blog/airflow-2.5.0/index.html
+++ b/blog/airflow-2.5.0/index.html
@@ -34,11 +34,11 @@
<meta property="og:type" content="article" />
<meta property="og:url" content="/blog/airflow-2.5.0/" /><meta
property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="blog" />
<meta property="article:published_time" content="2022-12-02T00:00:00+00:00" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Apache Airflow 2.5.0: Tick-Tock">
<meta itemprop="description" content="We're proud to announce that Apache
Airflow 2.5.0 has been released with many quality of life changes."><meta
itemprop="datePublished" content="2022-12-02T00:00:00+00:00" />
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="392"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="Release," /><meta name="twitter:card"
content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/blog/airflow-2.6.0/index.html b/blog/airflow-2.6.0/index.html
index 6ebf9b8483..f7c784657e 100644
--- a/blog/airflow-2.6.0/index.html
+++ b/blog/airflow-2.6.0/index.html
@@ -34,11 +34,11 @@
<meta property="og:type" content="article" />
<meta property="og:url" content="/blog/airflow-2.6.0/" /><meta
property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="blog" />
<meta property="article:published_time" content="2023-04-30T00:00:00+00:00" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="what's new in Apache Airflow 2.6.0">
<meta itemprop="description" content="Apache Airflow 2.6.0 has been
released!"><meta itemprop="datePublished" content="2023-04-30T00:00:00+00:00" />
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="535"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="Release," /><meta name="twitter:card"
content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/blog/airflow-survey-2020/index.html
b/blog/airflow-survey-2020/index.html
index 41e4c0bdda..34c40e7628 100644
--- a/blog/airflow-survey-2020/index.html
+++ b/blog/airflow-survey-2020/index.html
@@ -34,11 +34,11 @@
<meta property="og:type" content="article" />
<meta property="og:url" content="/blog/airflow-survey-2020/" /><meta
property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="blog" />
<meta property="article:published_time" content="2021-03-09T00:00:00+00:00" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Airflow Survey 2020">
<meta itemprop="description" content="We observe steady growth in number of
users as well as in an amount of active contributors. So listening and
understanding our community is of high importance."><meta
itemprop="datePublished" content="2021-03-09T00:00:00+00:00" />
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="2136"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="community,survey,users," /><meta
name="twitter:card" content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/blog/airflow-survey-2022/index.html
b/blog/airflow-survey-2022/index.html
index e180e6dbb8..413f96dbd6 100644
--- a/blog/airflow-survey-2022/index.html
+++ b/blog/airflow-survey-2022/index.html
@@ -34,11 +34,11 @@
<meta property="og:type" content="article" />
<meta property="og:url" content="/blog/airflow-survey-2022/" /><meta
property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="blog" />
<meta property="article:published_time" content="2022-06-17T00:00:00+00:00" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Airflow Survey 2022">
<meta itemprop="description" content="2021 saw rapid adoption of Airflow 2,
and continued growth of the community. This annual survey helps us understand
how people are using Airflow, and where we can best focus our efforts going
forward."><meta itemprop="datePublished" content="2022-06-17T00:00:00+00:00" />
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="3865"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="community,survey,users," /><meta
name="twitter:card" content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/blog/airflow-survey/index.html b/blog/airflow-survey/index.html
index a11050c8c4..bc12714069 100644
--- a/blog/airflow-survey/index.html
+++ b/blog/airflow-survey/index.html
@@ -34,11 +34,11 @@
<meta property="og:type" content="article" />
<meta property="og:url" content="/blog/airflow-survey/" /><meta
property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="blog" />
<meta property="article:published_time" content="2019-12-11T00:00:00+00:00" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Airflow Survey 2019">
<meta itemprop="description" content="Receiving and adjusting to our users’
feedback is a must. Let’s see who Airflow users are, how they play with it, and
what they miss."><meta itemprop="datePublished"
content="2019-12-11T00:00:00+00:00" />
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="1775"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="community,survey,users," /><meta
name="twitter:card" content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/blog/airflow-two-point-oh-is-here/index.html
b/blog/airflow-two-point-oh-is-here/index.html
index 4089fe928a..e9db4c5232 100644
--- a/blog/airflow-two-point-oh-is-here/index.html
+++ b/blog/airflow-two-point-oh-is-here/index.html
@@ -34,11 +34,11 @@
<meta property="og:type" content="article" />
<meta property="og:url" content="/blog/airflow-two-point-oh-is-here/" /><meta
property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="blog" />
<meta property="article:published_time" content="2020-12-17T00:00:00+00:00" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Apache Airflow 2.0 is here!">
<meta itemprop="description" content="We're proud to announce that Apache
Airflow 2.0.0 has been released."><meta itemprop="datePublished"
content="2020-12-17T00:00:00+00:00" />
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="1165"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="Release," /><meta name="twitter:card"
content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/blog/airflow_summit_2021/index.html
b/blog/airflow_summit_2021/index.html
index 4dc276a661..3186d46732 100644
--- a/blog/airflow_summit_2021/index.html
+++ b/blog/airflow_summit_2021/index.html
@@ -34,11 +34,11 @@
<meta property="og:type" content="article" />
<meta property="og:url" content="/blog/airflow_summit_2021/" /><meta
property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="blog" />
<meta property="article:published_time" content="2021-03-21T00:00:00+00:00" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Airflow Summit 2021">
<meta itemprop="description" content="We are thrilled about Airflow Summit
2021!"><meta itemprop="datePublished" content="2021-03-21T00:00:00+00:00" />
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="77"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="Community,Airflow Summit," /><meta
name="twitter:card" content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/blog/airflow_summit_2022/index.html
b/blog/airflow_summit_2022/index.html
index 864fe9a934..71d5e4998d 100644
--- a/blog/airflow_summit_2022/index.html
+++ b/blog/airflow_summit_2022/index.html
@@ -34,11 +34,11 @@
<meta property="og:type" content="article" />
<meta property="og:url" content="/blog/airflow_summit_2022/" /><meta
property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="blog" />
<meta property="article:published_time" content="2022-05-16T00:00:00+00:00" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Airflow Summit 2022">
<meta itemprop="description" content="Airflow Summit 2022 is here"><meta
itemprop="datePublished" content="2022-05-16T00:00:00+00:00" />
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="129"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="Community,Airflow Summit," /><meta
name="twitter:card" content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/blog/announcing-new-website/index.html
b/blog/announcing-new-website/index.html
index b13b1c0b6e..d69e405a93 100644
--- a/blog/announcing-new-website/index.html
+++ b/blog/announcing-new-website/index.html
@@ -34,11 +34,11 @@
<meta property="og:type" content="article" />
<meta property="og:url" content="/blog/announcing-new-website/" /><meta
property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="blog" />
<meta property="article:published_time" content="2019-12-11T00:00:00+00:00" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="New Airflow website">
<meta itemprop="description" content="We are thrilled about our new
website!"><meta itemprop="datePublished" content="2019-12-11T00:00:00+00:00" />
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="282"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="Community," /><meta name="twitter:card"
content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/blog/apache-airflow-for-newcomers/index.html
b/blog/apache-airflow-for-newcomers/index.html
index e24fd029af..d92bb18d51 100644
--- a/blog/apache-airflow-for-newcomers/index.html
+++ b/blog/apache-airflow-for-newcomers/index.html
@@ -35,12 +35,12 @@ Authoring Workflow in Apache Airflow. Airflow makes it easy
to author workflows
<meta property="og:type" content="article" />
<meta property="og:url" content="/blog/apache-airflow-for-newcomers/" /><meta
property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="blog" />
<meta property="article:published_time" content="2020-08-17T00:00:00+00:00" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Apache Airflow For Newcomers">
<meta itemprop="description" content="Apache Airflow is a platform to
programmatically author, schedule, and monitor workflows. A workflow is a
sequence of tasks that processes a set of data. You can think of workflow as
the path that describes how tasks go from being undone to done. Scheduling, on
the other hand, is the process of planning, controlling, and optimizing when a
particular task should be done.
Authoring Workflow in Apache Airflow. Airflow makes it easy to author
workflows using python scripts."><meta itemprop="datePublished"
content="2020-08-17T00:00:00+00:00" />
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="1070"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="Community," /><meta name="twitter:card"
content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git
a/blog/apache-con-europe-2019-thoughts-and-insights-by-airflow-committers/index.html
b/blog/apache-con-europe-2019-thoughts-and-insights-by-airflow-committers/index.html
index c1b451f35c..27770ce70f 100644
---
a/blog/apache-con-europe-2019-thoughts-and-insights-by-airflow-committers/index.html
+++
b/blog/apache-con-europe-2019-thoughts-and-insights-by-airflow-committers/index.html
@@ -34,11 +34,11 @@
<meta property="og:type" content="article" />
<meta property="og:url"
content="/blog/apache-con-europe-2019-thoughts-and-insights-by-airflow-committers/"
/><meta property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="blog" />
<meta property="article:published_time" content="2019-11-22T00:00:00+00:00" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="ApacheCon Europe 2019 — Thoughts and Insights
by Airflow Committers">
<meta itemprop="description" content="Here come some thoughts by Airflow
committers and contributors from the ApacheCon Europe 2019. Get to know the ASF
community!"><meta itemprop="datePublished" content="2019-11-22T00:00:00+00:00"
/>
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="138"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="Community," /><meta name="twitter:card"
content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/blog/documenting-using-local-development-environments/index.html
b/blog/documenting-using-local-development-environments/index.html
index bfa3463c71..bcbe0694ec 100644
--- a/blog/documenting-using-local-development-environments/index.html
+++ b/blog/documenting-using-local-development-environments/index.html
@@ -34,11 +34,11 @@
<meta property="og:type" content="article" />
<meta property="og:url"
content="/blog/documenting-using-local-development-environments/" /><meta
property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="blog" />
<meta property="article:published_time" content="2019-11-22T00:00:00+00:00" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Documenting using local development
environment">
<meta itemprop="description" content="The story behind documenting local
development environment of Apache Airflow"><meta itemprop="datePublished"
content="2019-11-22T00:00:00+00:00" />
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="256"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="Development," /><meta name="twitter:card"
content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git
a/blog/experience-in-google-season-of-docs-2019-with-apache-airflow/index.html
b/blog/experience-in-google-season-of-docs-2019-with-apache-airflow/index.html
index 67f7d29916..9b16575853 100644
---
a/blog/experience-in-google-season-of-docs-2019-with-apache-airflow/index.html
+++
b/blog/experience-in-google-season-of-docs-2019-with-apache-airflow/index.html
@@ -35,12 +35,12 @@ About Me I have been writing tech articles on medium as
well as my blog for the
<meta property="og:type" content="article" />
<meta property="og:url"
content="/blog/experience-in-google-season-of-docs-2019-with-apache-airflow/"
/><meta property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="blog" />
<meta property="article:published_time" content="2019-12-20T00:00:00+00:00" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Experience in Google Season of Docs 2019 with
Apache Airflow">
<meta itemprop="description" content="I came across Google Season of Docs
(GSoD) almost by accident, thanks to my extensive HackerNews and Twitter
addiction. I was familiar with the Google Summer of Code but not with this
program. It turns out it was the inaugural phase. I read the details, and the
process felt a lot like GSoC except that this was about documentation.
About Me I have been writing tech articles on medium as well as my blog for
the past 1."><meta itemprop="datePublished" content="2019-12-20T00:00:00+00:00"
/>
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="1521"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="Documentation," /><meta name="twitter:card"
content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/blog/experience-with-airflow-as-an-outreachy-intern/index.html
b/blog/experience-with-airflow-as-an-outreachy-intern/index.html
index 4163bfd7ae..d32854805a 100644
--- a/blog/experience-with-airflow-as-an-outreachy-intern/index.html
+++ b/blog/experience-with-airflow-as-an-outreachy-intern/index.html
@@ -35,12 +35,12 @@ Contribution Period The first thing I had to do was choose
a project under an or
<meta property="og:type" content="article" />
<meta property="og:url"
content="/blog/experience-with-airflow-as-an-outreachy-intern/" /><meta
property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="blog" />
<meta property="article:published_time" content="2020-08-30T00:00:00+00:00" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Journey with Airflow as an Outreachy Intern">
<meta itemprop="description" content="Outreachy is a program which organises
three months paid internships with FOSS projects for people who are typically
underrepresented in those projects.
Contribution Period The first thing I had to do was choose a project under an
organisation. After going through all the projects I chose “Extending the REST
API of Apache Airflow”, because I had a good idea of what REST API(s) are, so I
thought it would be easier to get started with the contributions."><meta
itemprop="datePublished" content="2020-08-30T00:00:00+00:00" />
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="528"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="Community," /><meta name="twitter:card"
content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/blog/implementing-stable-api-for-apache-airflow/index.html
b/blog/implementing-stable-api-for-apache-airflow/index.html
index afa418b9ad..beb7583a70 100644
--- a/blog/implementing-stable-api-for-apache-airflow/index.html
+++ b/blog/implementing-stable-api-for-apache-airflow/index.html
@@ -34,11 +34,11 @@
<meta property="og:type" content="article" />
<meta property="og:url"
content="/blog/implementing-stable-api-for-apache-airflow/" /><meta
property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="blog" />
<meta property="article:published_time" content="2020-07-19T00:00:00+00:00" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Implementing Stable API for Apache Airflow">
<meta itemprop="description" content="An Outreachy intern's progress
report on contributing to Apache Airflow REST API."><meta
itemprop="datePublished" content="2020-07-19T00:00:00+00:00" />
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="703"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="REST API," /><meta name="twitter:card"
content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/blog/its-a-breeze-to-develop-apache-airflow/index.html
b/blog/its-a-breeze-to-develop-apache-airflow/index.html
index 654f734b67..53d8454431 100644
--- a/blog/its-a-breeze-to-develop-apache-airflow/index.html
+++ b/blog/its-a-breeze-to-develop-apache-airflow/index.html
@@ -34,11 +34,11 @@
<meta property="og:type" content="article" />
<meta property="og:url"
content="/blog/its-a-breeze-to-develop-apache-airflow/" /><meta
property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="blog" />
<meta property="article:published_time" content="2019-11-22T00:00:00+00:00" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="It's a "Breeze" to develop Apache
Airflow">
<meta itemprop="description" content="A Principal Software Engineer's
journey to developer productivity. Learn how Jarek and his team sped up and
simplified Airflow development for the community."><meta
itemprop="datePublished" content="2019-11-22T00:00:00+00:00" />
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="124"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="Development," /><meta name="twitter:card"
content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/docs/docker-stack/_modules/index.html
b/docs/docker-stack/_modules/index.html
index 42fddff612..3a01b19c9c 100644
--- a/docs/docker-stack/_modules/index.html
+++ b/docs/docker-stack/_modules/index.html
@@ -561,6 +561,7 @@
<li><a
href="docs/docker-stack/docker-examples/extending/add-providers/Dockerf.html">docs.docker-stack.docker-examples.extending.add-providers.Dockerf</a></li>
<li><a
href="docs/docker-stack/docker-examples/extending/add-pypi-packages/Dockerf.html">docs.docker-stack.docker-examples.extending.add-pypi-packages.Dockerf</a></li>
<li><a
href="docs/docker-stack/docker-examples/extending/add-requirement-packages/Dockerf.html">docs.docker-stack.docker-examples.extending.add-requirement-packages.Dockerf</a></li>
+<li><a
href="docs/docker-stack/docker-examples/extending/add-requirement-packages/requirements/.html">docs.docker-stack.docker-examples.extending.add-requirement-packages.requirements.</a></li>
<li><a
href="docs/docker-stack/docker-examples/extending/custom-providers/Dockerf.html">docs.docker-stack.docker-examples.extending.custom-providers.Dockerf</a></li>
<li><a
href="docs/docker-stack/docker-examples/extending/embedding-dags/Dockerf.html">docs.docker-stack.docker-examples.extending.embedding-dags.Dockerf</a></li>
<li><a
href="docs/docker-stack/docker-examples/extending/writable-directory/Dockerf.html">docs.docker-stack.docker-examples.extending.writable-directory.Dockerf</a></li>
diff --git a/docs/docker-stack/_sources/build.rst.txt
b/docs/docker-stack/_sources/build.rst.txt
index 0020697cdb..5d14ba86cd 100644
--- a/docs/docker-stack/_sources/build.rst.txt
+++ b/docs/docker-stack/_sources/build.rst.txt
@@ -55,6 +55,17 @@ The following example adds ``lxml`` python package from PyPI
to the image. When
``pip`` you need to use the ``airflow`` user rather than ``root``. Attempts to
install ``pip`` packages
as ``root`` will fail with an appropriate error message.
+.. note::
+ In the example below, we also add apache-airflow package to be installed -
in the very same version
+ that the image version you used it from. This is not strictly necessary,
but it is a good practice
+ to always install the same version of apache-airflow as the one you are
using. This way you can
+ be sure that the version you are using is the same as the one you are
extending. In some cases where
+ your new packages have conflicting dependencies, ``pip`` might decide to
downgrade or upgrade
+ apache-airflow for you, so adding it explicitly is a good practice - this
way if you have conflicting
+ requirements, you will get an error message with conflict information,
rather than a surprise
+ downgrade or upgrade of airflow. If you upgrade airflow base image, you
should also update the version
+ to match the new version of airflow.
+
.. exampleinclude:: docker-examples/extending/add-pypi-packages/Dockerfile
:language: Dockerfile
:start-after: [START Dockerfile]
@@ -67,11 +78,26 @@ The following example adds few python packages from
``requirements.txt`` from Py
Note that similarly when adding individual packages, you need to use the
``airflow`` user rather than
``root``. Attempts to install ``pip`` packages as ``root`` will fail with an
appropriate error message.
+.. note::
+ In the example below, we also add apache-airflow package to be installed -
in the very same version
+ that the image version you used it from. This is not strictly necessary,
but it is a good practice
+ to always install the same version of apache-airflow as the one you are
using. This way you can
+ be sure that the version you are using is the same as the one you are
extending. In some cases where
+ your new packages have conflicting dependencies, ``pip`` might decide to
downgrade or upgrade
+ apache-airflow for you, so adding it explicitly is a good practice - this
way if you have conflicting
+ requirements, you will get an error message with conflict information,
rather than a surprise
+ downgrade or upgrade of airflow. If you upgrade airflow base image, you
should also update the version
+ to match the new version of airflow.
+
+
.. exampleinclude::
docker-examples/extending/add-requirement-packages/Dockerfile
:language: Dockerfile
:start-after: [START Dockerfile]
:end-before: [END Dockerfile]
+.. exampleinclude::
docker-examples/extending/add-requirement-packages/requirements.txt
+ :language: text
+
Embedding DAGs
..............
@@ -266,8 +292,11 @@ Naming conventions for the images:
| Image | Python | Standard image | Slim
image |
+================+==================+=================================+======================================+
| Latest default | 3.7 | apache/airflow:latest |
apache/airflow:slim-latest |
++----------------+------------------+---------------------------------+--------------------------------------+
| Default | 3.7 | apache/airflow:X.Y.Z |
apache/airflow:slim-X.Y.Z |
++----------------+------------------+---------------------------------+--------------------------------------+
| Latest | 3.7,3.8,3.9,3.10 | apache/airflow:latest-pythonN.M |
apache/airflow:slim-latest-pythonN.M |
++----------------+------------------+---------------------------------+--------------------------------------+
| Specific | 3.7,3.8,3.9,3.10 | apache/airflow:X.Y.Z-pythonN.M |
apache/airflow:slim-X.Y.Z-pythonN.M |
+----------------+------------------+---------------------------------+--------------------------------------+
@@ -385,11 +414,25 @@ The following example adds few python packages from
``requirements.txt`` from Py
Note that similarly when adding individual packages, you need to use the
``airflow`` user rather than
``root``. Attempts to install ``pip`` packages as ``root`` will fail with an
appropriate error message.
+.. note::
+ In the example below, we also add apache-airflow package to be installed -
in the very same version
+ that the image version you used it from. This is not strictly necessary,
but it is a good practice
+ to always install the same version of apache-airflow as the one you are
using. This way you can
+ be sure that the version you are using is the same as the one you are
extending. In some cases where
+ your new packages have conflicting dependencies, ``pip`` might decide to
downgrade or upgrade
+ apache-airflow for you, so adding it explicitly is a good practice - this
way if you have conflicting
+ requirements, you will get an error message with conflict information,
rather than a surprise
+ downgrade or upgrade of airflow. If you upgrade airflow base image, you
should also update the version
+ to match the new version of airflow.
+
.. exampleinclude::
docker-examples/extending/add-requirement-packages/Dockerfile
:language: Dockerfile
:start-after: [START Dockerfile]
:end-before: [END Dockerfile]
+.. exampleinclude::
docker-examples/extending/add-requirement-packages/requirements.txt
+ :language: text
+
Example when writable directory is needed
.........................................
@@ -558,6 +601,18 @@ You can use ``docker-context-files`` for the following
purposes:
* you can place ``requirements.txt`` and add any ``pip`` packages you want to
install in the
``docker-context-file`` folder. Those requirements will be automatically
installed during the build.
+.. note::
+ In the example below, we also add apache-airflow package to be installed -
in the very same version
+ that the image version you used it from. This is not strictly necessary,
but it is a good practice
+ to always install the same version of apache-airflow as the one you are
using. This way you can
+ be sure that the version you are using is the same as the one you are
extending. In some cases where
+ your new packages have conflicting dependencies, ``pip`` might decide to
downgrade or upgrade
+ apache-airflow for you, so adding it explicitly is a good practice - this
way if you have conflicting
+ requirements, you will get an error message with conflict information,
rather than a surprise
+ downgrade or upgrade of airflow. If you upgrade airflow base image, you
should also update the version
+ to match the new version of airflow.
+
+
.. exampleinclude:: docker-examples/customizing/own-requirements.sh
:language: bash
:start-after: [START build]
diff --git a/docs/docker-stack/build.html b/docs/docker-stack/build.html
index 211c98b83a..d23f19f52d 100644
--- a/docs/docker-stack/build.html
+++ b/docs/docker-stack/build.html
@@ -674,10 +674,22 @@ switch to the <code class="docutils literal
notranslate"><span class="pre">root<
<p>The following example adds <code class="docutils literal notranslate"><span
class="pre">lxml</span></code> python package from PyPI to the image. When
adding packages via
<code class="docutils literal notranslate"><span class="pre">pip</span></code>
you need to use the <code class="docutils literal notranslate"><span
class="pre">airflow</span></code> user rather than <code class="docutils
literal notranslate"><span class="pre">root</span></code>. Attempts to install
<code class="docutils literal notranslate"><span class="pre">pip</span></code>
packages
as <code class="docutils literal notranslate"><span
class="pre">root</span></code> will fail with an appropriate error message.</p>
+<div class="admonition note">
+<p class="admonition-title">Note</p>
+<p>In the example below, we also add apache-airflow package to be installed -
in the very same version
+that the image version you used it from. This is not strictly necessary, but
it is a good practice
+to always install the same version of apache-airflow as the one you are using.
This way you can
+be sure that the version you are using is the same as the one you are
extending. In some cases where
+your new packages have conflicting dependencies, <code class="docutils literal
notranslate"><span class="pre">pip</span></code> might decide to downgrade or
upgrade
+apache-airflow for you, so adding it explicitly is a good practice - this way
if you have conflicting
+requirements, you will get an error message with conflict information, rather
than a surprise
+downgrade or upgrade of airflow. If you upgrade airflow base image, you should
also update the version
+to match the new version of airflow.</p>
+</div>
<div class="example-block-wrapper compound">
<p class="example-header compound-first"><span
class="example-title">docs/docker-stack/docker-examples/extending/add-pypi-packages/Dockerfile</span></p>
<div class="compound-last highlight-Dockerfile notranslate"><div
class="highlight"><pre><span></span><span class="k">FROM</span><span class="w">
</span><span class="s">apache/airflow:2.6.1</span>
-<span class="k">RUN</span><span class="w"> </span>pip<span class="w">
</span>install<span class="w"> </span>--no-cache-dir<span class="w"> </span>lxml
+<span class="k">RUN</span><span class="w"> </span>pip<span class="w">
</span>install<span class="w"> </span>--no-cache-dir<span class="w">
</span><span class="s2">"apache-airflow==</span><span
class="si">${</span><span class="nv">AIRFLOW_VERSION</span><span
class="si">}</span><span class="s2">"</span><span class="w"> </span>lxml
</pre></div>
</div>
</div>
@@ -687,11 +699,30 @@ as <code class="docutils literal notranslate"><span
class="pre">root</span></cod
<p>The following example adds few python packages from <code class="docutils
literal notranslate"><span class="pre">requirements.txt</span></code> from PyPI
to the image.
Note that similarly when adding individual packages, you need to use the <code
class="docutils literal notranslate"><span class="pre">airflow</span></code>
user rather than
<code class="docutils literal notranslate"><span
class="pre">root</span></code>. Attempts to install <code class="docutils
literal notranslate"><span class="pre">pip</span></code> packages as <code
class="docutils literal notranslate"><span class="pre">root</span></code> will
fail with an appropriate error message.</p>
+<div class="admonition note">
+<p class="admonition-title">Note</p>
+<p>In the example below, we also add apache-airflow package to be installed -
in the very same version
+that the image version you used it from. This is not strictly necessary, but
it is a good practice
+to always install the same version of apache-airflow as the one you are using.
This way you can
+be sure that the version you are using is the same as the one you are
extending. In some cases where
+your new packages have conflicting dependencies, <code class="docutils literal
notranslate"><span class="pre">pip</span></code> might decide to downgrade or
upgrade
+apache-airflow for you, so adding it explicitly is a good practice - this way
if you have conflicting
+requirements, you will get an error message with conflict information, rather
than a surprise
+downgrade or upgrade of airflow. If you upgrade airflow base image, you should
also update the version
+to match the new version of airflow.</p>
+</div>
<div class="example-block-wrapper compound">
<p class="example-header compound-first"><span
class="example-title">docs/docker-stack/docker-examples/extending/add-requirement-packages/Dockerfile</span></p>
<div class="compound-last highlight-Dockerfile notranslate"><div
class="highlight"><pre><span></span><span class="k">FROM</span><span class="w">
</span><span class="s">apache/airflow:2.6.1</span>
<span class="k">COPY</span><span class="w"> </span>requirements.txt<span
class="w"> </span>/
-<span class="k">RUN</span><span class="w"> </span>pip<span class="w">
</span>install<span class="w"> </span>--no-cache-dir<span class="w">
</span>-r<span class="w"> </span>/requirements.txt
+<span class="k">RUN</span><span class="w"> </span>pip<span class="w">
</span>install<span class="w"> </span>--no-cache-dir<span class="w">
</span><span class="s2">"apache-airflow==</span><span
class="si">${</span><span class="nv">AIRFLOW_VERSION</span><span
class="si">}</span><span class="s2">"</span><span class="w">
</span>-r<span class="w"> </span>/requirements.txt
+</pre></div>
+</div>
+</div>
+<div class="example-block-wrapper compound">
+<p class="example-header compound-first"><span
class="example-title">docs/docker-stack/docker-examples/extending/add-requirement-packages/requirements.txt</span></p>
+<div class="compound-last highlight-text notranslate"><div
class="highlight"><pre><span></span>lxml
+beautifulsoup4
</pre></div>
</div>
</div>
@@ -935,22 +966,25 @@ require different limits for the same dependencies.</p>
</tr>
</thead>
<tbody>
-<tr class="row-even"><td><p>Latest default
-Default
-Latest
-Specific</p></td>
-<td><p>3.7
-3.7
-3.7,3.8,3.9,3.10
-3.7,3.8,3.9,3.10</p></td>
-<td><p>apache/airflow:latest
-apache/airflow:X.Y.Z
-apache/airflow:latest-pythonN.M
-apache/airflow:X.Y.Z-pythonN.M</p></td>
-<td><p>apache/airflow:slim-latest
-apache/airflow:slim-X.Y.Z
-apache/airflow:slim-latest-pythonN.M
-apache/airflow:slim-X.Y.Z-pythonN.M</p></td>
+<tr class="row-even"><td><p>Latest default</p></td>
+<td><p>3.7</p></td>
+<td><p>apache/airflow:latest</p></td>
+<td><p>apache/airflow:slim-latest</p></td>
+</tr>
+<tr class="row-odd"><td><p>Default</p></td>
+<td><p>3.7</p></td>
+<td><p>apache/airflow:X.Y.Z</p></td>
+<td><p>apache/airflow:slim-X.Y.Z</p></td>
+</tr>
+<tr class="row-even"><td><p>Latest</p></td>
+<td><p>3.7,3.8,3.9,3.10</p></td>
+<td><p>apache/airflow:latest-pythonN.M</p></td>
+<td><p>apache/airflow:slim-latest-pythonN.M</p></td>
+</tr>
+<tr class="row-odd"><td><p>Specific</p></td>
+<td><p>3.7,3.8,3.9,3.10</p></td>
+<td><p>apache/airflow:X.Y.Z-pythonN.M</p></td>
+<td><p>apache/airflow:slim-X.Y.Z-pythonN.M</p></td>
</tr>
</tbody>
</table>
@@ -1023,7 +1057,7 @@ use features available in that provider version. Here is
an example of how you c
<div class="example-block-wrapper compound">
<p class="example-header compound-first"><span
class="example-title">docs/docker-stack/docker-examples/extending/custom-providers/Dockerfile</span></p>
<div class="compound-last highlight-Dockerfile notranslate"><div
class="highlight"><pre><span></span><span class="k">FROM</span><span class="w">
</span><span class="s">apache/airflow:2.6.1</span>
-<span class="k">RUN</span><span class="w"> </span>pip<span class="w">
</span>install<span class="w"> </span>--no-cache-dir<span class="w">
</span>apache-airflow-providers-docker<span class="o">==</span><span
class="m">2</span>.5.1
+<span class="k">RUN</span><span class="w"> </span>pip<span class="w">
</span>install<span class="w"> </span><span
class="s2">"apache-airflow==</span><span class="si">${</span><span
class="nv">AIRFLOW_VERSION</span><span class="si">}</span><span
class="s2">"</span><span class="w"> </span>--no-cache-dir<span class="w">
</span>apache-airflow-providers-docker<span class="o">==</span><span
class="m">2</span>.5.1
</pre></div>
</div>
</div>
@@ -1044,7 +1078,7 @@ python package from PyPI.</p>
<span class="w"> </span><span class="o">&&</span><span class="w">
</span>rm<span class="w"> </span>-rf<span class="w"> </span>/var/lib/apt/lists/*
<span class="k">USER</span><span class="w"> </span><span
class="s">airflow</span>
<span class="k">ENV</span><span class="w"> </span><span
class="nv">JAVA_HOME</span><span
class="o">=</span>/usr/lib/jvm/java-11-openjdk-amd64
-<span class="k">RUN</span><span class="w"> </span>pip<span class="w">
</span>install<span class="w"> </span>--no-cache-dir<span class="w">
</span>apache-airflow-providers-apache-spark<span class="o">==</span><span
class="m">2</span>.1.3
+<span class="k">RUN</span><span class="w"> </span>pip<span class="w">
</span>install<span class="w"> </span>--no-cache-dir<span class="w">
</span><span class="s2">"apache-airflow==</span><span
class="si">${</span><span class="nv">AIRFLOW_VERSION</span><span
class="si">}</span><span class="s2">"</span><span class="w">
</span>apache-airflow-providers-apache-spark<span class="o">==</span><span
class="m">2</span>.1.3
</pre></div>
</div>
</div>
@@ -1073,7 +1107,7 @@ python package from PyPI.</p>
<div class="example-block-wrapper compound">
<p class="example-header compound-first"><span
class="example-title">docs/docker-stack/docker-examples/extending/add-pypi-packages/Dockerfile</span></p>
<div class="compound-last highlight-Dockerfile notranslate"><div
class="highlight"><pre><span></span><span class="k">FROM</span><span class="w">
</span><span class="s">apache/airflow:2.6.1</span>
-<span class="k">RUN</span><span class="w"> </span>pip<span class="w">
</span>install<span class="w"> </span>--no-cache-dir<span class="w"> </span>lxml
+<span class="k">RUN</span><span class="w"> </span>pip<span class="w">
</span>install<span class="w"> </span>--no-cache-dir<span class="w">
</span><span class="s2">"apache-airflow==</span><span
class="si">${</span><span class="nv">AIRFLOW_VERSION</span><span
class="si">}</span><span class="s2">"</span><span class="w"> </span>lxml
</pre></div>
</div>
</div>
@@ -1083,11 +1117,30 @@ python package from PyPI.</p>
<p>The following example adds few python packages from <code class="docutils
literal notranslate"><span class="pre">requirements.txt</span></code> from PyPI
to the image.
Note that similarly when adding individual packages, you need to use the <code
class="docutils literal notranslate"><span class="pre">airflow</span></code>
user rather than
<code class="docutils literal notranslate"><span
class="pre">root</span></code>. Attempts to install <code class="docutils
literal notranslate"><span class="pre">pip</span></code> packages as <code
class="docutils literal notranslate"><span class="pre">root</span></code> will
fail with an appropriate error message.</p>
+<div class="admonition note">
+<p class="admonition-title">Note</p>
+<p>In the example below, we also add apache-airflow package to be installed -
in the very same version
+that the image version you used it from. This is not strictly necessary, but
it is a good practice
+to always install the same version of apache-airflow as the one you are using.
This way you can
+be sure that the version you are using is the same as the one you are
extending. In some cases where
+your new packages have conflicting dependencies, <code class="docutils literal
notranslate"><span class="pre">pip</span></code> might decide to downgrade or
upgrade
+apache-airflow for you, so adding it explicitly is a good practice - this way
if you have conflicting
+requirements, you will get an error message with conflict information, rather
than a surprise
+downgrade or upgrade of airflow. If you upgrade airflow base image, you should
also update the version
+to match the new version of airflow.</p>
+</div>
<div class="example-block-wrapper compound">
<p class="example-header compound-first"><span
class="example-title">docs/docker-stack/docker-examples/extending/add-requirement-packages/Dockerfile</span></p>
<div class="compound-last highlight-Dockerfile notranslate"><div
class="highlight"><pre><span></span><span class="k">FROM</span><span class="w">
</span><span class="s">apache/airflow:2.6.1</span>
<span class="k">COPY</span><span class="w"> </span>requirements.txt<span
class="w"> </span>/
-<span class="k">RUN</span><span class="w"> </span>pip<span class="w">
</span>install<span class="w"> </span>--no-cache-dir<span class="w">
</span>-r<span class="w"> </span>/requirements.txt
+<span class="k">RUN</span><span class="w"> </span>pip<span class="w">
</span>install<span class="w"> </span>--no-cache-dir<span class="w">
</span><span class="s2">"apache-airflow==</span><span
class="si">${</span><span class="nv">AIRFLOW_VERSION</span><span
class="si">}</span><span class="s2">"</span><span class="w">
</span>-r<span class="w"> </span>/requirements.txt
+</pre></div>
+</div>
+</div>
+<div class="example-block-wrapper compound">
+<p class="example-header compound-first"><span
class="example-title">docs/docker-stack/docker-examples/extending/add-requirement-packages/requirements.txt</span></p>
+<div class="compound-last highlight-text notranslate"><div
class="highlight"><pre><span></span>lxml
+beautifulsoup4
</pre></div>
</div>
</div>
@@ -1119,7 +1172,7 @@ running the container.</p>
<span class="w"> </span><span class="o">&&</span><span class="w">
</span>apt-get<span class="w"> </span>clean<span class="w"> </span><span
class="se">\</span>
<span class="w"> </span><span class="o">&&</span><span class="w">
</span>rm<span class="w"> </span>-rf<span class="w"> </span>/var/lib/apt/lists/*
<span class="k">USER</span><span class="w"> </span><span
class="s">airflow</span>
-<span class="k">RUN</span><span class="w"> </span>pip<span class="w">
</span>install<span class="w"> </span>--no-cache-dir<span class="w">
</span>mpi4py
+<span class="k">RUN</span><span class="w"> </span>pip<span class="w">
</span>install<span class="w"> </span>--no-cache-dir<span class="w">
</span><span class="s2">"apache-airflow==</span><span
class="si">${</span><span class="nv">AIRFLOW_VERSION</span><span
class="si">}</span><span class="s2">"</span><span class="w"> </span>mpi4py
</pre></div>
</div>
</div>
@@ -1281,12 +1334,25 @@ during the build.</p>
<li><p>you can place <code class="docutils literal notranslate"><span
class="pre">requirements.txt</span></code> and add any <code class="docutils
literal notranslate"><span class="pre">pip</span></code> packages you want to
install in the
<code class="docutils literal notranslate"><span
class="pre">docker-context-file</span></code> folder. Those requirements will
be automatically installed during the build.</p></li>
</ul>
+<div class="admonition note">
+<p class="admonition-title">Note</p>
+<p>In the example below, we also add apache-airflow package to be installed -
in the very same version
+that the image version you used it from. This is not strictly necessary, but
it is a good practice
+to always install the same version of apache-airflow as the one you are using.
This way you can
+be sure that the version you are using is the same as the one you are
extending. In some cases where
+your new packages have conflicting dependencies, <code class="docutils literal
notranslate"><span class="pre">pip</span></code> might decide to downgrade or
upgrade
+apache-airflow for you, so adding it explicitly is a good practice - this way
if you have conflicting
+requirements, you will get an error message with conflict information, rather
than a surprise
+downgrade or upgrade of airflow. If you upgrade airflow base image, you should
also update the version
+to match the new version of airflow.</p>
+</div>
<div class="example-block-wrapper compound">
<p class="example-header compound-first"><span
class="example-title">docs/docker-stack/docker-examples/customizing/own-requirements.sh</span></p>
<div class="compound-last highlight-bash notranslate"><div
class="highlight"><pre><span></span>mkdir<span class="w"> </span>-p<span
class="w"> </span>docker-context-files
cat<span class="w"> </span><span class="s"><<EOF
>./docker-context-files/requirements.txt</span>
<span class="s">beautifulsoup4==4.10.0</span>
+<span class="s">apache-airflow==2.6.0.dev0</span>
<span class="s">EOF</span>
<span class="nb">export</span><span class="w"> </span><span
class="nv">DOCKER_BUILDKIT</span><span class="o">=</span><span
class="m">1</span>
diff --git a/docs/docker-stack/recipes.html b/docs/docker-stack/recipes.html
index e55b3d1f2b..85c3c79d6f 100644
--- a/docs/docker-stack/recipes.html
+++ b/docs/docker-stack/recipes.html
@@ -565,8 +565,8 @@ recipes to the documentation in case they prove useful to
other members of the c
submitting a pull request. The sections below capture this knowledge.</p>
<div class="section" id="google-cloud-sdk-installation">
<h2>Google Cloud SDK installation<a class="headerlink"
href="#google-cloud-sdk-installation" title="Permalink to this
heading">¶</a></h2>
-<p>Some operators, such as <a class="reference external"
href="/docs/apache-airflow-providers-google/stable/_api/airflow/providers/google/cloud/operators/kubernetes_engine/index.html#airflow.providers.google.cloud.operators.kubernetes_engine.GKEStartPodOperator"
title="(in apache-airflow-providers-google v10.0.0)"><code class="xref py
py-class docutils literal notranslate"><span
class="pre">GKEStartPodOperator</span></code></a>,
-<a class="reference external"
href="/docs/apache-airflow-providers-google/stable/_api/airflow/providers/google/cloud/operators/dataflow/index.html#airflow.providers.google.cloud.operators.dataflow.DataflowStartSqlJobOperator"
title="(in apache-airflow-providers-google v10.0.0)"><code class="xref py
py-class docutils literal notranslate"><span
class="pre">DataflowStartSqlJobOperator</span></code></a>, require
+<p>Some operators, such as <a class="reference external"
href="/docs/apache-airflow-providers-google/stable/_api/airflow/providers/google/cloud/operators/kubernetes_engine/index.html#airflow.providers.google.cloud.operators.kubernetes_engine.GKEStartPodOperator"
title="(in apache-airflow-providers-google v10.1.0)"><code class="xref py
py-class docutils literal notranslate"><span
class="pre">GKEStartPodOperator</span></code></a>,
+<a class="reference external"
href="/docs/apache-airflow-providers-google/stable/_api/airflow/providers/google/cloud/operators/dataflow/index.html#airflow.providers.google.cloud.operators.dataflow.DataflowStartSqlJobOperator"
title="(in apache-airflow-providers-google v10.1.0)"><code class="xref py
py-class docutils literal notranslate"><span
class="pre">DataflowStartSqlJobOperator</span></code></a>, require
the installation of <a class="reference external"
href="https://cloud.google.com/sdk";>Google Cloud SDK</a> (includes <code
class="docutils literal notranslate"><span class="pre">gcloud</span></code>).
You can also run these commands with BashOperator.</p>
<p>Create a new Dockerfile like the one shown below.</p>
@@ -739,7 +739,7 @@ Below are the steps to take tools that are frequently used
in Hadoop-world:</p>
</div>
<div class="section" id="apache-beam-go-stack-installation">
<h2>Apache Beam Go Stack installation<a class="headerlink"
href="#apache-beam-go-stack-installation" title="Permalink to this
heading">¶</a></h2>
-<p>To be able to run Beam Go Pipeline with the <a class="reference external"
href="/docs/apache-airflow-providers-apache-beam/stable/_api/airflow/providers/apache/beam/operators/beam/index.html#airflow.providers.apache.beam.operators.beam.BeamRunGoPipelineOperator"
title="(in apache-airflow-providers-apache-beam v5.0.0)"><code class="xref py
py-class docutils literal notranslate"><span
class="pre">BeamRunGoPipelineOperator</span></code></a>,
+<p>To be able to run Beam Go Pipeline with the <a class="reference external"
href="/docs/apache-airflow-providers-apache-beam/stable/_api/airflow/providers/apache/beam/operators/beam/index.html#airflow.providers.apache.beam.operators.beam.BeamRunGoPipelineOperator"
title="(in apache-airflow-providers-apache-beam v5.1.0)"><code class="xref py
py-class docutils literal notranslate"><span
class="pre">BeamRunGoPipelineOperator</span></code></a>,
you will need Go in your container. Install airflow with <code class="docutils
literal notranslate"><span
class="pre">apache-airflow-providers-google>=6.5.0</span></code> and <code
class="docutils literal notranslate"><span
class="pre">apache-airflow-providers-apache-beam>=3.2.0</span></code></p>
<p>Create a new Dockerfile like the one shown below.</p>
<div class="example-block-wrapper compound">
diff --git a/docs/docker-stack/searchindex.js b/docs/docker-stack/searchindex.js
index 054d02f3a4..2059b1dabe 100644
--- a/docs/docker-stack/searchindex.js
+++ b/docs/docker-stack/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["build", "build-arg-ref", "changelog",
"entrypoint", "index", "recipes"], "filenames": ["build.rst",
"build-arg-ref.rst", "changelog.rst", "entrypoint.rst", "index.rst",
"recipes.rst"], "titles": ["Building the image", "Image build arguments
reference", "Dockerfile Changelog", "Entrypoint", "Docker Image for Apache
Airflow", "Recipes"], "terms": {"befor": [0, 1, 2], "dive": 0, "deepli": 0,
"wai": [0, 1, 2, 3, 4, 5], "how": [0, 2, 3, 4], "built": [0, 1, 2], " [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["build", "build-arg-ref", "changelog",
"entrypoint", "index", "recipes"], "filenames": ["build.rst",
"build-arg-ref.rst", "changelog.rst", "entrypoint.rst", "index.rst",
"recipes.rst"], "titles": ["Building the image", "Image build arguments
reference", "Dockerfile Changelog", "Entrypoint", "Docker Image for Apache
Airflow", "Recipes"], "terms": {"befor": [0, 1, 2], "dive": 0, "deepli": 0,
"wai": [0, 1, 2, 3, 4, 5], "how": [0, 2, 3, 4], "built": [0, 1, 2], " [...]
\ No newline at end of file
diff --git a/index.html b/index.html
index 218d569ce4..7c9112f9b1 100644
--- a/index.html
+++ b/index.html
@@ -1193,12 +1193,12 @@
<div id="integrations-container" class="list-items">
- <a class="list-item"
href="/docs/apache-airflow-providers-google/stable/operators/marketing_platform/search_ads.html">
+ <a class="list-item"
href="/docs/apache-airflow-providers-microsoft-azure/stable/index.html">
<div class="card">
<div class="box-event box-event__integration">
- <span class="box-event__integration--name">Google Search Ads 360</span>
+ <span class="box-event__integration--name">Microsoft Azure Container
Instances</span>
</div>
</div>
@@ -1206,12 +1206,12 @@
- <a class="list-item"
href="/docs/apache-airflow-providers-amazon/stable/operators/dms.html">
+ <a class="list-item"
href="/docs/apache-airflow-providers-neo4j/stable/operators/neo4j.html">
<div class="card">
<div class="box-event box-event__integration">
- <span class="box-event__integration--name">AWS Database Migration
Service</span>
+ <span class="box-event__integration--name">Neo4j</span>
</div>
</div>
@@ -1219,12 +1219,12 @@
- <a class="list-item"
href="/docs/apache-airflow-providers-telegram/stable/operators.html">
+ <a class="list-item"
href="/docs/apache-airflow-providers-amazon/stable/operators/lambda.html">
<div class="card">
<div class="box-event box-event__integration">
- <span class="box-event__integration--name">Telegram</span>
+ <span class="box-event__integration--name">AWS Lambda</span>
</div>
</div>
@@ -1232,12 +1232,12 @@
- <a class="list-item"
href="/docs/apache-airflow-providers-google/stable/operators/firebase/firestore.html">
+ <a class="list-item"
href="/docs/apache-airflow-providers-amazon/stable/operators/sqs.html">
<div class="card">
<div class="box-event box-event__integration">
- <span class="box-event__integration--name">Google Cloud
Firestore</span>
+ <span class="box-event__integration--name">Amazon Simple Queue Service
(SQS)</span>
</div>
</div>
@@ -1245,12 +1245,12 @@
- <a class="list-item"
href="/docs/apache-airflow-providers-vertica/stable/index.html">
+ <a class="list-item"
href="/docs/apache-airflow-providers-apache-hdfs/stable/operators/webhdfs.html">
<div class="card">
<div class="box-event box-event__integration">
- <span class="box-event__integration--name">Vertica</span>
+ <span class="box-event__integration--name">WebHDFS</span>
</div>
</div>
@@ -1258,12 +1258,12 @@
- <a class="list-item"
href="/docs/apache-airflow-providers-mysql/stable/operators.html">
+ <a class="list-item"
href="/docs/apache-airflow-providers-docker/stable/index.html">
<div class="card">
<div class="box-event box-event__integration">
- <span class="box-event__integration--name">MySQL</span>
+ <span class="box-event__integration--name">Docker</span>
</div>
</div>
@@ -1271,12 +1271,12 @@
- <a class="list-item"
href="/docs/apache-airflow-providers-google/stable/index.html">
+ <a class="list-item"
href="/docs/apache-airflow-providers-amazon/stable/operators/sagemaker.html">
<div class="card">
<div class="box-event box-event__integration">
- <span class="box-event__integration--name">Google Cloud Secret
Manager</span>
+ <span class="box-event__integration--name">Amazon SageMaker</span>
</div>
</div>
@@ -1284,12 +1284,12 @@
- <a class="list-item"
href="/docs/apache-airflow-providers-amazon/stable/index.html">
+ <a class="list-item"
href="/docs/apache-airflow-providers-google/stable/operators/cloud/spanner.html">
<div class="card">
<div class="box-event box-event__integration">
- <span class="box-event__integration--name">Amazon Web Services</span>
+ <span class="box-event__integration--name">Google Cloud Spanner</span>
</div>
</div>
diff --git a/search/index.html b/search/index.html
index e0a3f5e46b..d50ab897c2 100644
--- a/search/index.html
+++ b/search/index.html
@@ -34,11 +34,11 @@
<meta property="og:type" content="article" />
<meta property="og:url" content="/search/" /><meta property="og:image"
content="/images/feature-image.png"/><meta property="article:section"
content="" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Search Results">
<meta itemprop="description" content="">
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="0"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="" /><meta name="twitter:card"
content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/sitemap.xml b/sitemap.xml
index 4e4c700039..973c47f0bc 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -3,158 +3,158 @@
xmlns:xhtml="http://www.w3.org/1999/xhtml";>
<url>
<loc>/docs/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/tags/release/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/tags/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/airflow-2.6.0/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/airflow-2.5.0/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/airflow-2.4.0/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/airflow-survey-2022/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/tags/community/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/tags/survey/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/tags/users/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/tags/airflow-summit/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/airflow_summit_2022/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/airflow-2.3.0/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/airflow-2.2.0/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/airflow_summit_2021/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/airflow-survey-2020/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/airflow-two-point-oh-is-here/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/experience-with-airflow-as-an-outreachy-intern/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/airflow-1.10.12/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/apache-airflow-for-newcomers/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/announcements/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/implementing-stable-api-for-apache-airflow/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/tags/rest-api/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/airflow-1.10.10/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/airflow-1.10.8-1.10.9/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/tags/documentation/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/experience-in-google-season-of-docs-2019-with-apache-airflow/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/airflow-survey/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/announcing-new-website/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/apache-con-europe-2019-thoughts-and-insights-by-airflow-committers/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/tags/development/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/documenting-using-local-development-environments/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/its-a-breeze-to-develop-apache-airflow/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/use-cases/adobe/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/use-cases/adyen/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/use-cases/big-fish-games/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/blog/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/categories/</loc>
</url><url>
<loc>/community/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/use-cases/dish/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/ecosystem/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/use-cases/experity/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/meetups/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/use-cases/onefootball/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/use-cases/plarium-krasnodar/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/privacy-notice/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/roadmap/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/search/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/use-cases/seniorlink/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/use-cases/sift/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url><url>
<loc>/use-cases/</loc>
- <lastmod>2023-05-22T22:31:13+03:00</lastmod>
+ <lastmod>2023-05-23T12:58:51+02:00</lastmod>
</url>
</urlset>
diff --git a/use-cases/adobe/index.html b/use-cases/adobe/index.html
index ac643da7ec..00436b4660 100644
--- a/use-cases/adobe/index.html
+++ b/use-cases/adobe/index.html
@@ -34,11 +34,11 @@
<meta property="og:type" content="article" />
<meta property="og:url" content="/use-cases/adobe/" /><meta
property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="use-cases" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Adobe">
<meta itemprop="description" content="What was the problem? Modern big data
platforms need sophisticated data pipelines connecting to many backend services
enabling complex workflows. These workflows need to be deployed, monitored, and
run either on regular schedules or triggered by external events. Adobe
Experience Platform component services architected and built an orchestration
service to enable their users to author, schedule, and monitor complex
hierarchical (including sequential a [...]
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="251"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="" /><meta name="twitter:card"
content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/use-cases/adyen/index.html b/use-cases/adyen/index.html
index cbbf242e24..72a2028d8d 100644
--- a/use-cases/adyen/index.html
+++ b/use-cases/adyen/index.html
@@ -34,11 +34,11 @@
<meta property="og:type" content="article" />
<meta property="og:url" content="/use-cases/adyen/" /><meta
property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="use-cases" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Adyen">
<meta itemprop="description" content="What was the problem? Many years ago we
started out with our own orchestration framework. Due to all the required
custom functionality it made sense at the time. However, quickly we realized
creating an orchestration tool is not to be underestimated. With the quickly
increasing number of users and teams, time spent on fixing issues increased,
severely limiting development speed. Furthermore, due to it not being open
source, we constantly had to make [...]
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="405"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="" /><meta name="twitter:card"
content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/use-cases/big-fish-games/index.html
b/use-cases/big-fish-games/index.html
index 0e23f9a350..cec3045c8f 100644
--- a/use-cases/big-fish-games/index.html
+++ b/use-cases/big-fish-games/index.html
@@ -34,11 +34,11 @@
<meta property="og:type" content="article" />
<meta property="og:url" content="/use-cases/big-fish-games/" /><meta
property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="use-cases" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Big Fish Games">
<meta itemprop="description" content="What was the problem? The main challenge
is the lack of standardized ETL workflow orchestration tools. PowerShell and
Python-based ETL frameworks built in-house are currently used for scheduling
and running analytical workloads. However, there is no web UI through which we
can monitor these workflows and it requires additional effort to maintain this
framework. These scheduled jobs based on external dependencies are not well
suited to modern Big Data [...]
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="336"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="" /><meta name="twitter:card"
content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/use-cases/dish/index.html b/use-cases/dish/index.html
index 7ae0de76bf..e977886e0d 100644
--- a/use-cases/dish/index.html
+++ b/use-cases/dish/index.html
@@ -34,11 +34,11 @@
<meta property="og:type" content="article" />
<meta property="og:url" content="/use-cases/dish/" /><meta property="og:image"
content="/images/feature-image.png"/><meta property="article:section"
content="use-cases" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Dish">
<meta itemprop="description" content="What was the problem? We faced
increasing complexity managing lengthy crontabs with scheduling being an issue,
this required carefully planning timing due to resource constraints, usage
patterns, and especially custom code needed for retry logic. In the last case,
having to verify success of previous jobs and/or steps prior to running the
next. Furthermore, time to results is important, but we were increasingly
relying on buffers for processing, wher [...]
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="248"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="" /><meta name="twitter:card"
content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/use-cases/experity/index.html b/use-cases/experity/index.html
index 73916c1196..3293faa899 100644
--- a/use-cases/experity/index.html
+++ b/use-cases/experity/index.html
@@ -35,12 +35,12 @@ How did Apache Airflow help to solve this problem?
Ultimately we decided flexibl
<meta property="og:type" content="article" />
<meta property="og:url" content="/use-cases/experity/" /><meta
property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="use-cases" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Experity">
<meta itemprop="description" content="What was the problem? We had to deploy
our complex, flagship app to multiple nodes in multiple ways. This required
tasks to communicate across Windows nodes and coordinate timing perfectly. We
did not want to buy an expensive enterprise scheduling tool and needed ultimate
flexibility.
How did Apache Airflow help to solve this problem? Ultimately we decided
flexible, multi-node, DAG capable tooling was key and airflow was one of the
few tools that fit that bill.">
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="191"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="" /><meta name="twitter:card"
content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/use-cases/onefootball/index.html b/use-cases/onefootball/index.html
index 1562176478..099ee5d6ee 100644
--- a/use-cases/onefootball/index.html
+++ b/use-cases/onefootball/index.html
@@ -35,12 +35,12 @@ On top of that, new data tools appear each month: third
party data sources, clou
<meta property="og:type" content="article" />
<meta property="og:url" content="/use-cases/onefootball/" /><meta
property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="use-cases" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Onefootball">
<meta itemprop="description" content="What was the problem? With millions of
daily active users, managing the complexity of data engineering at Onefootball
is a constant challenge. Lengthy crontabs, multiplication of custom API
clients, erosion of confidence in the analytics served, increasing heroism
(“only one person can solve this issue”). Those are the challenges
that most teams face unless they consciously invest in their tools and
processes.
On top of that, new data tools appear each month: third party data sources,
cloud providers solutions, different storage technologies… Managing all
those integrations is costly and brittle, especially for small data engineering
teams that are trying to do more with less.">
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="294"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="" /><meta name="twitter:card"
content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/use-cases/plarium-krasnodar/index.html
b/use-cases/plarium-krasnodar/index.html
index dc10e7a64a..ebcf36166d 100644
--- a/use-cases/plarium-krasnodar/index.html
+++ b/use-cases/plarium-krasnodar/index.html
@@ -34,11 +34,11 @@
<meta property="og:type" content="article" />
<meta property="og:url" content="/use-cases/plarium-krasnodar/" /><meta
property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="use-cases" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Plarium Krasnodar">
<meta itemprop="description" content="What was the problem? Our Research &
Development department carries out various experiments, and in all of them, we
need to create workflow orchestrations for solving tasks in game dev.
Previously, we didn’t have any suitable tools with a sufficient number of
built-in functions, and we had to orchestrate processes manually and entirely
from scratch every time. This led to difficulties with dependencies and
monitoring when building complex w [...]
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="257"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="" /><meta name="twitter:card"
content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/use-cases/seniorlink/index.html b/use-cases/seniorlink/index.html
index 456fa69e2f..855cc211d1 100644
--- a/use-cases/seniorlink/index.html
+++ b/use-cases/seniorlink/index.html
@@ -35,12 +35,12 @@ We had built a robust stack of batch processes to deliver
value to the business,
<meta property="og:type" content="article" />
<meta property="og:url" content="/use-cases/seniorlink/" /><meta
property="og:image" content="/images/feature-image.png"/><meta
property="article:section" content="use-cases" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Seniorlink">
<meta itemprop="description" content="What was the problem? Here at
Seniorlink, we provide services, support, and technology that engages family
caregivers. One of our focuses is using data to bolster our knowledge and
improve the experience of our users. Like many looking to build an effective
data stack, we adopted a Python, Spark, Redshift, and Tableau core toolset.
We had built a robust stack of batch processes to deliver value to the
business, deploying these data services in AWS using a mixture of EMR, ECS,
Lambda, and EC2.">
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="400"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="" /><meta name="twitter:card"
content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
diff --git a/use-cases/sift/index.html b/use-cases/sift/index.html
index 405d695d8b..6a19c2337d 100644
--- a/use-cases/sift/index.html
+++ b/use-cases/sift/index.html
@@ -34,11 +34,11 @@
<meta property="og:type" content="article" />
<meta property="og:url" content="/use-cases/sift/" /><meta property="og:image"
content="/images/feature-image.png"/><meta property="article:section"
content="use-cases" />
-<meta property="article:modified_time" content="2023-05-22T22:31:13+03:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2023-05-23T12:58:51+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Sift">
<meta itemprop="description" content="What was the problem? At Sift, we’re
constantly training machine learning models that feed into the core of Sift’s
Digital Trust & Safety platform. The platform gives our customers a way to
discern suspicious online behavior from trustworthy behavior, allowing our
customers to protect their online transactions, maintain the integrity of their
content platforms, and keep their users’ accounts secure. To make this
possible, we’ve built model traini [...]
-<meta itemprop="dateModified" content="2023-05-22T22:31:13+03:00" />
+<meta itemprop="dateModified" content="2023-05-23T12:58:51+02:00" />
<meta itemprop="wordCount" content="641"><meta itemprop="image"
content="/images/feature-image.png"/>
<meta itemprop="keywords" content="" /><meta name="twitter:card"
content="summary_large_image"/>
<meta name="twitter:image" content="/images/feature-image.png"/>
