You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Waseem Shahzad <wa...@curemd.com> on 2012/02/23 15:46:56 UTC
Automated Deployments in SVN--Windows
Guys
What is the best approach to deploy through SVN on Remote servers:-
1. ASP pages à Copy and Paste
2. SPs à in SQL 20xx
3. COM+Dlls
Moreover ; Any threat or problem if I put my Live Application in SVN checkout?
Cheers,
Waseem Bukhari
CMer
RE: Automated Deployments in SVN--Windows
Posted by Waseem Shahzad <wa...@curemd.com>.
Thanks for your ACK.
> I have just ASPs files , need to be copy and paste.
>Below are part of my deployment that I want to do with SVN.
1. ASPs --> Copy Paste
2. SQL Scripts
3. DLLs
Any way to work with Other than web svn?
Cheers,
Waseem Bukhari
CMer - Ext: 506
-----Original Message-----
From: Thorsten Schöning [mailto:tschoening@am-soft.de]
Sent: Thursday, February 23, 2012 11:25 AM
To: users@subversion.apache.org
Subject: Re: Automated Deployments in SVN--Windows
Guten Tag Waseem Shahzad,
am Donnerstag, 23. Februar 2012 um 15:46 schrieben Sie:
> What is the best approach to deploy through SVN on Remote servers:-
That heavily depends on your software and environment. If your
software is installable using MSI, I for example prefer using WebSVN
to provide a relative simple download interface directly to a maybe
synced subversion repo to the users. If you have software which
doesn't need to be installed and depending on your customers, you may
even instruct them on using TortoiseSVN and directly.
> 1. ASP pages à Copy and Paste
> 2. SPs à in SQL 20xx
> 3. COM+Dlls
What do you mean with this? Is it describing the parts of your
software which need to be deployed or your ideas how you could deploy
with subversion?
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail:Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon.............030-2 1001-310
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hanover HRB 207 694 - Geschäftsführer: Andreas Muchow
Re: Automated Deployments in SVN--Windows
Posted by Les Mikesell <le...@gmail.com>.
On Thu, Feb 23, 2012 at 10:35 AM, Waseem Shahzad
<wa...@curemd.com> wrote:
> One more thing.
>
>>> What do you mean with this? Is it describing the parts of your software which need to be deployed or your ideas how you could deploy with subversion?
>
> --- Yes , your ideas how you could deploy with subversion?
Some people do run live production servers on a subversion working
copy and trigger svn updates or switches in post-commit hooks on the
subversion server, but it is not really designed for that. For most
purposes it would be better to use subversion for development with a
separate testing/deployment step. For example you might use jenkins
(http://jenkins-ci.org/) to run automated test and deployment jobs
when in notices that changes have been commited, or simply do a manual
checkout on a staging system and then use rsync with the -C option to
push the changes to your production server(s).
--
Les Mikesell
lesmikesell@gmail.com
RE: Automated Deployments in SVN--Windows
Posted by Waseem Shahzad <wa...@curemd.com>.
One more thing.
>> What do you mean with this? Is it describing the parts of your software which need to be deployed or your ideas how you could deploy with subversion?
--- Yes , your ideas how you could deploy with subversion?
Cheers,
Waseem Bukhari
CMer - Ext: 506
-----Original Message-----
From: Waseem Shahzad
Sent: Thursday, February 23, 2012 11:34 AM
To: 'Thorsten Schöning'; users@subversion.apache.org
Subject: RE: Automated Deployments in SVN--Windows
Thanks for your ACK.
> I have just ASPs files , need to be copy and paste.
>Below are part of my deployment that I want to do with SVN.
1. ASPs --> Copy Paste
2. SQL Scripts
3. DLLs
Any way to work with Other than web svn?
Cheers,
Waseem Bukhari
CMer - Ext: 506
-----Original Message-----
From: Thorsten Schöning [mailto:tschoening@am-soft.de]
Sent: Thursday, February 23, 2012 11:25 AM
To: users@subversion.apache.org
Subject: Re: Automated Deployments in SVN--Windows
Guten Tag Waseem Shahzad,
am Donnerstag, 23. Februar 2012 um 15:46 schrieben Sie:
> What is the best approach to deploy through SVN on Remote servers:-
That heavily depends on your software and environment. If your
software is installable using MSI, I for example prefer using WebSVN
to provide a relative simple download interface directly to a maybe
synced subversion repo to the users. If you have software which
doesn't need to be installed and depending on your customers, you may
even instruct them on using TortoiseSVN and directly.
> 1. ASP pages à Copy and Paste
> 2. SPs à in SQL 20xx
> 3. COM+Dlls
What do you mean with this? Is it describing the parts of your
software which need to be deployed or your ideas how you could deploy
with subversion?
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail:Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon.............030-2 1001-310
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hanover HRB 207 694 - Geschäftsführer: Andreas Muchow
Re: Automated Deployments in SVN--Windows
Posted by Thorsten Schöning <ts...@am-soft.de>.
Guten Tag Waseem Shahzad,
am Donnerstag, 23. Februar 2012 um 15:46 schrieben Sie:
> What is the best approach to deploy through SVN on Remote servers:-
That heavily depends on your software and environment. If your
software is installable using MSI, I for example prefer using WebSVN
to provide a relative simple download interface directly to a maybe
synced subversion repo to the users. If you have software which
doesn't need to be installed and depending on your customers, you may
even instruct them on using TortoiseSVN and directly.
> 1. ASP pages à Copy and Paste
> 2. SPs à in SQL 20xx
> 3. COM+Dlls
What do you mean with this? Is it describing the parts of your
software which need to be deployed or your ideas how you could deploy
with subversion?
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail:Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon.............030-2 1001-310
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hanover HRB 207 694 - Geschäftsführer: Andreas Muchow
RE: Automated Deployments in SVN--Windows
Posted by Waseem Shahzad <wa...@curemd.com>.
Thanks for your ACK.
I am using Windows ,Visual SVN Server and tortoise SVN as Client.
Now Pls share your thoughts?
Cheers,
Waseem Bukhari
CMer - Ext: 506
-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2012a@ryandesign.com]
Sent: Thursday, February 23, 2012 10:11 AM
To: Waseem Shahzad
Cc: users@subversion.apache.org
Subject: Re: Automated Deployments in SVN--Windows
On Feb 23, 2012, at 08:46, Waseem Shahzad wrote:
> Any threat or problem if I put my Live Application in SVN checkout?
Depending on where you check out your working copy on the server, your
version of Subversion, and your web server configuration, it's possible
users could access all the files in the working copy's pristine area,
thus possibly being able to read your code and/or gain access to any
passwords or other confidential information contained therein. So I
recommend you configure your web server to deny access to any URL
containing "/.svn".
For Apache 2, I have the following line in my httpd.conf to accomplish
this goal:
RedirectMatch 404 .*/\.svn(/|$)
If you use a different web server you'll have to consult its
documentation to learn how to do that kind of thing.
For automated deployments generally, I've often recommended
SVN::Notify::Mirror. I don't know if it will help in your situations
specifically.
http://search.cpan.org/perldoc?SVN::Notify::Mirror
Re: Automated Deployments in SVN--Windows
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Feb 23, 2012, at 08:46, Waseem Shahzad wrote:
> Any threat or problem if I put my Live Application in SVN checkout?
Depending on where you check out your working copy on the server, your version of Subversion, and your web server configuration, it's possible users could access all the files in the working copy's pristine area, thus possibly being able to read your code and/or gain access to any passwords or other confidential information contained therein. So I recommend you configure your web server to deny access to any URL containing "/.svn".
For Apache 2, I have the following line in my httpd.conf to accomplish this goal:
RedirectMatch 404 .*/\.svn(/|$)
If you use a different web server you'll have to consult its documentation to learn how to do that kind of thing.
For automated deployments generally, I've often recommended SVN::Notify::Mirror. I don't know if it will help in your situations specifically.
http://search.cpan.org/perldoc?SVN::Notify::Mirror