Add tileserver to pypi

[pnorman]

Is it possible to add tileserver to pypi? I could take this on, but would much rather a maintainer does so.

[rmarianski]

Yes, we discussed this a little bit before but opted to wait until somebody asked for it, and here we are :)

It'll imply that all dependent packages are also on pypi, which from a cursory glance looks to be just tilequeue. The work there should mostly be just writing a readme to describe how that might be used.

Longer term it might make more sense to split up the code in tilequeue a little bit more. Right now I see it responsible for 2 things:

1. API for fetching data, processing, and formatting tiles, as well as some utility functions
2. Operational structure for how Mapzen processes tiles

Tileserver only needs to depend on the first part, and I'm assuming that the 2nd is more specific to Mapzen and less useful to others.

But for now, I think we should just publish our existing structure to pypi and possibly make another issue if we want to split up the repo. Any further thoughts @zerebubuth, @iandees, @nvkelso ?

[nvkelso]

Pub now, file an issue to split it up for a rainy day.

On Nov 10, 2016, at 07:22, Robert Marianski [email protected] wrote:

Yes, we discussed this a little bit before but opted to wait until somebody asked for it, and here we are :)

It'll imply that all dependent packages are also on pypi, which from a cursory glance looks to be just tilequeue. The work there should mostly be just writing a readme to describe how that might be used.

Longer term it might make more sense to split up the code in tilequeue a little bit more. Right now I see it responsible for 2 things:

1. API for fetching data, processing, and formatting tiles, as well as some utility functions
2. Operational structure for how Mapzen processes tiles

Tileserver only needs to depend on the first part, and I'm assuming that the 2nd is more specific to Mapzen and less useful to others.

But for now, I think we should just publish our existing structure to pypi and possibly make another issue if we want to split up the repo. Any further thoughts @zerebubuth, @iandees, @nvkelso ?

―
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[pnorman]

👍 to pub now, 2.0 can be a split if desired.

Operational structure for how Mapzen processes tiles

What does this consist of?

[rmarianski]

Operational structure for how Mapzen processes tiles

What does this consist of?

Managing the tile processing pipeline we have on running on aws, eg sqs, redis, s3.

[pnorman]

Everything except tilequeue is now being pulled from pypi, so it's just it left. Should I open an issue on its repo?

[nvkelso]

I've added tilezen/tilequeue#220 – but we also have Dockerization in the mix via #93 so a few different planes in the air right now.

[pnorman]

Anything I can do to help on this?

[nvkelso]

@rmarianski can you take a fresh look at this, please?

[rmarianski]

Apologies for this taking so long. I'll go ahead and push over the latest vector-datasource, tileserver, and tilequeue releases to pypi tomorrow morning.

[rmarianski]

vector-datasource, tileserver, and tilequeue have been published to pypi.