Обсуждение: Re: [pgsql-advocacy] Setting up for Press Contacts inSE Asia
> > We don't want end-users running *anything* on wwwmaster. This is the reason > > we made it it's own VM. We do *not* want the mess of svr1 all over again. > > Unless I missed something (which is possible, I haven't really been > paying attention), we're talking about Josh having access to the > 186_www database in lieu of an admin interface to... No, we're talking about a separate db I think. At least that's where we started. > hmm, OK - what is > he trying to do exactly? At least part of this thread doesn't seem to > be on the archives site or my own mail folder :-( AFAIK a simple replacement for his having the db on his own box - to make it easier to share the work. > In any case, I don't consider Josh to be an end user, nor do I have Just to be clear, I consider myself (and you) end users in this case. > any problem giving him a shell account on wwwmaster to do work which > sounds like it's comparable to one of us loading the latest version of > the docs. I'm pretty confident we can train him not to use the account > for any other purpose! I'd certainly much rather do that than have > random IPs granted direct access to the DB. It shouldn't be random, of course. And it required software to be installed and maintained that's not there now. I'd rathersee that on svr1. /Magnus
On Jan 29, 2008 1:09 PM, Magnus Hagander <magnus@hagander.net> wrote: > > > any problem giving him a shell account on wwwmaster to do work which > > sounds like it's comparable to one of us loading the latest version of > > the docs. I'm pretty confident we can train him not to use the account > > for any other purpose! I'd certainly much rather do that than have > > random IPs granted direct access to the DB. > > It shouldn't be random, of course. And it required software to be installed and maintained that's not there now. I'd rathersee that on svr1. Right - but that detail is buried in the messages I can't find. Please recap on what exactly Josh is trying to do. /D
Dave, > Right - but that detail is buried in the messages I can't find. Please > recap on what exactly Josh is trying to do. Right now I have a private database on one of my machines, which does 2 things: 1) Track and generate the Regional Contacts page; 2) Track all North America press contacts and spam them It's really a bad idea to have this only on one of my machines, which is on the end of a DSL line and has a previous history of power supply issues. For one thing, it keeps me from meaningfully training Robert or Magnus or you from being able to take over for me if food poisoning brings me down. -- Josh Berkus PostgreSQL @ Sun San Francisco
On Jan 29, 2008 3:41 PM, Josh Berkus <josh@agliodbs.com> wrote: > Dave, > > > Right - but that detail is buried in the messages I can't find. Please > > recap on what exactly Josh is trying to do. > > Right now I have a private database on one of my machines, which does 2 > things: > > 1) Track and generate the Regional Contacts page; > 2) Track all North America press contacts and spam them > > It's really a bad idea to have this only on one of my machines, which is on > the end of a DSL line and has a previous history of power supply issues. For > one thing, it keeps me from meaningfully training Robert or Magnus or you > from being able to take over for me if food poisoning brings me down. OK, that makes a lot more sense (btw, we need to look at these lists again - apparently I'm not the only one missing parts of this thread, though not necessarily the same parts as others :-o ). It seems to me there is a legitimate reason to keep the data on the wwwmaster database (and to create some proper PHP scripts for admin and the RC page in the future), and for you to have a shell account to manage it in the meantime via ssh/ssh tunnel. The spam scripts can most definitely stay on svr1, and the temporary script to generate the RC page can be run on Yridian (when it's ready or elsewhere in the meantime. Alternatively, the RC page can be manually updated. I'd still rather not have direct access to the database server. /D
On Tue, Jan 29, 2008 at 03:51:27PM +0000, Dave Page wrote: > On Jan 29, 2008 3:41 PM, Josh Berkus <josh@agliodbs.com> wrote: > > Dave, > > > > > Right - but that detail is buried in the messages I can't find. Please > > > recap on what exactly Josh is trying to do. > > > > Right now I have a private database on one of my machines, which does 2 > > things: > > > > 1) Track and generate the Regional Contacts page; > > 2) Track all North America press contacts and spam them > > > > It's really a bad idea to have this only on one of my machines, which is on > > the end of a DSL line and has a previous history of power supply issues. For > > one thing, it keeps me from meaningfully training Robert or Magnus or you > > from being able to take over for me if food poisoning brings me down. > > OK, that makes a lot more sense (btw, we need to look at these lists > again - apparently I'm not the only one missing parts of this thread, > though not necessarily the same parts as others :-o ). > > It seems to me there is a legitimate reason to keep the data on the > wwwmaster database (and to create some proper PHP scripts for admin > and the RC page in the future), and for you to have a shell account to > manage it in the meantime via ssh/ssh tunnel. The spam scripts can > most definitely stay on svr1, and the temporary script to generate the > RC page can be run on Yridian (when it's ready or elsewhere in the > meantime. Alternatively, the RC page can be manually updated. > > I'd still rather not have direct access to the database server. If you're keeping the scripts on svr1, you open for svr1 (which I think is already open, but that's a different question). No need for a shell account on the db server for that... Are we talking about the RC contact on the website? If that's it, then it's pobably just as easy to have the website generate the stuff directly, as to create a temp script on a different box to generate something to be manually committed to the page. Josh - is it simple enough that you can in 5 bullet points or so outline what the requiremetns would be to integrate the whole thing (minus the spam part) into the website? //Magnus
> I'd still rather not have direct access to the database server. And I'd prefer SSH myself, so that I can log in from anywhere. Keep in mind that I'll be doing a lot of releases *at* conferences, etc., so doing this via psql-over-SSL would mean relaying through my office machine. Which would really suck if I had a power outage or DSL down back home ... which is why we're doing this in the first place, no? -- Josh Berkus PostgreSQL @ Sun San Francisco