Prev: upload directly into a resource?
Next: In need of CVS/SVN checkout script for Production servers[solved]
From: "Daevid Vincent" on 4 May 2010 16:10
> -----Original Message-----
> From: Daevid Vincent [mailto:daevid(a)daevid.com]
> Sent: Thursday, April 29, 2010 12:33 PM
> To: php-general(a)lists.php.net
> Subject: [PHP] In need of CVS/SVN checkout script for
> Production servers
>
> Semi-off-topic, but I'm pretty sure you all are faced with this same
> challenge, I figured it's worth a shot and maybe some flaming.
>
> I'm looking for a script (bash or php) that I would run on my
> production
> web server that would do this or close to it:
>
> 1. do a CVS/SVN checkout to a new timestamped directory
> 2. change the symlink from the old directory
> 3. change permissions to www-data:www-data on new directory
> 4. and possibly tarball up the old directory.
>
> I'm assuming this is a fairly common task, and I actually wrote one of
> these at my previous job, but I can't find the script
> anymore. I remember
> it's not quite as trivial as it sounds and took a few hours
> to perfect, so
> I thought I'd try to save myself some time. :)
>
> I have some other useful SVN scripts here if anyone is interested:
> http://daevid.com/content/examples/snippets.php

Well, here is the one I'm using. I ended up just writing one (again!)

http://www.daevid.com/content/examples/snippets.php :: "Production
Deployment Script"

From: Michiel Sikma on 5 May 2010 17:55
On 5 May 2010 17:18, tedd <tedd.sperling(a)gmail.com> wrote:

> At 1:10 PM -0700 5/4/10, Daevid Vincent wrote:
>
>> Well, here is the one I'm using. I ended up just writing one (again!)
>>
>> http://www.daevid.com/content/examples/snippets.php :: "Production
>> Deployment Script"
>>
>
> What?!?
>
> Advanced features??
> -snip-
>


Just want to add my +1 to this. I'm running Safari, which most definitely
will support whatever advanced features you put in there, and I'm being
blocked. Putting aside the level of standards compliance of your site, you
really should blacklist browsers instead of whitelisting them. Sites should
never become inaccessible if your browser lacks features, and even if the
entire site revolves around some fancy Javascript, you should at least
provide a "go ahead at your own risk" link in case you're accidentally
shutting out the wrong browser.

Here's an example from a site I made a while ago which mimics the workings
of Gmail. It's accessible to screen readers through alternative content, and
if you're trying to visit using IE6 (we consciously decided not to apply
browser fixes for it), you get the following message:

http://wedemandhtml.com/tmp/tag_ie6_is_unsupported.png

Michiel
From: David Otton on 6 May 2010 05:06
On 6 May 2010 04:14, Adam Richardson <simpleshot(a)gmail.com> wrote:

> Daevid asked the list for a an app that facilitated SVN/CVS, and when nobody
> provided options, he crafted a solution of his own and then offered it back
> to the list.

Er... I suggested Phing. Phing/Ant/Gradle/Maven/Capistrano... a build
tool is the standard solution here, and there are about a million of
them (http://en.wikipedia.org/wiki/List_of_build_automation_software).
I can't believe people are seriously discussing rolling your own when
all those mature tools are sitting right there.

Did my post not get through or something?
 | 
Pages: 1
Prev: upload directly into a resource?
Next: In need of CVS/SVN checkout script for Production servers[solved]