That approach with svn seems like a pretty good idea. The only thing I like better about 'symfony sync go' is that if necessary I can set it up to deploy things that we don't keep in the repository, like dynamically generated images and such.
SVK is working pretty well. The main problems I have with it: * No pretty Tortoise-like interface. I'm cool with that but it makes it hard to sell to my coworkers on Windows. * No support for svn:externals. This is actually the bigger problem for me by far. On the bright side, even if you ignore the ability to use your repository in a detached fashion, it's got some nice features when compared to svn: * No .svn directories littering your working copy. * General text interface polish. For instance. if you do an svk add directory_name it will automatically find and add all new files anywhere under direcotry_name. I'm looking into similar alternatives for checking out entire svn repositories, using them detached, and then deploying changes back to the central repository. There are projects for doing this with git, mercurial, and bazaar... but as far as I know none of them have figured out a good way to support svn:externals yet. If one of them does I will pounce. :-) David On 8/17/07, Kiril Angov <[EMAIL PROTECTED]> wrote: > > I am also using svn for version control. What I am doing is not using > the sybversion sync at all. I am using an asvn working copy on > production which allows me to push changes with a simple 'svn switch > svn://domain.com/tags/release-1.1', for example. I have the web server > deny access to .svn directories and if somebody decides ofter all to do > some changes in production directly I can see that clearly with svn st. > This has saved me a whole lot until now and I do not see a reason why > not use this approach, rather than 'symfony sync go'. What problems did > you have with svk, I have been using it for not that long and I want t > know if I should invest the time into learning it more or if there is a > better solution. I really like the idea that svn is still using svn as a > backend which means that I can still continue using svn as usual and > have the added decentralized option. It seems to me important enough > that maybe the svn guys should make svk part of svn and write it in c > rather than than perl :) > > regards, > Kiril > > David Brewer wrote: > > The last piece of the puzzle is version control -- we are mostly using > > subversion, but if you are using distributed version control like git, > > bazaar, or mercurial and you have your virtual machines running on a > > laptop you can work totally unplugged.n > > I've been using SVK to mirror our subversion repositories on my > > laptop, which allows me to continue making updates while unplugged and > > then push all the changesets to our subversion server when I get back > > to the office. But it's not ideal and I'm starting to look into other > > options. Anyone using a different approach to do detached work on a > > central repository? > > > > On 8/16/07, Kiril Angov <[EMAIL PROTECTED]> wrote: > > > >> I second David's workflow. In my previous company we used exactly the > >> same procedure and we could replicate the production servers with only > >> one physical machine, thus no longer working on the production code > >> while the code is running (yeah, I was shocked too when I went for my > >> first day. They created a copy of the file, implement the changes and > >> then copy the changes to the old file :)). The good part of the virtual > >> machine is also that you do not ruin your desktop machine installing and > >> removing packages which you think you need for development but then you > >> don't, etc, especially if you compile from source. > >> > >> I can attest that the same virtual machines work just fine under VMWare > >> Fusion (vmware support for Mac). I am happy that other people also > >> reached the same process for development as I did with trial and error. > >> > >> Regards, > >> Kiril > >> > >> David Brewer wrote: > >> > >>> I can't speak directly to your rsync issues, but I can speak a little > >>> to your virtualization question. > >>> > >>> At our company we use VMware server to make virtualized server > >>> environments for each project. This has worked out great for us: > >>> > >>> 1) The virtual machines can be pretty small because it doesn't take > >>> much memory or space to run a small development server. > >>> > >>> 2) The virtual machines can easily be copied, which means that you can > >>> have one central staging server and each developer can have their own > >>> local version of the server which is exactly the same in terms of > >>> software versions and settings. > >>> > >>> 3) The same virtual machine works fine under Windows and Linux (and > >>> probably OSX as well, although we haven't tried that yet). You just > >>> connect to a shared folder on your development server using samba (on > >>> Windows) or sshfs (on Linux) and then you can use your preferred tools > >>> and desktop environment, no problem. Commands that need to be run on > >>> the server are run using an ssh session. > >>> > >>> 4) It's free (as in beer). > >>> > >>> I started out developing on Windows using this setup... after a few > >>> months I was comfortable enough with Linux that I wanted to completely > >>> switch, so now my computer is all Linux... but the virtual machines > >>> are exactly the same either way. As an added bonus, if you DO decide > >>> to mostly switch to Linux, you can virtualize Windows inside VMware > >>> Server as well. That works fine but can be a bit tricky since many > >>> computers come with OEM copies of Windows that are locked to the > >>> specific hardware they came with; make sure you research this issue > >>> before going that path (ESPECIALLY if you are using Vista, which has > >>> stricter rules regarding virtualization). > >>> > >>> Hope that helps, > >>> > >>> David Brewer > >>> Second Story Interactive Studios > >>> > >>> On 8/16/07, Alex Salle <[EMAIL PROTECTED]> wrote: > >>> > >>> > >>>> Hi, > >>>> > >>>> Using the cwRsync files on trac allowed me to use the symfony sync > >>>> command > >>>> through the Windows command prompt, but it created a rather serious > >>>> problem > >>>> with file permissions. All files are being sent to the Linux production > >>>> server with rwx-------- permissions. Then the web server is unable to > >>>> access > >>>> these files and Apache throws forbidden errors. > >>>> > >>>> Will I have to shift my dev environment to linux to avoid these > >>>> headaches? > >>>> If so, should I virtualize within Windows if I use MS apps such as Office > >>>> and Photoshop? > >>>> > >>>> If not, what kind of fix is there? > >>>> > >>>> Thanks! > >>>> > >>>> - Alex > >>>> > > >>>> > >>>> > >>>> > >>> > >> > > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
