On 04/10/2013 07:08 PM, Dmitry Yemanov wrote:
10.04.2013 17:07, Stefan Heymann wrote:
What about backups? Will GBAK backup and restore these settings so
they don't get lost?
No, these things are unrelated. They won't be lost if you backup/restore
on the same host but you have to copy them
It's up to you to decide. You may move local settings to mydb.conf and
then #include it into databases.conf. But databases.conf is still
necessary to make the server aware of pre-configured databases.
Can you give me/us an idea of what the things are that can be
configured in these files?
On 04/11/2013 04:59 PM, Stefan Heymann wrote:
It's up to you to decide. You may move local settings to mydb.conf and
then #include it into databases.conf. But databases.conf is still
necessary to make the server aware of pre-configured databases.
Can you give me/us an idea of what the things
What’s the point of the rename? It seems to only break existing code
and documentation.
aliases.conf name does not reflect what for this file can be used in
fb3. In addition to defining aliases for databases it now supports
per-database configuration parameters. We (I and Dmitry) failed to
10.04.2013 17:07, Stefan Heymann wrote:
I'm not sure if it is a good idea to have those per-database
configurations in one central place. So when you move a database to
another server you have to copy-and-paste those things to the other
server.
What about having a pair of files:
Question from twitter https://twitter.com/shtue/status/321510432458289152
What’s the point of the rename? It seems to only break existing code
and documentation.
--
Precog is a next-generation analytics platform capable
On 04/09/13 10:38, marius adrian popa wrote:
Question from twitter https://twitter.com/shtue/status/321510432458289152
What’s the point of the rename? It seems to only break existing code
and documentation.
aliases.conf name does not reflect what for this file can be used in
fb3. In addition
