> * copying the folder layout from the server makes it much easier to upload > files. You can configure textmate and transmit to sync these files to your > server into the correct directory automatically. That's a huge time saver.
That's a great tip, thanks Mike! On Apr 16, 8:00 pm, "Mike Combs" <m...@combsnet.com> wrote: > Once you get set up, you're going to love this. Here is what I'd do. It might > not be right for you but it will give you some ideas. > > Clientname-projectname/ > -- tags > -- trunk > -- -- specs > -- -- -- source (stuff from client) > -- -- -- work (comps and stuff) > -- -- web > -- -- -- .htpasswd and other files on server but not on web > -- -- -- html > -- -- -- -- .htaccess > -- -- -- -- wordpress > -- -- -- -- -- wp-content > -- -- -- -- -- -- themes > -- -- -- -- -- -- plugins > > Notes: > * I use a single repository > * Since most clients have only one project, I didn't nest the folders. I > create a folder for each client-project combination. > * htaccess is tricky to make work so i want it to be in svn > * copying the folder layout from the server makes it much easier to upload > files. You can configure textmate and transmit to sync these files to your > server into the correct directory automatically. That's a huge time saver. > > I hope this helps. > > Sent from my mobile. > > ----- Reply message ----- > From: "blogjunkie" <david...@gmail.com> > Date: Fri, Apr 15, 2011 9:53 pm > Subject: SVN setup advice for single user backing up client projects > To: "Versions" <versions@googlegroups.com> > > Hi guys, I'm a version control newbie and I've decided to start using > Subversion to version and backup my client and personal projects. I > would like some advice on the best way to set up my repos and my > workflow with Versions. > > I mainly create WordPress themes, so the only directories that are > relevant to me are /wordpress/wp-content/themes/mytheme and sometimes / > wordpress/wp-content/plugins/custom-plugin. There's no need for me to > put the whole /wordpress directory under version control. > > I'm planning to create 1 repo for each client (I'm hosting subversion > on my web host) with the following structure: > > Client name > - themes > -- mytheme > - plugins > -- custom-plugin > > Because the repo doesn't reflect the same directory structure as my > WordPress install, how do I create the initial repo directory > structure? Do I just use Versions to browse and create new folders? > > Is there a way I can (be lazy and) share 1 repo for mutliple clients? > I'm worried that things can get cluttered if I have many clients and > create 1 repo for each of them. > > Any other advice you may have to organize my Subversion repos are > welcome. Please remember I'm a newbie - detailed answers are > appreciated. Thanks! > > -- > You received this message because you are subscribed to the Google Groups > "Versions" group. > To post to this group, send email to versions@googlegroups.com. > To unsubscribe from this group, send email to > versions+unsubscr...@googlegroups.com. > For more options, visit this group > athttp://groups.google.com/group/versions?hl=en. -- You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versions@googlegroups.com. To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/versions?hl=en.
