PEERINGDB_USERNAMEdefine('PEERINGDB_USERNAME', 'username');
|
Default value: none The username for the account used to connect to the PeeringDB API Instead of saving the username and password in the database, the values can be hard coded into globals.php PEERINGDB_PASSWORDdefine('PEERINGDB_PASSWORD', 'mypass');
|
Default value: none The password for the account used to connect to the PeeringDB API PEERINGDB_URLdefine('PEERINGDB_URL', 'https://www.peeringdb.com/api/');
|
Default value: https://peeringdb.com/api/ The URL of the PeeringDB API. Alternate value: https://beta.peeringdb.com/api/ | Info |
|---|
| title | PeeringDB URL Change, March 2022 |
|---|
| Previous versions of PeeringDB allowed authenticated requests to https://peeringdb.com/api/. As of March 2022, PEERINGDB_URL must be set to https://www.peeringdb.com/api/ for authenticated requests to succeed. Existing local customers who already have their peeringdb account details saved in Provision should update PEERINGDB_URL in globals.php to: | Code Block |
|---|
define('PEERINGDB_URL', 'https://www.peeringdb.com/api/'); |
Customers that do not already have their peeringdb account details saved will not currently be able to add their account through the UI, because it will fail the "valid account test" which uses the hardcoded string value. Until a patch is available, affected users may directly save the account information using the save_account API call:
| Code Block |
|---|
https://cloud.6connect.com/APIv2/spec.php?family=peering#/default/save_account |
|
PEERINGDB_CACHE_TTLdefine('PEERINGDB_CACHE_TTL', 43200);
|
Default value: 43200 (12 hours) How often (in seconds) to purge the cached PeeringDB API calls. If a customer wants real time access, this can be set to 0. If experiencing major lag issues with real time access, it is recommended to increase to increase the cache TTL from 0 to 5, 10, or 15 minutes.
| 