Comments (10)
Thanks @radumas for posting this fix. I was stuck after following the install guide.
from tileserver.
Instead of having requirements files in each repo though, I think we should have a single set of requirements just in vector-datasource that assumes installation of everything for setup purposes, since that's the useful part practically anyway.
I think that would be useful for people who want the easiest route to setting everything up.
We're releasing a bunch of packages to PyPI now. Would it make sense to use those for released versions, so that we didn't need git versions in requirements.txt
? In other words, that we'd specify version constraints in setup.py
to avoid things like tileserver
referencing DataFetcher
without having pulled in a sufficiently new version of tilequeue
?
from tileserver.
This would also be an issue if someone followed the current version of the vector-datasource install guide using the checkout versions listed there.
from tileserver.
Yea, good point, those do have master set for those releases. Those instructions are usually tested just with master, and I take the steps you describe above when switching versions. We should probably at a minimum update the documentation to call this out, and ensure that going forward releases have specific versions set in their requirements files.
Instead of having requirements files in each repo though, I think we should have a single set of requirements just in vector-datasource that assumes installation of everything for setup purposes, since that's the useful part practically anyway. We could either split apart just the upstream dependencies from the versions of the tilezen repos, and make separate explicit pip install steps for the install or tilezen repos which might make this more visible. That would also mean that we wouldn't have the problem of having to update the requirements files when we release. Or we just add a step to the instructions that says to edit the bottom of the requirements file for the particular versions desired.
What does everyone think?
from tileserver.
So tilequeue
seems to behave happily as a dependency of vector-datasource
since AFAIK it doesn't require configuration. Would it be possible to configure vector-datasource
's setup (or a version of it) to add tileserver
as a git submodule, so that the tileserver
config is easily accessible to configure (or otherwise put the tileserver/__init__.py
and config.yaml
in an accessible location).
Then the instructions to get a "standard install" would be to clone vector-datasource
, checkout the latest release, and then run setup.
from tileserver.
I think that would be useful for people who want the easiest route to setting everything up.
Which is where we have the problems anyway right? :)
We're releasing a bunch of packages to PyPI now. Would it make sense to use those for released versions, so that we didn't need git versions in requirements.txt?
We deploy off branches too, so we would need a workflow for that anyway.
from tileserver.
I think PyPi makes even more sense for a simple, stable deployment.
We deploy off branches too, so we would need a workflow for that anyway.
You all can figure out what you need for your development
from tileserver.
I think PyPi makes even more sense for a simple, stable deployment.
Yes, I think this is the best way. I thought it was possible now to pip install tileserver
?
from tileserver.
@pnorman Filed related issues this weekend that we're working on. Thanks everyone for the feedback!
from tileserver.
Closing for inactivity.
from tileserver.
Related Issues (20)
- ImportError: No module named tileserver.cache HOT 2
- custom layers in postgis HOT 9
- ImportError: No module named meta.python HOT 11
- psycopg2.ProgrammingError HOT 15
- Performance question HOT 3
- Tileserver is not accepting remote connections HOT 1
- Error with python setup.py develop, install directory is hard-coded (or sudo is required) HOT 3
- Cat readme into setup.py long description HOT 4
- pip intall error HOT 2
- pip install fails HOT 2
- Provide binary via pip. HOT 2
- AssertionError: Missing min_zoom in layer water
- Not seeing any output through tileserver appears to be running. Any advice? HOT 2
- My Server seems very slow in serving tiles,pls explain how to add tilequeue for buffering HOT 6
- CORS problem due to missing min_zoom in layer water HOT 3
- Question about scaling HOT 11
- syntax error HOT 1
- Writing to cache/store after generation HOT 4
- Redis caching problem on last config file HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from tileserver.