Re: RFC: cake deploy
> you plan on deploying the actual app that you're in , or using a svn > checkout at the remote machine (when using ssh) ? It would be great if it's SCM agnostic or if support for different SCMs could be plugged in (@Chris: I can make it support git :P ). - Dardo Sordi. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: RFC: cake deploy
generating index.php/test.php file for advanced layout etc ? On Sat, May 17, 2008 at 1:16 AM, francky06l <[EMAIL PROTECTED]> wrote: > > Ability to switch to different cake version .. I use to have a "latest > svn", a kind of "qa" and a "production one" .. > Tmp clean is also essential as well maybe as database choice..and > debug mode. > > On May 16, 10:23 pm, "b logica" <[EMAIL PROTECTED]> wrote: >> On Fri, May 16, 2008 at 1:52 PM, Marcin Domanski <[EMAIL PROTECTED]> wrote: >> >> > you hijacker! >> >> I don't know that this is the best place for this question but it's >> >> ~somewhat~ related. I'm looking for people's thoughts on extending >> >> cake's i18n extract so that one can update existing .po files. Use >> >> case: Extraction has taken place and a copy made for each locale and >> >> sent off to the translator. Later, after they've been returned and >> >> installed, a further extract call writes any new msgids to each >> >> locale's .po file rather than (or, maybe including) a generic .pot >> >> file. The .po files would also be backed up, of course. This would >> >> make it much easier to update the files with new strings. >> >> > poedit - update catalog from pot file >> >> Thanks for the clue. I did think of poedit, but it hadn't occurred to >> me that it would only update the files with those msgids that don't >> already exist. Of course, it seems obvious now. I'll give that a go. > > > -- Marcin Domanski http://kabturek.info --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: RFC: cake deploy
Ability to switch to different cake version .. I use to have a "latest svn", a kind of "qa" and a "production one" .. Tmp clean is also essential as well maybe as database choice..and debug mode. On May 16, 10:23 pm, "b logica" <[EMAIL PROTECTED]> wrote: > On Fri, May 16, 2008 at 1:52 PM, Marcin Domanski <[EMAIL PROTECTED]> wrote: > > > you hijacker! > >> I don't know that this is the best place for this question but it's > >> ~somewhat~ related. I'm looking for people's thoughts on extending > >> cake's i18n extract so that one can update existing .po files. Use > >> case: Extraction has taken place and a copy made for each locale and > >> sent off to the translator. Later, after they've been returned and > >> installed, a further extract call writes any new msgids to each > >> locale's .po file rather than (or, maybe including) a generic .pot > >> file. The .po files would also be backed up, of course. This would > >> make it much easier to update the files with new strings. > > > poedit - update catalog from pot file > > Thanks for the clue. I did think of poedit, but it hadn't occurred to > me that it would only update the files with those msgids that don't > already exist. Of course, it seems obvious now. I'll give that a go. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: RFC: cake deploy
On Fri, May 16, 2008 at 1:52 PM, Marcin Domanski <[EMAIL PROTECTED]> wrote: > > you hijacker! >> I don't know that this is the best place for this question but it's >> ~somewhat~ related. I'm looking for people's thoughts on extending >> cake's i18n extract so that one can update existing .po files. Use >> case: Extraction has taken place and a copy made for each locale and >> sent off to the translator. Later, after they've been returned and >> installed, a further extract call writes any new msgids to each >> locale's .po file rather than (or, maybe including) a generic .pot >> file. The .po files would also be backed up, of course. This would >> make it much easier to update the files with new strings. > > poedit - update catalog from pot file > Thanks for the clue. I did think of poedit, but it hadn't occurred to me that it would only update the files with those msgids that don't already exist. Of course, it seems obvious now. I'll give that a go. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: RFC: cake deploy
Hey, some basic toughts: the ability to save/not save paswords different configs (dev/live etc) clearing tmp, chmoding some possibility to plug into the whole process and add your own commands etc you plan on deploying the actual app that you're in , or using a svn checkout at the remote machine (when using ssh) ? On Fri, May 16, 2008 at 6:09 PM, Chris Hartjes <[EMAIL PROTECTED]> wrote: > > Hi kids. > I'm starting to get my notes together for creating a 'cake deploy' > task, since I have become rather involved in application deployment as > of late. > > In my mind right now I have two options: > > 'cake deploy config' > - configure what options will be used for the deployment > > I envision you choosing between ssh and ftp, usernames and passwords, > servers, source and destination. That info will be stored in a file > in APP/config. > > 'cake deploy' > - pretty self explanatory > > Anyway, I would appreciate people's thoughts and comments on what they > would like to see as part of 'cake deploy'. Please keep in mind that > I am under no obligation to accept any of your ideas. :) > > -- > Chris Hartjes > Internet Loudmouth > Motto for 2008: "Moving from herding elephants to handling snakes..." > @TheKeyBoard: http://www.littlehart.net/atthekeyboard > > > > -- Marcin Domanski http://kabturek.info --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: RFC: cake deploy
you hijacker! > I don't know that this is the best place for this question but it's > ~somewhat~ related. I'm looking for people's thoughts on extending > cake's i18n extract so that one can update existing .po files. Use > case: Extraction has taken place and a copy made for each locale and > sent off to the translator. Later, after they've been returned and > installed, a further extract call writes any new msgids to each > locale's .po file rather than (or, maybe including) a generic .pot > file. The .po files would also be backed up, of course. This would > make it much easier to update the files with new strings. poedit - update catalog from pot file -- Marcin Domanski http://kabturek.info --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: RFC: cake deploy
One thing that would be nice to see is an option to clear out the tmp subfolders (like caches/model, caches/view ...) and likely making sure the perms are still good on that directory. I know that is something when I was starting out that kept biting me in the butt. Sam D On Fri, May 16, 2008 at 9:36 AM, b logica <[EMAIL PROTECTED]> wrote: > > rsync --rsh might be nice to have as well. Also, the debug & error > logs should be nulled. Oh, and permissions on the files & tmp > directories might be a nice option--rather than opening them up with > 777 I prefer to chgrp apache for them. I'm not sure how that would be > best configured for deployment. Maybe that's best left for tidying up > later. > > I don't know that this is the best place for this question but it's > ~somewhat~ related. I'm looking for people's thoughts on extending > cake's i18n extract so that one can update existing .po files. Use > case: Extraction has taken place and a copy made for each locale and > sent off to the translator. Later, after they've been returned and > installed, a further extract call writes any new msgids to each > locale's .po file rather than (or, maybe including) a generic .pot > file. The .po files would also be backed up, of course. This would > make it much easier to update the files with new strings. > > Of course, if this is already possible with Cake, please point that > out to me :-\ > > On Fri, May 16, 2008 at 12:09 PM, Chris Hartjes <[EMAIL PROTECTED]> wrote: >> >> Hi kids. >> >> I'm starting to get my notes together for creating a 'cake deploy' >> task, since I have become rather involved in application deployment as >> of late. >> >> In my mind right now I have two options: >> >> 'cake deploy config' >> - configure what options will be used for the deployment >> >> I envision you choosing between ssh and ftp, usernames and passwords, >> servers, source and destination. That info will be stored in a file >> in APP/config. >> >> 'cake deploy' >> - pretty self explanatory >> >> Anyway, I would appreciate people's thoughts and comments on what they >> would like to see as part of 'cake deploy'. Please keep in mind that >> I am under no obligation to accept any of your ideas. :) >> >> -- >> Chris Hartjes >> Internet Loudmouth >> Motto for 2008: "Moving from herding elephants to handling snakes..." >> @TheKeyBoard: http://www.littlehart.net/atthekeyboard >> >> > >> > > > > -- -- (the old fart) the advice is free, the lack of crankiness will cost you - its a fine line between a real question and an idiot http://blog.samdevore.com/archives/2007/03/05/when-open-source-bugs-me/ http://blog.samdevore.com/cakephp-pages/my-cake-wont-bake/ http://blog.samdevore.com/cakephp-pages/i-cant-bake/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: RFC: cake deploy
rsync --rsh might be nice to have as well. Also, the debug & error logs should be nulled. Oh, and permissions on the files & tmp directories might be a nice option--rather than opening them up with 777 I prefer to chgrp apache for them. I'm not sure how that would be best configured for deployment. Maybe that's best left for tidying up later. I don't know that this is the best place for this question but it's ~somewhat~ related. I'm looking for people's thoughts on extending cake's i18n extract so that one can update existing .po files. Use case: Extraction has taken place and a copy made for each locale and sent off to the translator. Later, after they've been returned and installed, a further extract call writes any new msgids to each locale's .po file rather than (or, maybe including) a generic .pot file. The .po files would also be backed up, of course. This would make it much easier to update the files with new strings. Of course, if this is already possible with Cake, please point that out to me :-\ On Fri, May 16, 2008 at 12:09 PM, Chris Hartjes <[EMAIL PROTECTED]> wrote: > > Hi kids. > > I'm starting to get my notes together for creating a 'cake deploy' > task, since I have become rather involved in application deployment as > of late. > > In my mind right now I have two options: > > 'cake deploy config' > - configure what options will be used for the deployment > > I envision you choosing between ssh and ftp, usernames and passwords, > servers, source and destination. That info will be stored in a file > in APP/config. > > 'cake deploy' > - pretty self explanatory > > Anyway, I would appreciate people's thoughts and comments on what they > would like to see as part of 'cake deploy'. Please keep in mind that > I am under no obligation to accept any of your ideas. :) > > -- > Chris Hartjes > Internet Loudmouth > Motto for 2008: "Moving from herding elephants to handling snakes..." > @TheKeyBoard: http://www.littlehart.net/atthekeyboard > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
RFC: cake deploy
Hi kids. I'm starting to get my notes together for creating a 'cake deploy' task, since I have become rather involved in application deployment as of late. In my mind right now I have two options: 'cake deploy config' - configure what options will be used for the deployment I envision you choosing between ssh and ftp, usernames and passwords, servers, source and destination. That info will be stored in a file in APP/config. 'cake deploy' - pretty self explanatory Anyway, I would appreciate people's thoughts and comments on what they would like to see as part of 'cake deploy'. Please keep in mind that I am under no obligation to accept any of your ideas. :) -- Chris Hartjes Internet Loudmouth Motto for 2008: "Moving from herding elephants to handling snakes..." @TheKeyBoard: http://www.littlehart.net/atthekeyboard --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
