I typically deploy to production using a Subversion checkout. The only controller I have in the repository is index.php, which is enforced by a "*_*.php" svn:ignore property on the web directory.
If I need to access another environment on the production server in 1.0, I create a controller using the init-controller task (which is absent in 1.1?), then delete it. Isn't this simple enough? How about a subversion:set-ignores task that sets all these svn:ignore properties across the project? Kris On May 20, 1:34 am, "Tristan Rivoallan" <[EMAIL PROTECTED]> wrote: > On Tue, May 20, 2008 at 10:23 AM, Ian P. Christian <[EMAIL PROTECTED]> wrote: > > > > > Tristan Rivoallan wrote: > >> On Tue, May 20, 2008 at 10:14 AM, Ian P. Christian<[EMAIL PROTECTED]> > >> wrote: > >>> Having said that.... What are peoples thoughts on having IP restricted / > >>> htpasswd restricted stuff in the default .htaccess, but commented out. > > >> yes that could go nicely along with the other stuff. but why should it > >> be commented out by default ? > > > My reason for this suggesion is that we've alrady agreed that we'll have > > IP restrictions directly in teh _dev files, so adding it to .htaccess > > too might be a bit over the top - if you wanted to un-restrict it, you'd > > need to edit 2 files. > > true. > > ++ > tristan > > -- > Tristan Rivoallanhttp://www.clever-age.com > Clever Age - conseil en architecture technique > GSM: +33 6 219 219 33 Tél: +33 1 53 34 66 10 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
