[Clipart] I hope you have backups.

Bassel Safadi bassel.safadi at gmail.com
Sat Feb 5 10:46:09 PST 2011

Agree, but still good to have a playground for ppl to test, nothing that
might crash the server can happen from aiki panel, but for learning will be
On Feb 5, 2011 7:51 PM, "chovynz" <chovynz at gmail.com> wrote:
> I don't think you can do any worse that what happened yesterday. :)
> For the most part, I'd suggest you relax about not comfortable about
> on a live site. That's one of the reasons why I put the "chovynz is
> working!" sign up, to make people aware that weird things could happen.
> I do understand the thinking though, which is why it's taken me this long
> get to where I am with coding OCAL. However, now that I've done editing ON
> the live site for awhile, I now think that a test site is a waste of time.
> mean we already had a BETA site with so much more features and fixed bugs
> it, then when this one came through I was disappointed to see most of the
> changes was lost.
> You have good thoughts, though. All I'm doing is commenting on the idea.
> against having a test site, and just want other devs to just jump in on
> live site. If my opinion weighs anything, my vote is against, but i don't
> want the discussion to stop. Ultimately the choice is Jon's/server owners.
> Convince him either way.
> On Sun, Feb 6, 2011 at 5:54 AM, J. Alves <alvesjmp at gmail.com> wrote:
>> By the way, I was wondering about that these days. Maybe this has been
>> discussed before and I missed it, in which case I apologize for the
>> repetition... Just let me know and I return to under me bridge. :-)
>> I am thinking of trying to learn Aiki, php and all that to be able to
>> help with the code side of things. But I would never feel comfortable
>> touching the live site even after I'm fluent in those technologies,
>> let alone during the learning process, so I was hoping there was a
>> parallel code or site for this type of activity. You know, a sort of
>> private mirror of OpenClipart's code (not necessary to have the full
>> database, although that would be nice too) where people would develop
>> and tweak without worry that the main site was getting screwed up (as
>> its looks were when I looked 5 min ago, for example). Then, when we
>> were confident that the modifications are working and nothing is
>> getting damaged in the DB by our actions, then it would be time to
>> patch the old code with the new stuff. That's what I do with my little
>> web apps that are not important and don't have any traffic beyond two
>> or three labs and not 1,000s of visitors a day like OCAL. Is anything
>> like that in place for OCAL? I suspect not. The next best alternative
>> of having a working development branch of the site would be to give
>> people the full code for installing at their home server so they can
>> work on it there (is that available? I'd like that). Then they would
>> send the modifications either to the main site or to a (few) central
>> person(s) who'd integrate the code with the live site every once in a
>> while.
>> Imagine for example if I try to solve the tags problem or try to
>> implement the "idea mill" I registered in the blueprints (is that the
>> place for ideas of new features?) or whatever, and in the process ALL
>> tags for ALL cliparts get mangled to something unexpected and useless.
>> That would be a huge disaster and I'd have to hide from librarians for
>> the rest of my life. :-) OK, I suppose there are backups, but still a
>> pain in the proverbial.
>> Cheers
>> J
>> On Sat, Feb 5, 2011 at 6:02 AM, Bassel Safadi <bassel.safadi at gmail.com>
>> wrote:
>> > it seems a server side problem, I emailed osuosl about, hope to get it
>> back
>> > soon
>> >
>> > On Sat, Feb 5, 2011 at 5:43 AM, chovynz <chovynz at gmail.com> wrote:
>> >>
>> >> To Jon or Bassel
>> >>
>> >> I hope you have backups.
>> >> I'm tired of the interlinked problems.
>> >>
>> >> The only thing I did was change one value in the css.
>> >> div.r-img-i {width:110px;}
>> >> to
>> >> div.r-img-i {width:100px;}
>> >>
>> >> And the whole site crashed. This after successfully already unwinding
>> much
>> >> of the css spagehtti code. Fucking stupid.
>> >> Now, I can't login to admin, and no-one can see the site. Nothing I
>> do
>> >> from my end. Someone with ssh access is going to have to fix whatever
>> went
>> >> wrong.
>> >>
>> >> I was editing the "main" widget css at the time. I hope you've got a
>> >> file of what happened, because I'm sure I did nothing that would cause
>> this,
>> >> since I was only playing with the layouts of the cliparts that were
>> >> displayed on the main page to get them to fit better. If i did do
>> something,
>> >> then I need to know what it was, so that I can avoid that in the
>> >>
>> >> I'm going to take a break. sheesh.
>> >>
>> >> --
>> >> Cheers
>> >> Chovynz
>> >
>> >
>> >
>> > --
>> > Bassel Safadi
>> > http://bassel.ws
>> > http://aikilab.org
>> > Global +1 323-545-3855
>> > Singapore +65 93488349
>> >
>> >
>> > _______________________________________________
>> > clipart mailing list
>> > clipart at lists.freedesktop.org
>> > http://lists.freedesktop.org/mailman/listinfo/clipart
>> >
>> >
>> --
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> João Marcelo Pereira Alves (J) - Genomics, Molecular Phylogeny and
>> Evolution
>> Dept. Microbiology & Immunology - MCV/VCU - Richmond, VA, USA
>> f. 1-804-828-3897 / 804-852-1234 - http://bioinfo.lpb.mic.vcu.edu
> --
> Cheers
> Chovynz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/clipart/attachments/20110205/87a261e0/attachment.html>

More information about the clipart mailing list