Following your guidelines, I got this working, including SVN/TortoiseSVN directly on my drive. It's great!
However, I've just been offered a couple of (probably freebee) jobs, and since I really am a newbie still, my immediate (and required) response was to install PHP (to access the plethora of public scripts for guestbooks, forums, blogs, etc.). I now have a good setup: Eclipse for Flex, and Dreamweaver for everything else. But I can't for the life of me figure out how to include the non-Flex Projects into the versioning. For example, what I'd like is, as per my server, to be able to have folders named per the sites: (HTDOCS root folder) -shawngibson.com folder -myothersites.com folder -projectsite.com folder -projectsite2.com folder (etc.) ...and have Dreamweaver with my localhost for testing (I have apache on my development machine), using the SVN repository for Local files (makes sense), and of course Remote server is my server, live (which should be uploading all the versions, just the newest one, obviously). How do I get the versioning to work properly with this? I keep doing things that SAY they worked, but then I go in and modify say index.php in Dreamweaver in shawngibson.com, use the Dreamweaver extension for SVN, hit Commit, and it throws me an error. It works perfectly for new projects in Flex (using exactly the instructions you provided for building an area to work in), but nothing else, at this point. Any suggestions? Thanks kindly, Shawn --- In [email protected], Kevin <[EMAIL PROTECTED]> wrote: > > > I'm a bit in the dark here, but am I correct in assuming that I can > > use the above setup to have my main Flex/CF development machine... > YES. You are correct. > > At this point, I've installed the Subclipse plug-in into Eclipse, and > > a so-called no-brainer package to get "Tortoise" and SVN on my > > development machine. > All you need is Subclise. If you want to try to set up your own SVN, > go for it. HOWEVER, i found it much easier to use the following SVN > hosting service: > http://www.myversioncontrol.com/ > > They set up everything for you and if your project is under 4mb, it's > free. You can also use https (which was a plus for me) as well as an > included Trac site. I use the $5/month version, which for me was well > worth it. It literally took me 10 min to signup and set up my SVN. > Their email support is pretty good as well. > > > > After that, I've no idea yet how to get these things up and running > > (I'd appreciate any help there); also, how do I extend all this so > > that the 3 computers are able to do their thing? > In myversioncontrol.com (or on your personal SVN) set up a user/ > password for each computer that you may use to code. > > You can do everything else in eclipse. > > Go To the SVN Repository perspective, right-click and add new > repository location using the wizard. > You can then add dirs (right-click) for different projects and then > folders like branches, tags, trunk as needed. > HERE IS HOW I DO IT: > svn_root > - some_project > - branches > - truck (main dev code) > - tags > -another_project > - branches > - truck (main dev code) > - tags > > (see SVN manual for description of these OR http://en.wikipedia.org/ > wiki/Subversion_%28software%29#Branching_and_tagging). > You can initially import a project into the project trunk OR > you can change to the project's perspective and choose: Right Click - > > Team -> Share Project to upload your code > (I prefer the later, however, remember to ignore certain eclipse > files like .project [see below]) > > Once you have your code on the SVN, you can go to your other > computers and do the following: > Go To the SVN Repository perspective, right-click and add new > repository location using the wizard. Add these with their unique > user/pw. > Once the repository is added, navigate to the truck of the project > you want to checkout and right click - Checkout > Use the Checkout to New Project and go through the wizard as if you > were setting up a New Project in Eclipse. > Once the new project is set up, it will download the trunk into the > project. > You can now move back to the project's perspective and Team- >Commit > when you want to commit your updates. > > You are now under version control. A couple things to note: > - It is good practice to always do a Team->Update before you start > working on some code to make sure you have the latest version. > - Remove .project files & .setting files from version control as you > don't really want to be committing those back & forth. You can > choose files to ignore by clicking Team->Add to svn:ignore > - Commit files when you are done using a computer or you will get > into messy conflict issues every time you work on your code. > > I hope that helps simplify the process. It is actually very easy > once you get it all set up. > > - Kevin >
