On Jan 30, 2008 11:58 AM, crimson090 <jon_at_cabot.net> wrote:
>
> Thank you very much for the responses. I do realize that this is not an ideal
> setup; however we are working with a content management system that only
> gives us one license, and so we cannot setup a development server with a
> cost that my company is not willing to pay for.
Double check that licensing. Many companies will allow you to run
development/test environments under the same license that you've
purchased for production use. If that's not possible, the message that
I hear is "the company is not willing to devote the resources to
setting up a proper environment, and most likely doesn't understand
the risks that introduces."
You're flying without a net. I've been there. Accidents will happen,
and your live site will go down. Maybe not today, but someday. Is your
management going to take the blame/responsibility when that happens,
or will it fall on your shoulders?
> So if I understand correctly, I will need to make a copy of the project and
> all related files, one for each user. Then I will need to setup the original
> files as the master repository. Then when users check out their own copy of
> the files, Tortoise will know to merge those changes with the original
> master files. Is that correct?
Put the production code into Subversion, then each user checks out
their own copy from there into their own working copy. When their
changes are done, the users commit, and everyone else's WCs will be
updated when they run svn update. When you're ready to deploy out to
production, export to your live website (if you make the live site a
working copy, it's as easy as svn up).
> Nearly everyone here uses a Mac as we do publishing. I am the only one with
> a PC. So I suppose I could do my development locally now, and have Tortoise
> upload the changes to the server. But yes, we have had no problems using
> remote desktop connection on the Mac's to use Visual Studio.
>
>
>
> Lasse Vågsæther Karlsen wrote:
> >
> > Basically, to expand further on the idea by Ron, you need to check out
> > multiple copies on the same server into individual working folders.
> >
> > This way, each developer will use a terminal server connection with their
> > own user (and thus, their own session and context), and work on their own
> > personal copy of the files. This will function like multiple workstations.
> > Then you use TortoiseSVN/Subversion against a common repository, and each
> > user checks out his working copy from that repository, once you've set it
> > up.
> >
> > What you cannot have, and where TortoiseSVN/Subversion *won't* help you is
> > if you keep just one copy of the files on the server and have multiple
> > users
> > working on these at the same time, like you're currently doing.
> >
> > I understand why you are all working on the same copy of the files:
> > without
> > version control, synchronizing the changes is insurmountable.
> >
> > As for a web app, you do not say wether this is what you're writing. Since
> > you're all using Mac's I guess you would be making web apps (otherwise,
> > why
> > are you using Mac's when you need to do Windows development?), so I don't
> > know if you can get the visual studio 2008 development web server working
> > reliably on a terminal server, but I assume you can.
> >
> > On Jan 30, 2008 4:04 PM, Ron Wilson <ronw.mrmx_at_gmail.com> wrote:
> >
> >> On Jan 30, 2008 9:51 AM, crimson090 <jon_at_cabot.net> wrote:
> >> > We do not have a development server, so all
> >> > work is done on the production server. We also have mostly Apple
> >> computers,
> >> > so we have people using remote desktop to connect to the server, load
> >> Visual
> >> > Studio, and make updates there.
> >> >
> >> > Of course this causes all sorts of problems when two people are working
> >> at
> >> > once, because they both are modifying the same project. Even if they
> >> are
> >> > working on different files the project still complains about file
> >> > modifications.
> >>
> >> Yes. In fact SVN/TSVN will solve a lot of your problems.
> >>
> >> Each developer will have their own working copy of the project. Does
> >> not matter if they are all on the server. However, you will need to
> >> your TSVN cache setting to "Shell" so each user has their own cache.
> >>
> >> I also suggest you have an additional working copy for integration and
> >> testing. Once your testing is done, you can export from that working
> >> copy to your production build area and do your production build,
> >> there.
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
> >> For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
> >>
> >>
> >
> >
> > --
> > Lasse Vågsæther Karlsen
> > mailto:lasse_at_vkarlsen.no
> > http://presentationmode.blogspot.com/
> > PGP KeyID: 0xBCDEA2E3
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Will-TortoiseSVN-work-in-this-environment--tp15183207p15185137.html
> Sent from the tortoisesvn - users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
>
> To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
> For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-01-30 18:45:08 CET