From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: Moving psqlodbc from pgfoundry to github |
Date: | 2014-06-04 14:24:09 |
Message-ID: | 20140604142409.GZ2556@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Alvaro,
* Alvaro Herrera (alvherre(at)2ndquadrant(dot)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.
> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2014-06-04 14:49:13 | Re: Moving psqlodbc from pgfoundry to github |
Previous Message | Alvaro Herrera | 2014-06-04 14:20:20 | Re: Moving psqlodbc from pgfoundry to github |