On Thu, Feb 24, 2011 at 02:18:07PM -0800, Luis Esteves wrote:
> In our organisation we have 4 postfix servers.
>
> Each time i need to add a new configuration to the transport file (for a new
> domain), i need to update the transport file on each server.
> This is cumbersome. Connect on each server with ssh, update the transport
> file, et run make to generate a db file.
>
> Is there an easy way to update all files on each server easily (without
> generating ssh public/private keys and running these commands from one
> server) ?
I commit configuration changes to an SVN repository, and use a push
script from a trusted management node that checks out the latest
commited versions of all pertinent files and deploys them to all
the nodes.
> Is it a good idea to use a centralized PostgreSQL database to store the
> Postfix configuration files ?
Databases are not particularly good file-systems, and typically revision
control is a good idea. So "svn", "git" or even "cvs" is usually a better
choice than a database.
Now if the data in question is transport table entries, rather than
main.cf, master.cf, ... a database is sometimes a reasonable way to
manage tabular data.
--
Viktor.
