pygeoapi
pygeoapi copied to clipboard
geopython
admin GUI
Is your feature request related to a problem? Please describe. Some users have difficulty configuring due to yml syntax issues, and the general length + complexity of the yml when many resources are configured.
Describe the solution you'd like A GUI to configure pygeoapi, perhaps just a simple HTML form, perhaps in React.
@webb-ben and I are pursuing this on our own to serve some organizations that have expressed interest. If there is interest in this being a core feature, can open a draft PR.
+1 . My personal pref would be using VueJS over React. IMO the pygeoapi config structure could first be made more 'composable'/'loosely coupled', by allowing e.g. Collections configured as per-collection-file-yaml's in a directory.
ldproxy, another OGC API server, has a 'manager' UI doing something similar with also a directory-based config convention:
https://github.com/interactive-instruments/ldproxy/tree/master/ldproxy-manager
@justb4 If this is something that is wanted enough, I would be interested in implementing that sort of behavior for the config. Probably would make sense to happen in a different branch/issue that an admin GUI, right?
Hi @ksonda , I'm thinking of creating a config yml generator to help users use GUI form to generate files. Please let me know if you are working on it, otherwise I can then spin up an issue.
Thanks
@webb-ben can you show where current draft and any feedback is? You're welcome to iterate on that or try a different implementation if you want. Our work on this is not immediate for the time being.
@krishnaglodha @ksonda cc: @tomkralidis
This is implemented in cgs-earth/pygeoapi:admin. Simultaneous to the GUI, working is being done to build out an admin api that is in line with OGC API - Features - Part 4.
HI @webb-ben , I cloned the repo and it's running but when I do /admin I'm getting error, can you please tell how can I access admin panel ?
@krishnaglodha Could you tell me the error you are getting? /admin should be redirecting to /login if credentials have not been provided.
I just rebased the branch and am able to get it running using this docker compose file.
An admin API is now merged in master (#1137) which includes a simple UI.
An enhanced UI (my preference would be Vue.js) can be realized in as a separate project in a separate repository (basically an AJAX client).
