Re: Audio & Video? - Mailing list pgsql-www
From | Guido Barosio |
---|---|
Subject | Re: Audio & Video? |
Date | |
Msg-id | f7f6b4c70902111607q55b33b5bwdd7d076cb1ce84be@mail.gmail.com Whole thread Raw |
In response to | Re: Audio & Video? ("Gavin M. Roy" <gmr@ehpg.net>) |
List | pgsql-www |
IMHO if this comes from *PUG, then that *PUG should take the call and sort this out with their resources. After that, a ping to -advocacy and maybe -www in order to let the community know that things are in place. /* capacity planning */ Otherwise: - we are facing a big amount of media heading *.postgresql.org sooner or later. - postgresql.org resources will be assigned to keep this. /* sysadmins running against nagios complaining about space, for instance */ I do support and appreciate Josh's work, in fact the idea and effort rock. But I am a bit concerned on how to handle future situations. If this grows we are gonna face a big problem. One single meeting created 100mb. How many meetings / events / talks are we planning to store? I do have the BsAs December talks still in HD, ~ 1gb of media. Another point of view could be the fact that "spreading the bytes" helps the project advocacy because of the single fact that more sites contain postgresql content. 2 cents and nothing more than that, please feel free to tag this as a stupid mail. gb.- On Wed, Feb 11, 2009 at 9:33 PM, Gavin M. Roy <gmr@ehpg.net> wrote: > I'd agree that this probably doesn't belong in the Wiki or the main www > tree. Perhaps a simple host: media.postgresql.org would suffice, with a > plain html index template that Josh can edit as he adds items and the > ability to serve the content. > If setting up a jail and such for this is a pain right now, I could setup a > vhost on my shared hosting box for the time being and setup a generic > template for you to edit, Josh. > Gavin > > On Wed, Feb 11, 2009 at 5:02 PM, Alvaro Herrera <alvherre@commandprompt.com> > wrote: >> >> Stefan Kaltenbrunner wrote: >> > Tom Lane wrote: >> >> >> It's probably fair to discuss what is a reasonable space budget for >> >> audio/video stuff, and maybe to try to prevent it from being mirrored >> >> if the sysadmins think that would be a good idea. But this doesn't >> >> strike me as being too large for the servers we've got. >> > >> > we have more than enough resources to host stuff like this - the wiki >> > allows uploads of content of up to 100MB per object (it used to display >> > a warning for stuff that was larger than 150kb but I just disabled >> > that). >> >> I think the Wiki is not a good place for storing such things. It barely >> knows that binary files are "images" >> >> -- >> Sent via pgsql-www mailing list (pgsql-www@postgresql.org) >> To make changes to your subscription: >> http://www.postgresql.org/mailpref/pgsql-www > >