A static version of the webpage is built and put into /static to be served by flask/uwsgi/nginx.
Deployment can now be done either by sending the docker images to the server or rebuilding on the server. Only the api and nginx container needs to be run, the frontend container is only for local development.
The docker image for api has been changed from ubuntu to python 3.8 on debian buster because then no apt invocation is needed and everything is run a bit faster.
Cross-origin has been improved to only include localhost:1234 where the frontend dev server is running. It's now done on every request implicitly (no decorator needed).
This PR also includes frontend updates of precalculated boxplots and testing that were too much of a hassle to detangle. Not expecting Dimitrios to look at this, will sync this with Martin at some point soon.
This PR additionally includes git hub actions that runs the build and the tests because it was about time to add this.
Ideally there should be some end-to-end test that checks that the served built frontend actually does something sensible but there is no such test yet.
A static version of the webpage is built and put into /static to be served by flask/uwsgi/nginx.
Deployment can now be done either by sending the docker images to the server or rebuilding on the server. Only the
apiandnginxcontainer needs to be run, thefrontendcontainer is only for local development.The docker image for api has been changed from ubuntu to python 3.8 on debian buster because then no apt invocation is needed and everything is run a bit faster.
Cross-origin has been improved to only include localhost:1234 where the frontend dev server is running. It's now done on every request implicitly (no decorator needed).
This PR also includes frontend updates of precalculated boxplots and testing that were too much of a hassle to detangle. Not expecting Dimitrios to look at this, will sync this with Martin at some point soon.
This PR additionally includes git hub actions that runs the build and the tests because it was about time to add this.
Ideally there should be some end-to-end test that checks that the served built frontend actually does something sensible but there is no such test yet.