Infrastructure changes (API URLs and auth token) that require code update
The objective of this issue is to document the required client code update because of the two recent changes on the infrastructure:
- A new and long run auth token (default token - unauthenticated user)
- API domains/URLs changes for different environments
New authentication token
This change has required two changes:
- The new token has been inserted manually in the production executable code (
bundle-es5.js
) (not recommendable practice, a temporary patch until the next deployment) - The new token has been inserted in the developing code and it's been tested in stagging (it is still necessary to test it in production)
API domains/URLs changes
These has required two changes:
- The new API domain/URL has been inserted manually in the production executable code (bundle-es5.js). The value of the API_HOST variable was changed from
encyclopedia-api.nomad-coe.eu
toencyclopedia.nomad-coe.eu
and the API_BASE_URL is the API_HOST plus theapi/v1.0/
string now (v1.0/
before) - The API domains/URLs has been changed for all the cases (different environments) in the developing code and they've been tested in local dev and stagging environments (it is still necessary to test it in production)
In addition, it'd be good to take the opportunity to check if the configuration specified in the current code is right or it can be improved (@ivancea):
- Production server. API HOST:
https://encyclopedia.nomad-coe.eu/
API PATH:api/v1.0/
- Staging/local installations server. API HOST:
/
API PATH:v1.0/
As said above, in the next production deployment we should be attentive and check that everything works fine (as expected)