docs: rewrite docu for docker setup

[jhaeu]

Pull Request Checklist

• 1. I have rebased the latest version of the main branch into my feature branch and all conflicts
  have been resolved.
• 2. I have added information about the change/addition to functionality to the CHANGELOG.md file under the
  [Unreleased] heading.
• 3. I have documented my code using JDocs tags.
• 4. I have removed unnecessary commented out code, imports and System.out.println statements.
• 5. I have written JUnit tests for any new methods/classes and ensured that they pass.
• 6. I have created API tests for any new functionality exposed to the API.
• 7. If changes/additions are made to the ors-config.json file, I have added these to the ors config documentation
  along with a short description of what it is for, and documented this in the Pull Request (below).
• 8. I have built graphs with my code of the Heidelberg.osm.gz file and run the api-tests with all test passing
• 9. I have referenced the Issue Number in the Pull Request (if the changes were from an issue).
• 10. For new features or changes involving building of graphs, I have tested on a larger dataset
  (at least Germany), and the graphs build without problems (i.e. no out-of-memory errors).
• 11. For new features or changes involving the graphbuilding process (i.e. changing encoders, updating the
  importer etc.), I have generated longer distance routes for the affected profiles with different options
  (avoid features, max weight etc.) and compared these with the routes of the same parameters and start/end
  points generated from the current live ORS.
  If there are differences then the reasoning for these MUST be documented in the pull request.
• 12. I have written in the Pull Request information about the changes made including their intended usage
  and why the change was needed.
• 13. For changes touching the API documentation, I have tested that the API playground renders correctly.

Fixes # .

Information about the changes

• Key functionality added: New docu for new fatJar based docker image and docker-compose file
• Reason for change: Documentation for docker setup was outdated (still docker setup with WAR+Tomcat)

Examples and reasons for differences between live ORS routes, and those generated from this pull request

Required changes to ors config (if applicable)

[MichaelsJP]

Intermediate review. Not yet through.

[MichaelsJP]

We should also adapt the installation part in the Readme.md.

[MichaelsJP]

LGTM, but someone else from the team should definitely look over it as well!

One thing, please add a changelog entry still before merging.

[koebi]

Can you point me to the workflow that takes care of the release assets?

Also, we should add an overview of the existing official docker images and link it from the README.

[MichaelsJP]

Can you point me to the workflow that takes care of the release assets?

@koebi Here you go

openrouteservice/.github/workflows/publish-tagged-release.yml

Line 79 in d90a23f

build_and_publish_release_artifacts:

This releases the docker image as well as uploading release artifacts.

---

This workflow takes care of setting the additional tags: vX and latest
https://github.com/GIScience/openrouteservice/blob/main/.github/workflows/release-tag-latest.yml

[TheGreatRefrigerator]

OK

[koebi]

Two minor notes, otherwise it looks good to me :)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud