Steve Rieger wrote:
> hi all
> i have the following set up and am looking for pointers.
> all the developers write on their local boxes, then upload to the dev
> QA upon request from dev moves from dev to stag
> once it passes QA sys admin moves from stag to prod.
I work in a company with quite a similar system and I found that the
easiest way was to be a bit inventive. I installed an ssh server on
remote Windows(cygwin) machines (dev,stg, live etc) which then enabled
me to use rsync to copy files from my subversion server up to the
various environments. Of course if you're lucky enough to be using linux
on the remote server then even better.I wrote some scripts in perl which
I can easily post if that would be useful. The process we follow is:
site is created in svn using perl script and details of remote servers
placed into a mysql database for later retrieval. This includes folders
which should not be uploaded etc in a seperate field
Users develop on their local machines
commit changes to the repos
When they wish to upload:
login to the subversion box using a restricted login from a shortcut on
their desktop - this runs another perl script
User chooses from a list of sites they wish to upload
They enter their svn username and password(we're using apache + mod_dav
+ htpasswd authentication)
If they are verified they are asked to choose where they would like to
upload to (dev/demo/stg etc etc)
they then confirm their request by typing in "yes"
The system then checkouts files to a tempdir and rsyncs the files
across(if being sent to a live/stg environment all .svn/ folders are
The above has problems in the fact that you are only authenticating
users with their svn passwd's but the script could easily be adapted to
enable only sysadmin's to upload to production or similar.
> i am sure that there is a way we can do all these changes through svn,
> how would i go about doing this.
> does anybody have any docs or pointers.
I can post scripts if requested?
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Aug 11 14:18:42 2005