Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compare Master and developp #119

Merged
merged 195 commits into from
Jan 20, 2022
Merged

Compare Master and developp #119

merged 195 commits into from
Jan 20, 2022

Conversation

pierrejego
Copy link
Contributor

Draft to compare master and develop

Rémi Desgrange and others added 30 commits March 13, 2020 11:50
Also change images org to geobretagne, since mviewer org doesn't exist
in docker hub.
* using flask to serve the static files
* removing the frontend part
* simplifying the docker composition
Draw attention to GeoServer specificities
* Using the docker subdirectory to store docker-specific files
 (dockerfiles, configurations, ...)
* In case of python backend, the config.json is only used client side,
  as the configuration is done via environment variables on the backend.
  Keeping the docker version of the config in the static/ files provided
  by the backend as symlink.
PHP backend is working in the docker-compo, still need to
debug the python backend.
* python services behind 'srv/'
* make the services url for list/delete configurable
… host

* Same ports convention for php & python backends (same listening port)
Rémi Desgrange and others added 5 commits June 17, 2021 09:31
Add types packages in dev-requirements.txt to make `mypy` happy.
Following this issue, moby/moby#37965 adding
DOCKER_BUILDKIT env var make the build working.
Fixing CI by adding magical env var
@pierrejego pierrejego changed the title Draft to compare Compare Master and developp Dec 22, 2021
@pierrejego
Copy link
Contributor Author

Seul le config-sample.json est en conflit.
Aucun soucis pour merger et faire une release.

@pierrejego pierrejego added this to the 3.2 milestone Dec 22, 2021
@pierrejego
Copy link
Contributor Author

link to #112

@bchartier
Copy link
Contributor

Seul le config-sample.json est en conflit.
Aucun soucis pour merger et faire une release.

A priori il n'y a rien à faire pour le fichier config-sample.json : la version de la branche develop a l'air très bien. Si ?

@bchartier
Copy link
Contributor

Seul le config-sample.json est en conflit.
Aucun soucis pour merger et faire une release.

A priori il n'y a rien à faire pour le fichier config-sample.json : la version de la branche develop a l'air très bien. Si ?

J'ai résolu le conflit sur config-sample.json.

Copy link
Contributor

@bchartier bchartier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

J'ai rapidement testé cette PR avec un docker compose.
Je n'ai pas repéré d'anomalie.
J'ai noté une erreur lors de l'exécution des tests unitaires sur le backend Python (dans les Github actions).

@spelhate
Copy link
Collaborator

spelhate commented Jan 19, 2022

Les images docker sont maintenant générées sans erreurs et poussées sur hub docker.
De mon point de vue, on peut merger develop dans master une fois la PR testée.

@spelhate spelhate marked this pull request as ready for review January 19, 2022 16:42
@spelhate spelhate merged commit 9824f25 into master Jan 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants