I want to store my database connection information in a single file, which both PHP and Ruby scripts can use.
Should I use name-value pairs, yaml, xml, or something else?
A:
YAML, XML, JSON, a proper database — any common format will have support on both sides.
Chuck
2009-09-19 07:24:55
You're suggesting I put my database configuration in 'a proper database'? Where then would I store the configuration information to connect to that database?
brianegge
2009-09-19 07:50:32
Well, you have to hardcode the info to get to the config no matter what format you use — SQLite wouldn't be much more of a stretch in that respect than XML. But I wasn't actually suggesting that option in particular — I just threw it in at the end to emphasize the "any common data storage format work."
Chuck
2009-09-19 08:00:38
To whoever downvoted: Feel free to point out the factual inaccuracy in your post. Because it's not there.
Chuck
2009-09-19 19:02:42
Agreed that SQLite would be a common format readable by both. I quite like SQLite, but would associate the term 'proper database' with an external database server.
brianegge
2009-09-21 02:19:36
+4
A:
YAML is probably a good option - it is very simple to implement, yet it can take you a long way with flexibility.
BTW. Sounds as if you may have some similar problems that are discussed on railsforphp.com Here is the article on PHP and YAML:
leonm
2009-09-19 07:39:15
+1
A:
I'd suggest JSON. It can be read natively by PHP with json_decode(). Surly Ruby must have some facilities to read JSON. Plus you can read it directly from JavaScript.
Kamil Szot
2009-09-19 08:33:48
Thanks. It looks like it would be slightly easier to get Ruby to read JSON that to get PHP to read YAML. Both require an extension, but I'm more familiar with installing ruby gems.
brianegge
2009-09-21 02:11:04