Use pysepal's TileBridge - #21
Open
dfguerrerom wants to merge 1 commit into
Open
Conversation
The comm-bridge component moved to pysepal, where it belongs: both tile servers need it and every SEPAL app was going to copy it. The opt-out flag moves with it as PYSEPAL_TILE_BRIDGE. Needs pysepal 3.9.0.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cleanup items (a) and (b) of the tile-transport plan.
The comm bridge that carries kernel-local tile URLs to the browser was a private component in
app.py, but both tile servers need it and every SEPAL app was going to copy it — so it moved to pysepal assolara.TileBridge. The app keeps one line. The opt-out flag moved with it and is nowPYSEPAL_TILE_BRIDGErather than a name borrowed from localtileserver, which never knew about it.Blocked on pysepal 3.9.0. Tests: 198 passed.