>> That's great news. I've never used a version control system or any
>> sort of developer framework. Would something like this work?
>
> I'm sorry but it really does sound like you have no idea how Subversion works. Please spend several days reading the book front to back:
>
> http://svnbook.org/
Right now I'm trying to decide whether or not I should use subversion.
Hopefully there is a less time-consuming method for making that
determination.
My goals are to implement a good development framework and to define a
(changing) list of files which are the only files a developer is
allowed to either read or write. If I can do that with subversion and
path-based authorization, I'd like to get an idea of the workflow
involved. Here is a modified version of my proposed workflow.
Hopefully it is more intelligent than my last attempt:
1. I install a subversion server on my dev machine.
2. I decide which file or files I want my dev to work on and give him
read/write access to only those files (and neither read nor write
access to any other files) via path-based authorization on the
subversion server.
3. The dev uses a subversion client over an encrypted connection to
edit the permissible files. He can test his changes via http on the
dev machine.
4. Once he is done, I test his changes via http on the dev machine and
use svn log to look at the specific changes he made.
5. I use rsync to copy the changes made to the dev machine's files to
the production machine.
6. Steps 2-5 are repeated.
Is this any better?
- Grant
Received on 2011-10-01 08:43:26 CEST