| HTML |
|---|
<div id="google_translate_element"></div>
<script type="text/javascript">
function googleTranslateElementInit() {
new google.translate.TranslateElement({pageLanguage: 'en'}, 'google_translate_element');
}
</script>
<script type="text/javascript" src="//translate.google.com/translate_a/element.js?cb=googleTranslateElementInit"></script> |
Peering Setup - Local Installations:
...
| Warning |
|---|
As of PeeringDB 2.0, SQL dump files are no longer provided. If you are using ProVision 5.3.0 or higher, you must follow this new install process. If you are using a lower version of ProVision, then please follow the instructions in the previous version of this page. |
...
1) Create a new database to store the PeeringDB data. This must be on the same server as the database which is used by ProVision.
2) Download, install, and use the PeeringDB Python Client to populate the database.
The PeeringDB documentation is available here: http://peeringdb.github.io/peeringdb-py/
3) Once this has been done, edit the ProVision global configuration file located here:
...
| Code Block | ||
|---|---|---|
| ||
$peeringdb_host = 'localhost'; // Database host must be the same for provision and peering $peeringdb_username = 'username'; // username for the MySQL user $peeringdb_password = 'password'; // password for the MySQL user $peeringdb_db_name = 'peeringdb'; // name of the database in MySQL |
...
4) Periodically sync with the PeeringDB server to get the latest updates. This can be done manually, or there are instructions in the PeeringDB documentation on how to automatically schedule syncs using cron (http://peeringdb.github.io/peeringdb-py/cli/#sync).