On Wed, Jun 4, 2014 at 3:24 PM, Stephen Frost <sfrost@snowman.net> wrote:
> Alvaro,
>
> * Alvaro Herrera (alvherre@2ndquadrant.com) wrote:
>> 1. psqlodbc.postgresql.org which would be its own VM running lighttpd
>> and serving the static files you have in the psqlodbc-www.git repo.
>
> For my 2c- I do *not* want a dedicated VM for this. If we go this way,
> that VM would be for all small projects like this which have static
> webpages, ala the developer webpages and git.postgresql.org. That VM
> wouldn't be the same one that the main site is on, but it also wouldn't
> be dedicated to serving the 20-or-so static files that make up the ODBC
> website.
I don't necessarily disagree, but for the record, the JDBC project
does have it's own VM for this purpose.
>> 2. www.postgresql.org/psqlodbc which would go through Varnish and
>> whatnot. While this means we don't need a separate VM, but on the other
>> hand I think it will be harder to integrate getting the files from the
>> git repo and configured correctly in the vhost, etc.
>
> Updates would also need to go through the -www team if it was integrated
> as part of the main site. There are pros and cons for each option.
>
> Thanks,
>
> Stephen
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
