nycplanning / docker-geosupport Goto Github PK

View Code? Open in Web Editor NEW

1.0 8.0 0.0 57 KB

Docker image for geosupport

Home Page: https://hub.docker.com/r/nycplanning/docker-geosupport/tags

Dockerfile 10.49% Shell 36.61% Python 52.90%

geosupport docker-image geocoding nyc nyc-opendata

docker-geosupport's Introduction

docker-geosupport

This repo is now archived. docker-geosupport image is produced in DCP Data Engineering's primary repo now

About:

This is a repository for dockerized geosupport linux desktop version. Thanks to python-geosupport python binding package for geosupport, we are able to localize our geocoding process.

Instructions:

Note that as of 2020/10/13, the nycplanning/docker-geosupport image will be automatically updated whenever there's a new major rlease or upad release on Bytes of the Big Apple. Manual updates are still available but discouraged, and will be gradually deprecated.

Build on your own machine

Make sure you have docker installed

RELEASE=20a
MAJOR=20
MINOR=1
PATCH=2
docker build --file Dockerfile \
        --build-arg RELEASE=$RELEASE \
        --build-arg MAJOR=$MAJOR \
        --build-arg MINOR=$MINOR \
        --build-arg PATCH=$PATCH \
        --tag nycplanning/docker-geosupport:$MAJOR.$MINOR.$PATCH .

make sure the submodule for python-geosupport is updated and available on your local

Pulling repo for the first time and pull files from submodule

git submodule update --init --recursive

Updating submodule

git submodule update --remote

Build through Issue (DEPRECATING ...)

Click on the issue icon and make a new issue.
follow the "build" issue template to open an issue.
make sure you specify the versioning info in the issue body.
When github actions finishes building the docker image and pushes the docker image to docker hub, it will automatically comment and close the issue that triggered the task.

Build through CI (DEPRECATING ...)

make sure you include version specifications in commit message
```
git commit -m 'RELEASE=20a MAJOR=20 MINOR=1 PATCH=0'
```

Note:

if there's no UPAD available, set PATCH=0.
You can find Geosupport desktop edition and UPAD related information on Bytes of the Big Apple

docker-geosupport's People

Contributors

Stargazers

Watchers

docker-geosupport's Issues

Automated check for new releases did not catch 20d

So far the automated workflow has only built a new geosupport docker container when triggered by a dispatch, not by the scheduled run.

For example, several days returned nycplanning/docker-geosupport:20.3.5 already exist well after the November 15 release of 20d.

[build] RELEASE=20a MAJOR=20 MINOR=1 PATCH=0

RELEASE=20a MAJOR=20 MINOR=1 PATCH=0

Get 22A9 of GeoSupport into Docker.

The GitHub Action stopped running automatically. The goal is to update docker-geosupport with Geosupport version 22A9, which is 22.1.9, with 9 being the version of UPAD. Unfortunately, the action fails when run manually. I think this is because the action is looking for version 22.1.2 ( by adding 1 to the current minor), but 22.1.2 is no longer available on Bytes. I think the way to fix this to get this going again to to set the minor to 9 temporally here, and run the action to get the latest version. Then remove the temporary hard coded value, and things should then work as expected with the automated runs.

I'd like someone else's input on this before making any changes.

getting a 401 "gone" error during build action
possible that the URL we use has been deprecated since first 23A UPAD release

build failing at UDAP step

example of build failing during patch.sh
last time the action passed
appears to fail at YES UPAD IS AVAILABLE linux_upad_tpad_22c1
may be urgent to generate a 22.3.4 image version for use in DevDB
- to use UPAD 22C4 release
- seems as though the last 22C image generated was 22.3.0 and didn't incorporate the UPAD

test

RELEASE=20a
MAJOR=20
MINOR=1
PATCH=2

[build]

RELEASE=20a MAJOR=20 MINOR=1 PATCH=2

[build] 20B update

RELEASE=20b MAJOR=20 MINOR=2 PATCH=0