Creating the model on a production server is not a good idea, does not matter if it is shared, vps, dedicated. You should do all of these tasks on a development server where you can test everything and if you break something, you can fix it without taking down the site. Once you have everything working, update production through ftp, rsync, svn, git or other means. Source control (svn or git) is the best way.
Pablo On Tue, Jan 6, 2009 at 8:02 AM, Eno <symb...@gmail.com> wrote: > > On Tue, 6 Jan 2009, Ward Loockx wrote: > >> - What is the project freeze ? Why can't you just upload the env to ftp >> ? what does the freeze exactly do? > > The freeze command copies the symfony library and related stuff into your > project. So you can upload it to a host that doesn't have symfony > installed or as a different version of symfony installed. Your project > becomes a self-contained sandbox with no external dependencies (except PHP > :-) > >> - I have setup dev/prod env. on shared hosting without shell. I now >> program directly via ftp on the shared hosting (not a good idea?) > > So you have dev controllers on a production machine?! Is it a separate > vhost or the same one? Generally that's not good :-) > > Also, what about backups / version control? > > > -- > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
