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

#7165 clean up configs for externalized datadir and documentation update #8522

Closed
wants to merge 5 commits into from

Conversation

MV88
Copy link
Contributor

@MV88 MV88 commented Aug 30, 2022

Description

To merge after this one: #8511

This pr introduces:

  • clean up of config
  • some changes to the scripts section with retrocompatibility
  • documentation update including release procedure

Please check if the PR fulfills these requirements

What kind of change does this PR introduce? (check one with "x", remove the others)

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Other... Please describe:

Issue

What is the current behavior?

#7165 externalize datadir

What is the new behavior?

Now authentication rules are not part of localconfig
scripts have changed

Breaking change

Does this PR introduce a breaking change? (check one with "x", remove the other)

  • Yes, and I documented them in migration notes
  • No

Other useful information

@MV88 MV88 added enhancement Priority: High Internal BackportNeeded Commits provided for an issue need to be backported to the milestone's stable branch QF Quality Friday DevOps labels Aug 30, 2022
@MV88 MV88 self-assigned this Aug 30, 2022
@tdipisa tdipisa mentioned this pull request Aug 30, 2022
6 tasks
@tdipisa tdipisa removed the request for review from allyoucanmap September 21, 2022 09:12
Copy link
Member

@offtherailz offtherailz left a comment

Choose a reason for hiding this comment

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

During the release I checked your canges to the release procedure to see these what could conflict with an update due to the things to update now and I notices some parts to comment.
I write this (incomplete) review to avoid to loose these comments. We can check it at the proper moment.

## [${newReleaseNumber}](https://github.com/geosolutions-it/MapStore2/tree/v${newReleaseNumber}) (${today})

- **[Full Changelog](https://github.com/geosolutions-it/MapStore2/compare/v${oldReleaseNumber}...v${newReleaseNumber})**

Copy link
Member

Choose a reason for hiding this comment

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

need to add new-features label tag too,

Something like :

- **[Implemented new features](https://github.com/geosolutions-it/MapStore2/issues?q=is%3Aissue+milestone%3A${newVersionNumber}+is%3Aclosed+label%3A%22New+Feature%22)**

- **[Fixed bugs](https://github.com/geosolutions-it/MapStore2/issues?q=is%3Aissue+milestone%3A%22${newReleaseNumber}%22+is%3Aclosed+label%3Abug)**

- **[Closed issues](https://github.com/geosolutions-it/MapStore2/issues?q=is%3Aissue+milestone%3A%22${newReleaseNumber}%22+is%3Aclosed)**
Copy link
Member

Choose a reason for hiding this comment

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

Need to add the related mapstore extension link, something like


- **[Related MapStrore extensions release v${newReleaseNumber}](https://github.com/geosolutions-it/MapStoreExtension/releases/tag/v${newReleaseNumber)**

Comment on lines +329 to +330
'/geofence': {
target: `${baseUrl}`
Copy link
Member

Choose a reason for hiding this comment

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

geofence doesn't exist locally, I should remove it.

Comment on lines +303 to +324
"start": "npm run frontend:dev",
"start:both": "concurrently \"npm:frontend:dev\" \"npm:backend:dev\"",

"frontend:dev": "webpack serve --progress --color --port 8081 --hot --inline --config build/webpack.config.js --content-base web/client",
"frontend:dev-prod": "webpack serve --progress --color --port 8081 --hot --inline --config build/prod-webpack.config.js --content-base web/client",
"frontend:build": "npm run clean && mkdirp ./web/client/dist && webpack build --progress --color --config build/prod-webpack.config.js",
"compile": "npm run frontend:build",

"backend:build": "mvn clean install -Pprinting",
"backend:dev": "npm run backend:build && mvn cargo:run -f ./product/pom.xml",

"pretest": "npm run doc:clean && npm run lint",
"test": "karma start ./build/karma.conf.single-run.js --color",
"test:watch": "karma start ./build/karma.conf.continuous-test.js --color",
"continuoustest": "npm run test:watch",

"doc": "docma -c build/docma-config.json --dest web/docs",
"build-doc": "mkdocs build",
"serve-doc": "mkdocs serve",
"cleandoc": "rimraf web/docs && rimraf web/client/mapstore/docs",
"doctest": "docma -c build/docma-config.json --dest web/client/mapstore/docs && echo documentation is accessible from the mapstore/docs path when running npm start",
"i18n": "node utility/translations/findMissingTranslations.js",
"doc:clean": "rimraf web/docs && rimraf web/client/mapstore/docs",
"doc:test": "docma -c build/docma-config.json --dest web/client/mapstore/docs && echo documentation is accessible from the mapstore/docs path when running npm start",
"doc-build": "mkdocs build",
"doc-serve": "mkdocs serve",
"cleandoc": "npm run doc:clean",
Copy link
Member

Choose a reason for hiding this comment

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

  • npm start should run both front-end and back-end (running front end alone is not immediate, you have to change webpack configuration, so it is better to use the simple command for the easer way). Instead of start:both
  • I should shorten frontend and backend into fe: and be:. So we can write fe:start, fe:build
  • I should avoid dev and instead i should use start. dev is harder to understand, you are starting the front-end and back-end (only the front-end in fact is in dev mode).
  • Accordingly to the semantic used, we should use also doc:buildm doc:serve and doc:clean, instead of doc-build, doc-serve and cleandoc.
@tdipisa tdipisa added this to the 2022.02.01 milestone Sep 29, 2022
@offtherailz offtherailz mentioned this pull request Sep 30, 2022
12 tasks
@offtherailz
Copy link
Member

closing in favor of #8645

@tdipisa tdipisa removed the BackportNeeded Commits provided for an issue need to be backported to the milestone's stable branch label Oct 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment