Обсуждение: Postgres Wiki
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 For better or worse, the Postgres Wiki is now up and running: http://wiki.postgresql.org It's running Postgres on the backend, but was originally designed to run Mysql, so let me know if you notice any problems. - -- Greg Sabino Mullane greg@turnstep.com End Point Corporation PGP Key: 0x14964AC8 200608150812 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFE4bpevJuQZxSWSsgRAl3FAKD+LezHtw0RmeCOepFXKIi/jvIx8wCdEXF/ vtX3yColTzt5gKrW9dvE84w= =TE4k -----END PGP SIGNATURE-----
Hello, On Tue, 2006-08-15 at 12:15 +0000, Greg Sabino Mullane wrote: > > For better or worse, the Postgres Wiki is now up and running: > > http://wiki.postgresql.org Great! I pushed RPM Installation article there. I'll report you if I experience problems. I believe that wiki will help us a lot for writing docs. Regards, -- The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564 PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/
Вложения
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > However, what's the rationale for putting this up on svr1? I would > consider that one our most critical server, considering it runs the cvs > repository. I would rather see the number of services on such an > important machine *decrease* than increase. If you need "internal > examples", we've already seen with the old svr2/wwwmaster box how messy > things can get with a large mix of services -and how easy it is to end > up with things with security issues in there. I think Marc was just the one willing to do the work to get something up and going, and that's how it ended up there. That being said, the company I work for would be more than willing to host this as well (we already run other MediaWiki instances) if we want to move it off of there. - -- Greg Sabino Mullane greg@turnstep.com End Point Corporation PGP Key: 0x14964AC8 200608151113 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFE4eS6vJuQZxSWSsgRAiuPAJ9xW81mBw5O8nIgLk+1ITRfd3GnygCeN+44 enEwkQyrWvKBYKV8K6Q1GKg= =XOGw -----END PGP SIGNATURE-----
> > For better or worse, the Postgres Wiki is now up and running: > > > > http://wiki.postgresql.org > > Great! I pushed RPM Installation article there. I'll report > you if I experience problems. > > I believe that wiki will help us a lot for writing docs. Just took a quick look at this one. Ignore for a moment the fact that I don't like Wikis in general - I'm definitly not going to argue not to have one for developers :-) Let's leave that part behind.. However, what's the rationale for putting this up on svr1? I would consider that one our most critical server, considering it runs the cvs repository. I would rather see the number of services on such an important machine *decrease* than increase. If you need "internal examples", we've already seen with the old svr2/wwwmaster box how messy things can get with a large mix of services -and how easy it is to end up with things with security issues in there. //Magnus
-----Original Message----- From: "Magnus Hagander" <mha@sollentuna.net> To: "Devrim GUNDUZ" <devrim@commandprompt.com>; "Greg Sabino Mullane" <greg@turnstep.com> Cc: "pgsql-www@postgresql.org" <pgsql-www@postgresql.org> Sent: 15/08/06 16:32 Subject: Re: [pgsql-www] Postgres Wiki > However, what's the rationale for putting this up on svr1? Because it was supposed to be on the root of the developer.postgresql.org vhost as a strictly developer only resource. /D
Eh? This was supposed to be on developer.postgresql.org /D -----Original Message----- From: "Greg Sabino Mullane" <greg@turnstep.com> To: "pgsql-www@postgresql.org" <pgsql-www@postgresql.org> Sent: 15/08/06 13:14 Subject: [pgsql-www] Postgres Wiki -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 For better or worse, the Postgres Wiki is now up and running: http://wiki.postgresql.org It's running Postgres on the backend, but was originally designed to run Mysql, so let me know if you notice any problems. - -- Greg Sabino Mullane greg@turnstep.com End Point Corporation PGP Key: 0x14964AC8 200608150812 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFE4bpevJuQZxSWSsgRAl3FAKD+LezHtw0RmeCOepFXKIi/jvIx8wCdEXF/ vtX3yColTzt5gKrW9dvE84w= =TE4k -----END PGP SIGNATURE----- ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
Greg Sabino Mullane wrote: > For better or worse, the Postgres Wiki is now up and running: > > http://wiki.postgresql.org Perhaps the URL could be beautified a little bit. Currently, http://wiki.postgresql.org/index.php/Main_Page Looking at Wikipedia and taking into account Dave's comment, it might better be http://developer.postgresql.org/wiki/Main_Page A little web server reconfiguration can probably do that. -- Peter Eisentraut http://developer.postgresql.org/~petere/
On Tue, 15 Aug 2006, Magnus Hagander wrote: > However, what's the rationale for putting this up on svr1? I would > consider that one our most critical server, considering it runs the cvs > repository. I would rather see the number of services on such an > important machine *decrease* than increase. If you need "internal > examples", we've already seen with the old svr2/wwwmaster box how messy > things can get with a large mix of services -and how easy it is to end > up with things with security issues in there. This was discussed when we first discussed setting up a wiki ... since it was meant to be a 'developers' wiki, not general users, it was felt that it was appropriate to stay with the developers vServer ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664
On 15/8/06 15:56, "Devrim GUNDUZ" <devrim@commandprompt.com> wrote: > Hello, > > On Tue, 2006-08-15 at 12:15 +0000, Greg Sabino Mullane wrote: >> >> For better or worse, the Postgres Wiki is now up and running: >> >> http://wiki.postgresql.org > > Great! I pushed RPM Installation article there. I'll report you if I > experience problems. Please remove these items, The whole point of this wiki was to be used a whiteboard for *developers* to hash out plans for development work and code. It was definitely *not* supposed to be for end user documentation, which should be on the techdocs area of the main site. This also means of course that write access to the wiki should be controlled and restricted to developers. Who will be doing that? Regards, Dave.
On 15/8/06 22:26, "mdean" <mdean@xn1.com> wrote: > Dave Page wrote: > > wow, i thought the whole idea of a wiki was that you didn't moderate or > restrict. The whole point of this one was to act as a developers resource and specifically not as a user resource. If you have a better idea to stop it being used by users then I'm all ears, but I don't see how the original designers of the Wiki concept should determine how we see fit to use one for our purposes. Regards, Dave.