dev into main #203
dev into main #203
Conversation
…van predictor jaar)
…nu nog te vaak te gebeuren
…ictor selectie kaart/grafiek wordt nog vaker geladen soms case study gebruikt nog niet juiste jaar voor outcome tabel
outcome table year correctly collected from case study data different years selectable for predictor and outcome
108 different years
152 cultural gems
|
@niekvanruler , it appears that the automated build of the docker image is failing. Do you have suggestions to resolve this? |
186 graced co2 emmissions
|
@doug-leasure Pushing of the docker image to our registry isn't working anymore due to the increased security on the server. We are discussing with system management how to resolve this. |
Thanks @niekvanruler . In the meantime, could you please confirm that the commits from your team in this pull request are ready to be merged into the main branch (i.e. to be deployed to the production server when you resolve the docker issue)? |
|
@doug-leasure We will setup a acceptation server to check if everything is ok. This server will have the frontend code from the dev branch and is connected to the production database. |
|
System management made some changes, so pushing the image to our registry server is working again. |
Update 31_graced_co2.sql
185 social connectedness index. still we need a conversation to add ufnctionality to the website to improve visual for country code sin dropdown list
Merging dev into main to capture a few minor repo reorganisation efforts.
@niekvanruler , can you please take a quick look to confirm the changes here are okay to merge into main for the production server?