Thread: psqlODBC website face-lift
The psqlODBC website, at psqlodbc.projects.pgfoundry.org, is a bit outdated. It's missing links to the new git repository (it didn't have a link to the old CVS repo either), the pgfoundry page, and the downloads. Also, it doesn't look modern. I created a little mock-up of what the site would look like using the main PostgreSQL web site's style: http://psqlodbc.mooo.com/ (that domain is just a temporary address for showcasing this - I'm not proposing that we change hosting) The sub-pages, like the howtos and faq, are unchanged. On the front page, I created a new "history" section, and move there the paragraphs talking about history from the introduction section. I created a section for "psqlODBC development", with links to the mailing list archives and the git repository. I also added a link to the downloads page in the introduction - that's the first thing that users look for, so it's good to have it at the top. The important links are also available in the top navigation bar. I think this page now contains all the important information about the project. I propose that we replace the contents of the current web site at psqlodbc.projects.pgfoundry.org with this. I don't know what the PostgreSQL project's policy is on using the website graphics and stylesheets, but we can work that out. - Heikki
On Mon, Apr 22, 2013 at 12:38 PM, Heikki Linnakangas <hlinnakangas@vmware.com> wrote: > The psqlODBC website, at psqlodbc.projects.pgfoundry.org, is a bit outdated. > It's missing links to the new git repository (it didn't have a link to the > old CVS repo either), the pgfoundry page, and the downloads. Also, it > doesn't look modern. > > I created a little mock-up of what the site would look like using the main > PostgreSQL web site's style: > > http://psqlodbc.mooo.com/ > > (that domain is just a temporary address for showcasing this - I'm not > proposing that we change hosting) > > The sub-pages, like the howtos and faq, are unchanged. On the front page, I > created a new "history" section, and move there the paragraphs talking about > history from the introduction section. I created a section for "psqlODBC > development", with links to the mailing list archives and the git > repository. I also added a link to the downloads page in the introduction - > that's the first thing that users look for, so it's good to have it at the > top. The important links are also available in the top navigation bar. > > I think this page now contains all the important information about the > project. I propose that we replace the contents of the current web site at > psqlodbc.projects.pgfoundry.org with this. No objection here. Do you have access through pgFoundry? > I don't know what the PostgreSQL project's policy is on using the website > graphics and stylesheets, but we can work that out. There's no problem with that. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Resending without attachments, previous post stalled due to size limit. I uploaded the attachments to http://psqlodbc.mooo.com/tarballs/ On 22.04.2013 14:58, Dave Page wrote: > On Mon, Apr 22, 2013 at 12:38 PM, Heikki Linnakangas > <hlinnakangas@vmware.com> wrote: >> I think this page now contains all the important information about the >> project. I propose that we replace the contents of the current web site at >> psqlodbc.projects.pgfoundry.org with this. > > No objection here. Do you have access through pgFoundry? No. Here's a tarball of the contents at the mock site, could you update the site, please? Also, the CVS repository at pgfoundry should be disabled, now that the git repository is the official one. Attached is a tarball of the CVS repository, we should put that up on the site, for archival purposes. I got it from Marc, but I removed the CVSROOT directory which contained some semi-sensitive information like the 'history' log file and configuration details. So this should be safe to publish to the public. We probably should move the website stuff out of the main git repository. Release notes and some of the documentation that might be version-specific should stay, but the web home page, FAQ, and howtos should go elsewhere. I think we should create a separate git repository for that, psqlodbc-www, similar to how you've done with pgadmin. >> I don't know what the PostgreSQL project's policy is on using the website >> graphics and stylesheets, but we can work that out. > > There's no problem with that. Ok, cool. - Heikki
Thanks - updated. I put a link to the old CVS tarball on the index page as well. FYI, you should be able to update the website yourself - SSH to psqlodbc.projects.pgfoundry.org and the docroot is here: /home/pgfoundry.org/groups/psqlodbc/htdocs. You seem to be in the correct group... On Mon, Apr 22, 2013 at 2:29 PM, Heikki Linnakangas <hlinnakangas@vmware.com> wrote: > Resending without attachments, previous post stalled due to size limit. I > uploaded the attachments to http://psqlodbc.mooo.com/tarballs/ > > > On 22.04.2013 14:58, Dave Page wrote: >> >> On Mon, Apr 22, 2013 at 12:38 PM, Heikki Linnakangas >> <hlinnakangas@vmware.com> wrote: >>> >>> I think this page now contains all the important information about the >>> >>> project. I propose that we replace the contents of the current web site >>> at >>> psqlodbc.projects.pgfoundry.org with this. >> >> >> No objection here. Do you have access through pgFoundry? > > > No. Here's a tarball of the contents at the mock site, could you update the > site, please? > > Also, the CVS repository at pgfoundry should be disabled, now that the git > repository is the official one. Attached is a tarball of the CVS repository, > we should put that up on the site, for archival purposes. I got it from > Marc, but I removed the CVSROOT directory which contained some > semi-sensitive information like the 'history' log file and configuration > details. So this should be safe to publish to the public. > > We probably should move the website stuff out of the main git repository. > Release notes and some of the documentation that might be version-specific > should stay, but the web home page, FAQ, and howtos should go elsewhere. I > think we should create a separate git repository for that, psqlodbc-www, > similar to how you've done with pgadmin. > >>> I don't know what the PostgreSQL project's policy is on using the website >>> graphics and stylesheets, but we can work that out. >> >> >> There's no problem with that. > > > Ok, cool. > > - Heikki -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
The "about" and "privacy policy" links at the very bottom don't work. Also, the archives bottom in the top menu links to archives.postgresql.org, which works but is deprecated -- I suggest www.postgresql.org/list/pgsql-odbc instead (there's one more link to the old archives in the "psqlODBC development" section). -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
On Mon, Apr 22, 2013 at 4:11 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote: > > The "about" and "privacy policy" links at the very bottom don't work. > > Also, the archives bottom in the top menu links to > archives.postgresql.org, which works but is deprecated -- I suggest > www.postgresql.org/list/pgsql-odbc instead (there's one more link to the > old archives in the "psqlODBC development" section). Thanks, fixed. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
On 22.04.2013 16:29, Heikki Linnakangas wrote: > We probably should move the website stuff out of the main git > repository. Release notes and some of the documentation that might be > version-specific should stay, but the web home page, FAQ, and howtos > should go elsewhere. I think we should create a separate git repository > for that, psqlodbc-www, similar to how you've done with pgadmin. I didn't hear any objections to that, so I went ahead. There is now a second repository for the website, at http://git.postgresql.org/gitweb/?p=psqlodbc-www.git. It contains the main page and mediat files, the HOWTOs, and the FAQ. I removed those files from the main psqlodbc repository, they are now maintained in the psqlodbc-www repository. The files with potentially version-specific content - the release notes, compilation instructions, and configuration options - are kept in the main psqlodbc repository. A copy of them is kept in the docs directory of the website; that copy should be updated whenever the files are modified in the main repository. - Heikki
Heikki Linnakangas wrote: > The files with potentially version-specific content - the release > notes, compilation instructions, and configuration options - are > kept in the main psqlodbc repository. A copy of them is kept in the > docs directory of the website; that copy should be updated whenever > the files are modified in the main repository. Would a git submodule help maintain this up to date? -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
On Tue, Apr 23, 2013 at 1:51 PM, Heikki Linnakangas <hlinnakangas@vmware.com> wrote: > On 22.04.2013 16:29, Heikki Linnakangas wrote: >> >> We probably should move the website stuff out of the main git >> repository. Release notes and some of the documentation that might be >> version-specific should stay, but the web home page, FAQ, and howtos >> should go elsewhere. I think we should create a separate git repository >> for that, psqlodbc-www, similar to how you've done with pgadmin. > > > I didn't hear any objections to that, so I went ahead. Sorry, completely managed to miss that you even wrote that :-/ > There is now a second repository for the website, at > http://git.postgresql.org/gitweb/?p=psqlodbc-www.git. It contains the main > page and mediat files, the HOWTOs, and the FAQ. I removed those files from > the main psqlodbc repository, they are now maintained in the psqlodbc-www > repository. Cool. Did you update the website docroot to be a checkout of the repo? Maybe we should just automate pulls in fact, so we can edit the site just by checking in the changes. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
On 23.04.2013 18:55, Dave Page wrote: > On Tue, Apr 23, 2013 at 1:51 PM, Heikki Linnakangas > <hlinnakangas@vmware.com> wrote: >> On 22.04.2013 16:29, Heikki Linnakangas wrote: >> There is now a second repository for the website, at >> http://git.postgresql.org/gitweb/?p=psqlodbc-www.git. It contains the main >> page and mediat files, the HOWTOs, and the FAQ. I removed those files from >> the main psqlodbc repository, they are now maintained in the psqlodbc-www >> repository. > > Cool. Did you update the website docroot to be a checkout of the repo? No. I tried, but there is no git installed on the server. > Maybe we should just automate pulls in fact, so we can edit the site > just by checking in the changes. That would certainly be nice. We change the site so seldom that it might not be worth the trouble, though. But if we want to make it more fancy, you could also use some sort of an include-mechanism to insert the page header and footer, rather than putting them directly into index.html. A static site generator, perhaps. And automatically pull the docs directory from the latest stable branch from the main psqlodbc repository there too. - Heikki
Marc - please see below... On Wed, Apr 24, 2013 at 4:10 PM, Heikki Linnakangas <hlinnakangas@vmware.com> wrote: > On 23.04.2013 18:55, Dave Page wrote: >> >> On Tue, Apr 23, 2013 at 1:51 PM, Heikki Linnakangas >> <hlinnakangas@vmware.com> wrote: >>> >>> On 22.04.2013 16:29, Heikki Linnakangas wrote: >>> There is now a second repository for the website, at >>> http://git.postgresql.org/gitweb/?p=psqlodbc-www.git. It contains the >>> main >>> page and mediat files, the HOWTOs, and the FAQ. I removed those files >>> from >>> the main psqlodbc repository, they are now maintained in the psqlodbc-www >>> repository. >> >> >> Cool. Did you update the website docroot to be a checkout of the repo? > > > No. I tried, but there is no git installed on the server. Marc, can you please install git, wget and curl on the shell server? I don't have root so can't do it myself. >> Maybe we should just automate pulls in fact, so we can edit the site >> just by checking in the changes. > > > That would certainly be nice. We change the site so seldom that it might not > be worth the trouble, though. That's easy enough to do. We do it all over the place. > But if we want to make it more fancy, you > could also use some sort of an include-mechanism to insert the page header > and footer, rather than putting them directly into index.html. A static site > generator, perhaps. And automatically pull the docs directory from the > latest stable branch from the main psqlodbc repository there too. I'm sure that'd be lovely, but I don't have time for it! -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
On 2013-04-24, at 08:18 , Dave Page <dpage@pgadmin.org> wrote: > > Marc, can you please install git, wget and curl on the shell server? I > don't have root so can't do it myself. Working on it, give it <30 and it will all be there and ready for you … Any PHP requirements? there is a very minimilistic (php + pgsql) install right now ...
Thanks Marc. No, I don't have any PHP requirements at present. On Wed, Apr 24, 2013 at 5:19 PM, Marc G. Fournier <scrappy@hub.org> wrote: > > On 2013-04-24, at 08:18 , Dave Page <dpage@pgadmin.org> wrote: > >> >> Marc, can you please install git, wget and curl on the shell server? I >> don't have root so can't do it myself. > > Working on it, give it <30 and it will all be there and ready for you … > > Any PHP requirements? there is a very minimilistic (php + pgsql) install right now ... -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
On Wed, Apr 24, 2013 at 4:18 PM, Dave Page <dpage@pgadmin.org> wrote: > Marc - please see below... > > On Wed, Apr 24, 2013 at 4:10 PM, Heikki Linnakangas > <hlinnakangas@vmware.com> wrote: >> On 23.04.2013 18:55, Dave Page wrote: >>> >>> On Tue, Apr 23, 2013 at 1:51 PM, Heikki Linnakangas >>> <hlinnakangas@vmware.com> wrote: >>>> >>>> On 22.04.2013 16:29, Heikki Linnakangas wrote: >>>> There is now a second repository for the website, at >>>> http://git.postgresql.org/gitweb/?p=psqlodbc-www.git. It contains the >>>> main >>>> page and mediat files, the HOWTOs, and the FAQ. I removed those files >>>> from >>>> the main psqlodbc repository, they are now maintained in the psqlodbc-www >>>> repository. >>> >>> >>> Cool. Did you update the website docroot to be a checkout of the repo? >> >> >> No. I tried, but there is no git installed on the server. > > Marc, can you please install git, wget and curl on the shell server? I > don't have root so can't do it myself. > >>> Maybe we should just automate pulls in fact, so we can edit the site >>> just by checking in the changes. >> >> >> That would certainly be nice. We change the site so seldom that it might not >> be worth the trouble, though. > > That's easy enough to do. We do it all over the place. This should be working now (updating hourly), but can you please delete /home/pgfoundry.org/groups/psqlodbc/htdocs/foo please Heikki? Thanks. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
On 26.04.2013 11:09, Dave Page wrote: > On Wed, Apr 24, 2013 at 4:18 PM, Dave Page<dpage@pgadmin.org> wrote: >> Marc - please see below... >> >> On Wed, Apr 24, 2013 at 4:10 PM, Heikki Linnakangas >> <hlinnakangas@vmware.com> wrote: >>> On 23.04.2013 18:55, Dave Page wrote: >>>> >>>> On Tue, Apr 23, 2013 at 1:51 PM, Heikki Linnakangas >>>> <hlinnakangas@vmware.com> wrote: >>>>> >>>>> On 22.04.2013 16:29, Heikki Linnakangas wrote: >>>>> There is now a second repository for the website, at >>>>> http://git.postgresql.org/gitweb/?p=psqlodbc-www.git. It contains the >>>>> main >>>>> page and mediat files, the HOWTOs, and the FAQ. I removed those files >>>>> from >>>>> the main psqlodbc repository, they are now maintained in the psqlodbc-www >>>>> repository. >>>> >>>> >>>> Cool. Did you update the website docroot to be a checkout of the repo? >>> >>> >>> No. I tried, but there is no git installed on the server. >> >> Marc, can you please install git, wget and curl on the shell server? I >> don't have root so can't do it myself. >> >>>> Maybe we should just automate pulls in fact, so we can edit the site >>>> just by checking in the changes. >>> >>> >>> That would certainly be nice. We change the site so seldom that it might not >>> be worth the trouble, though. >> >> That's easy enough to do. We do it all over the place. > > This should be working now (updating hourly), but can you please > delete /home/pgfoundry.org/groups/psqlodbc/htdocs/foo please Heikki? Oh, where did that come from? Did you rename docs -> foo? Deleted. We'll still need the HTML files from the main psqlodbc repository copied under docs. The link to release notes, for example, doesn't work at the moment. A git submodule, like Alvaro suggested, would probably be the best solution, although there doesn't seem to be any way to check out only one subdirectory in a submodule, so we'd have to checkout the sources too. I guess it wouldn't do any harm, though. For now, though, I just manually copied the docs/*.html files under /home/pgfoundry.org/groups/psqlodbc/htdocs/docs. - Heikki
On 26.04.2013 11:09, Dave Page wrote: > On Wed, Apr 24, 2013 at 4:18 PM, Dave Page<dpage@pgadmin.org> wrote: >> Marc - please see below... >> >> On Wed, Apr 24, 2013 at 4:10 PM, Heikki Linnakangas >> <hlinnakangas@vmware.com> wrote: >>> On 23.04.2013 18:55, Dave Page wrote: >>>> >>>> On Tue, Apr 23, 2013 at 1:51 PM, Heikki Linnakangas >>>> <hlinnakangas@vmware.com> wrote: >>>>> >>>>> On 22.04.2013 16:29, Heikki Linnakangas wrote: >>>>> There is now a second repository for the website, at >>>>> http://git.postgresql.org/gitweb/?p=psqlodbc-www.git. It contains the >>>>> main >>>>> page and mediat files, the HOWTOs, and the FAQ. I removed those files >>>>> from >>>>> the main psqlodbc repository, they are now maintained in the psqlodbc-www >>>>> repository. >>>> >>>> >>>> Cool. Did you update the website docroot to be a checkout of the repo? >>> >>> >>> No. I tried, but there is no git installed on the server. >> >> Marc, can you please install git, wget and curl on the shell server? I >> don't have root so can't do it myself. >> >>>> Maybe we should just automate pulls in fact, so we can edit the site >>>> just by checking in the changes. >>> >>> >>> That would certainly be nice. We change the site so seldom that it might not >>> be worth the trouble, though. >> >> That's easy enough to do. We do it all over the place. > > This should be working now (updating hourly), but can you please > delete /home/pgfoundry.org/groups/psqlodbc/htdocs/foo please Heikki? Oh, where did that come from? Did you rename docs -> foo? Deleted. We'll still need the HTML files from the main psqlodbc repository copied under docs. The link to release notes, for example, doesn't work at the moment. A git submodule, like Alvaro suggested, would probably be the best solution, although there doesn't seem to be any way to check out only one subdirectory in a submodule, so we'd have to checkout the sources too. I guess it wouldn't do any harm, though. For now, though, I just manually copied the docs/*.html files under /home/pgfoundry.org/groups/psqlodbc/htdocs/docs. - Heikki
On Fri, Apr 26, 2013 at 9:26 AM, Heikki Linnakangas <hlinnakangas@vmware.com> wrote: > >> This should be working now (updating hourly), but can you please >> delete /home/pgfoundry.org/groups/psqlodbc/htdocs/foo please Heikki? > > > Oh, where did that come from? Did you rename docs -> foo? Deleted. Yeah, I couldn't delete it. But... it still seems to be there: [dpage@shell /home/pgfoundry.org/groups/psqlodbc/htdocs]$ ls -al total 128 drwxrwsr-x 7 dpage psqlodbc 4096 Apr 25 16:41 . drwxrwsr-x 4 dpage psqlodbc 4096 Dec 30 2005 .. drwxrwsr-x 8 dpage psqlodbc 4096 Apr 26 08:13 .git -rw-rw-r-- 1 dpage psqlodbc 630 Apr 25 16:36 README.txt drwxrwsr-x 2 dpage psqlodbc 4096 Apr 23 12:44 backups drwxrwsr-x 2 dpage psqlodbc 4096 Apr 26 08:26 docs -rw-rw-r-- 1 dpage psqlodbc 35699 Apr 25 16:36 faq.html drwxr-sr-x 2 hlinnaka psqlodbc 4096 Apr 23 15:57 foo -rw-rw-r-- 1 dpage psqlodbc 2350 Apr 25 16:36 howto-accesslo.html -rw-rw-r-- 1 dpage psqlodbc 6215 Apr 25 16:36 howto-accessvba.html -rw-rw-r-- 1 dpage psqlodbc 1710 Apr 25 16:36 howto-bo.html -rw-rw-r-- 1 dpage psqlodbc 3995 Apr 25 16:36 howto-ch.html -rw-rw-r-- 1 dpage psqlodbc 4910 Apr 25 16:36 howto-csharp.html -rw-rw-r-- 1 dpage psqlodbc 3372 Apr 25 16:36 howto-vb.html -rw-rw-r-- 1 dpage psqlodbc 8374 Apr 25 16:36 howto-vblo.html -rw-rw-r-- 1 dpage psqlodbc 9702 Apr 25 16:36 index.html drwxrwsr-x 4 dpage psqlodbc 4096 Apr 22 10:55 media > We'll still need the HTML files from the main psqlodbc repository copied > under docs. The link to release notes, for example, doesn't work at the > moment. A git submodule, like Alvaro suggested, would probably be the best > solution, although there doesn't seem to be any way to check out only one > subdirectory in a submodule, so we'd have to checkout the sources too. I > guess it wouldn't do any harm, though. > > For now, though, I just manually copied the docs/*.html files under > /home/pgfoundry.org/groups/psqlodbc/htdocs/docs. OK. Unfortunately I can't do anything with those as I don't have permissions on them. If you can make /home/pgfoundry.org/groups/psqlodbc/htdocs/docs an appropriate git checkout, and ensure group write permissions are given, you should then be able to edit /home/pgfoundry.org/groups/psqlodbc/update-website.sh to ensure it gets updated along with the rest of the website. Thanks. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company