Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

allow persistent directory for tar1090-update #174

Merged
merged 1 commit into from
Apr 13, 2024

Conversation

wiedehopf
Copy link
Contributor

when recreating the container via docker compose, changes in the docker image are lost. this means tar1090-update needs to download data again. especially when changes to container are made via automation, this can happen relatively often and it's desirable that the data are not required to be downloaded more than once

change the directory for the tar1090 and tar1090-db git dirs and the aircraft.csv.gz file to TAR1090_UPDATE_DIR=/var/globe_history/tar1090-update

this directory is already mounted on most installs and redownloads are avoided

the Dockerfile places aircraft.csv.gz in TAR1090_INSTALL_DIR so it can be used in the unlikely event of /var/globe_history being mounted while UPDATE_TAR1090 is false

when recreating the container via docker compose, changes in the docker
image are lost. this means tar1090-update needs to download data again.
especially when changes to container are made via automation, this can
happen relatively often and it's desirable that the data are not
required to be downloaded more than once

change the directory for the tar1090 and tar1090-db git dirs and the
aircraft.csv.gz file to TAR1090_UPDATE_DIR=/var/globe_history/tar1090-update

this directory is already mounted on most installs and redownloads are avoided

the Dockerfile places aircraft.csv.gz in TAR1090_INSTALL_DIR so it can be
used in the unlikely event of /var/globe_history being mounted while
UPDATE_TAR1090 is false
@fredclausen fredclausen merged commit b17b020 into sdr-enthusiasts:main Apr 13, 2024
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants