Resolve "BE: Load workspace presets from BE - Opengeoweb"
Closes #6 (closed)
In this MR:
- setup of data for opengeoweb
- change in
cli.py
: if no environment variableDEPLOY_ENVIRONMENT
is set, automatically grab theopen
data
How to test:
- build the app without setting
DEPLOY_ENVIRONMENT
so it defaults toopen
(see here- alternatively, you could also do
export DEPLOY_ENVIRONMENT="open"
- alternatively, you could also do
- check that calling the
/workspacepreset
gives the contents of the hamburger menu in opengeoweb- You could do this by opening http://127.0.0.1:8080/workspacepreset
- Or going to http://127.0.0.1:8080/docs and executing the call there
Also:
- build with docker, set the .env variable without explicitly setting
DEPLOY_ENVIRONMENT=open
(see here- If it is set, you could run
unset DEPLOY_ENVIRONMENT
- If it is set, you could run
- running the docker build command will generate a warning, that value is set to empty string
- verify that containers are built and the correct data is shown
- Use
curl -kL https://0.0.0.0:4443/workspacepreset | python -m json.tool
- Or go to
https://0.0.0.0:4443/docs
and use the interface
- Use
FYI: Follow up:
To deploy to opengeoweb:
- a tag should be created
- a manual step should be done to update the database
Edited by Mizzi van der Ven