Geoapify key provided by the server
Closes #1074
What does this MR do?
foodsharing-ansible!12 (merged) adds the key for the geoapify map tile api to the php config. This is the necessary code change that forwards the key to the client.
How confident are you it won't break things if deployed?
Very sure
Links to related issues
How to test
- Checkout branch locally
- Open the map and see that the tiles are not being loaded
- Add the old key as
define('GEOAPIFY_API_KEY', '7649893675aa4d0c95ddb75ffef637fd');to config.inc.dev.php - Now the map tiles should load
Checklist
-
added a test, or explain why one is not needed/possible... -
no unrelated changes -
asked someone for a code review -
set a "for:" label to indicate who will be affected by this change -
added to the next milestone (see https://gitlab.com/foodsharing-dev/foodsharing/-/milestones, unless it has a "for:Dev" label) -
added an entry to CHANGELOG.md -
added a short text that can be used in the release notes -
Once your MR has been merged, you are responsible to create a testing issue in the Beta Testing forum: https://foodsharing.de/?page=bezirk&bid=734&sub=forum. Please change the MRs label to "state:Beta testing". - Consider writing a detailed description in German.
- Describe in a few sentences, what should be tested from a user perspective.
- Also mention different settings (e.g. different browsers, roles, ...) how this change can be tested.
- Be aware, that also non technical people should understand.
Release notes text in German
Edited by Alex