This is something that makes total sense. I do it all the time. Since
you are good with PHP, use it in command line to automate things
instead of struggling with Bash (which is not difficult but takes time
to learn the ins and outs) or other languages.

Pablo

On Thu, Jul 9, 2009 at 1:22 PM, Jonathan Wage<jonw...@gmail.com> wrote:
> You can write the scripts in PHP then instead of Ruby.
>
> - Jon
>
> On Thu, Jul 9, 2009 at 12:18 PM, Rene <r...@pc-dummy.net> wrote:
>>
>> For me it's very important, to automate that task so a user can run the
>> complete upgrade without the need of my help.
>>
>> The upgrade process should run on a unix (Mac/BSD/Linux) box, without
>> the requirement of ruby.
>>
>> But using patches as you described, is something i have to implement.
>>
>> Also i agree to not depend on the sf framwork for updates, if something
>> goes wrong the updater also isn't able to run anymore.
>>
>> Thank your for your descriptions,
>>
>> Rene Jochum
>>
>>
>>
>> Jonathan Wage schrieb:
>> > They are just ruby scripts :) You just write ruby code essentially to
>> > automate some commands in to a script that can be invoked easily across
>> > lots of machines.
>> >
>> > Honestly, the deployment of something is not the job of symfony. The way
>> > to do this has existed for a long time, outside of symfony. I would
>> > recommend using some existing best practice for deployment like the svn
>> > diff/patch and capistrano approach.
>> >
>> > - Jon
>> >
>> > On Thu, Jul 9, 2009 at 12:02 PM, Eno <symb...@gmail.com
>> > <mailto:symb...@gmail.com>> wrote:
>> >
>> >
>> >     On Thu, 9 Jul 2009, Jonathan Wage wrote:
>> >
>> >     > Now the above commands are all done manually but a lot of times I
>> >     just have
>> >     > simple capistrano scripts that do all this the same each time with
>> > one
>> >     > command and a set of arguments.
>> >
>> >     I spent some time playing with Capistrano a long time ago but the
>> >     documentation is pretty sparse and I never finished building a
>> > proper
>> >     solution. Could you shared some recipes? Also, I thought all work on
>> >     Capistrano had stopped?
>> >
>> >     The other options seem to be to write some symfont tasks and/or use
>> >     pake/phing. Anyone have experience with that?
>> >
>> >     I have to say, deployment is one area where symfony is rather weak -
>> > we
>> >     have a large site with multiple domains, running on multiple
>> > clusters
>> >     of www, image and other servers, with load balancers in front of
>> > public
>> >     servers. So I need to come up with several different deployment
>> >     tasks for
>> >     different kinds of servers.
>> >
>> >
>> >
>> >     --
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > --
>> > Jonathan H. Wage (+1 415 992 5468)
>> > Open Source Software Developer & Evangelist
>> > sensiolabs.com <http://sensiolabs.com> | jwage.com <http://jwage.com> |
>> > doctrine-project.org <http://doctrine-project.org> | symfony-project.org
>> > <http://symfony-project.org>
>> >
>> > You can contact Jonathan about Doctrine, Symfony and Open-Source or for
>> > training, consulting, application development, or business related
>> > questions at jonathan.w...@sensio.com <mailto:jonathan.w...@sensio.com>
>> >
>> > >
>>
>>
>>
>
>
>
> --
> Jonathan H. Wage (+1 415 992 5468)
> Open Source Software Developer & Evangelist
> sensiolabs.com | jwage.com | doctrine-project.org | symfony-project.org
>
> You can contact Jonathan about Doctrine, Symfony and Open-Source or for
> training, consulting, application development, or business related questions
> at jonathan.w...@sensio.com
>
> >
>



-- 
Pablo Godel
ServerGrove Networks
http://servergrove.com/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to 
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/symfony-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to