Closed carloscdias closed 6 years ago
Awesome, thank you! You'll also need to add the environment variable to:
REACT_APP_MAPBOX_TOKEN=change_me
)If you haven't already, be sure to ask Mike to add his mapbox token to the Azure environment so that it can be used there.
A day or two after this PR is merged, I will deactivate the API key that's currently being used.
Thanks for catching that @rdebeasi let me know if everything seems ok now. @mikefab We need to add this variable in Azure
Looks good to me! I will hold off on merging this until the variable is added to Azure.
Thanks!
Hi all! Just a reminder that the application is still using my Mapbox API token. I'm planning to deactivate that API token in June.
Please don't forget to:
REACT_APP_MAPBOX_TOKEN
environment variable in AzureThank you!!
Hi folks! Just a friendly reminder that the old API token will be disabled in a few weeks. Before the end of May, please add your own (free) API token in Azure and merge this PR. If for some reason there's a problem with this PR and it cannot be merged, you could hard-code a different API token as a stopgap solution.
I need to deactivate the existing token at the beginning of June. If a new API token is not supplied by then, the dev environment for magicbox-maps v2 will stop displaying the map until a new API token is added.
I'm happy to answer any questions that you might have. Thank you! :smile:
@mikefab @carloscdias @jflory7
Summary
This PR expects a new environment variable called REACT_APP_MAPBOX_TOKEN to exist and stores it as mapboxToken inside the helper file api-config in order to use this value as the token to access mapbox.