Skip to content
This repository was archived by the owner on Oct 7, 2019. It is now read-only.

migrate to "serverless" #25

Open
gassc opened this issue May 14, 2018 · 0 comments
Open

migrate to "serverless" #25

gassc opened this issue May 14, 2018 · 0 comments

Comments

@gassc
Copy link
Member

gassc commented May 14, 2018

I think with a hosted AGOL resource proxy, I can drop the Flask portion of this application and still use Esri premium services for the watershed and elevation profile fallback. That would vastly simplify builds, deployment, and hosting (I could even run it from a gh-pages branch here).

It would require:

  • a bit of work to migrate from the Flask application structure and jinja2 templates to a Jekyll structure with liquid templates.
  • some slight changes the javascript to remove token handling
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant