Skip to content
This repository has been archived by the owner on Mar 6, 2019. It is now read-only.

Enable the Libpostal Service #42

Merged
merged 3 commits into from
Apr 16, 2018
Merged

Enable the Libpostal Service #42

merged 3 commits into from
Apr 16, 2018

Conversation

orangejulius
Copy link
Contributor

As mentioned in pelias/api#1060 and pelias/api#1072, we have started converting Libpostal to its own service, rather than loading it into memory in the API service. This PR adds support for that in the dockerfiles.

It's ready to go immediately, although for now it will have to use an API docker image built off of the master branch.

I'd like to merge this before we merge the API changes for the libpostal service to the production branch, to ensure there's a seamless transition. Then we should go back and update the docker-compose.yml file to point to the production Docker images.

@ghost ghost assigned orangejulius Feb 7, 2018
@ghost ghost added the in review label Feb 7, 2018
@orangejulius orangejulius force-pushed the libpostal-service branch 2 times, most recently from 11de864 to 9de04b0 Compare March 12, 2018 23:57
orangejulius added a commit that referenced this pull request Mar 19, 2018
The Pelias API has now been modified to expect libpostal to live as a
separate HTTP service rather than being included in memory.

This PR adds the libpostal service to `docker-compose.yml` but doesn't
change anything else. The current (as of 2018/3/19) `production` version
of Pelias API does not yet use the libpostal service. It's convenient to
have this merged so that we can start the process of switching over,
though.

Connects #42
orangejulius added a commit that referenced this pull request Mar 19, 2018
The Pelias API has now been modified to expect libpostal to live as a
separate HTTP service rather than being included in memory.

This PR adds the libpostal service to `docker-compose.yml` but doesn't
change anything else. The current (as of 2018/3/19) `production` version
of Pelias API does not yet use the libpostal service. It's convenient to
have this merged so that we can start the process of switching over,
though.

Connects #42
@missinglink
Copy link
Contributor

I got stung with this today, seems the libpostal service code was already merged to master

@missinglink
Copy link
Contributor

is it possible to change pelias/api:master to pelias/api and merge this @orangejulius?

@missinglink
Copy link
Contributor

missinglink commented Mar 22, 2018

if the docker image is still not at latest (because the code hasn't made it to the release branch yet, then I'm cool to merge this as-is, with the tag master)

approving, will let you decide what's best

The Pelias API has now been modified to expect libpostal to live as a
separate HTTP service rather than being included in memory.
orangejulius and others added 2 commits April 9, 2018 10:20
support for the libpostal service has not yet been merged to production,
so we need this for now. It should be removed once libpostal support is
stable
@orangejulius
Copy link
Contributor Author

Okay, this has been open for a while, it's time to merge

@orangejulius orangejulius merged commit 0b35c79 into master Apr 16, 2018
@orangejulius
Copy link
Contributor Author

We will be merging the libpostal-service change to pelias-api to production/latest soon!

This was referenced Apr 16, 2018
@orangejulius orangejulius deleted the libpostal-service branch April 23, 2018 15:16
orangejulius added a commit that referenced this pull request May 15, 2018
Now that pelias/api#1138 is merged, the Pelias API production images now use the Libpostal service, as described in pelias/api#1072. In #42 we said we would use the staging branch for the API in this repo until that merge happened. Now we can move back!
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants