potiuk commented on issue #21105:
URL: https://github.com/apache/airflow/issues/21105#issuecomment-1096516005
Good point. By "Installed" I mean "checked out" really :)
The - unfortunate - problem with new contributors of irflow is that they
often don't have often "separate folder for code" and check out the code in
"$HOME" directly. And since default name of the repo is "airflow" this ends up
with airflow source code in "${HOME}/airflow" more often than not,
That's unfortunate and something we can't change without breaking
compatibility - airflow's default "HOME_DIR" when no AIRFLOW_HOME is not set is
.... "${HOME}/airflow" :scream: . And when you run airlfow it will do all kinds
of "writes" in this directory - logs, dags, sqlite database, airlfow
config/settings files are all create there (and which files get created depend
on some variables like UNIT_TEST_MODE :scream: :scream: :scream_cat: .
So really "${HOME}/airflow" might be both at the same time more often that
not - the source code checked out from git as well as "writable storage" for
running airflow.
This is not a HUGE problem for casual users (we already protect agains
accidential commits of files created in sources this way - via .gitignore - we
ignore a number of files tha airflow might write there when running. But if you
want to wipe that directory (which you might want to do to make sure there are
no databases, configuration , you better make sure you are not wiping out
checked out sources :).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
