Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Reg88

macrumors regular
Original poster
Jun 8, 2010
107
3
Hi,
I am coming from Windows and now setting up my local environment on my Mac.

Currently I use an assembla SVN repo, and I store all of my working copies in /documents/SVN/clientName.

1) If I add MAMP to the mix, is there any problem making the client htdocs folders the SVN working copies? So that MAMP can be my local test?

2) Has anyone stored the htdocs folder on Dropbox? Or would that cause problems?

Thanks!
 

firedept

macrumors 603
Jul 8, 2011
6,277
1,130
Somewhere!
Hi,
I am coming from Windows and now setting up my local environment on my Mac.

Currently I use an assembla SVN repo, and I store all of my working copies in /documents/SVN/clientName.

1) If I add MAMP to the mix, is there any problem making the client htdocs folders the SVN working copies? So that MAMP can be my local test?

2) Has anyone stored the htdocs folder on Dropbox? Or would that cause problems?

Thanks!

I can not directly answer your questions. But I believe your question may be best answered by contacting appsolute GmbH - Support directly. I have been using MAMP PRO for several years and on the couple of occasions I needed support, I have found them to have a very knowledgeable staff. They usually respond back within a couple of hours. Just click on Support with the link provided.
 

SrWebDeveloper

macrumors 68000
Dec 7, 2007
1,871
3
Alexandria, VA, USA
1) If I add MAMP to the mix, is there any problem making the client htdocs folders the SVN working copies? So that MAMP can be my local test?


Thanks!

The other user answered your question, this response is an alternative approach which you might consider, feel free to disregard if not for you:

Switch to GIT which works very well on Mac.
Maintain your repos on GITHUB.
Setup MAMP PRO for your local test.
Use Mac terminal to clone, commit, push, diff etc.
Use a quality IDE such as Komodo or Aptana which are CVS aware.

The repo should not be on the same box - you can lose it all if something breaks (yes, even on a Mac) so remote repo is the way to go. GITHUB web GUI makes repo management a piece of cake and you can create groups to allow read/write access. GIT in general is a more stable and professional tool than SVN and simplifies branching and ignoring files not intended for repo.

Just some thoughts.
 

Reg88

macrumors regular
Original poster
Jun 8, 2010
107
3
The other user answered your question, this response is an alternative approach which you might consider, feel free to disregard if not for you:

Switch to GIT which works very well on Mac.
Maintain your repos on GITHUB.
Setup MAMP PRO for your local test.
Use Mac terminal to clone, commit, push, diff etc.
Use a quality IDE such as Komodo or Aptana which are CVS aware.

The repo should not be on the same box - you can lose it all if something breaks (yes, even on a Mac) so remote repo is the way to go. GITHUB web GUI makes repo management a piece of cake and you can create groups to allow read/write access. GIT in general is a more stable and professional tool than SVN and simplifies branching and ignoring files not intended for repo.

Just some thoughts.

Thank you! I started with SVN, then went to Hg, then back to SVN. So I'll have to do some more research to see if I want to go back to a local->remote report style again. I'm getting to like just pushing to a remote repo since it's just me doing the coding for now.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.