I was thinking we should probably agree on a way of storing the API keys so we can share them amongst the projects.
Do you have any ideas of a good table schema for it?
We've moved the forum!
Please use forum.silverstripe.org for any new questions
(announcement).
The forum archive will stick around, but will be read only.
You can also use our Slack channel
or StackOverflow to ask for help.
Check out our community overview for more options to contribute.
That makes sense to me. Typically, we store this sort of information in the _config.php file of the main module for your project (the one with the same name as your project). Using PHP's define function is typically the way to create a constant string for this.
We hope to have the gsoc branch set up in SVN shortly, and adding it to the shared _config.php file will ensure that the other GSoC people have the keys as well.
The other way to set up configuration options is to create static methods on your application's classes. Something like:
GoogleMapsIntegration::set_api_key('dfadsfasdfasdfasdfasd');
This has the advantage of being easy to spot in an API documentation or by browsing the function listing in the code.
I agree with Sam on the static method implementation. Mashup module classes will follow that standard.