NYCPHP Meetup

[Jeremy Hise]

Well, FTP is a fine option I think, but this deployment strategy I'm
trying to work into cruisecontrol.rb. My ultimate goal is to go to the
cruise control interface, click a button. Make sure my php unit tests
work, make sure php lint doesn't complain and on success, push up the
latest release tag to a production server. This would also allow me to
deploy to QA servers for the testers. Config files and files generated by
the application would need to remain in place.




> So I'm a bit curious and perhaps I'm missing the point here (probably am)
> but why go through all this hassle? Why not just do a straight FTP of the
> files from the staging machine to the deployment machine?  Does using
> checkin/check out benefit us in some way besides the original file
> integrity
> and management?
>
>
>
> Anthony Papillion
>
>
>
>
>
> From: talk-bounces at lists.nyphp.org [mailto:talk-bounces at lists.nyphp.org]
> On
> Behalf Of Max Gribov
> Sent: Thursday, April 29, 2010 12:51 PM
> To: NYPHP Talk
> Subject: Re: [nycphp-talk] Deploying PHP Applications
>
>
>
> On 04/29/2010 01:35 PM, Jason Salsiccia wrote:
>
> Here's how I to do it.
>
> As you said, have a subversion client installed on the server running your
> web host.   If your doc root is /var/www/html,  have html be a symlink to
> current code.
>
> /var/www/html -> /var/www/tag_XXXX
>
>
> and you can also svn export to an nfs share, and then rsync from there to
> multiple machines if you want.
> the rsync and any other tasks can be done by a deploy script.
> using that tag method you can also automate changelog through svn log.
> you'd
> have to have the tag revision numbers.
>
>
>
>
>
> The build script checks out the new tag to the doc root in directory
> /var/www/tag_newtagname.   The last thing the build script does is switch
> the html symlink from the old tag to the new tag to make the deployment
> live.
>
> Jason
>
> On Thu, Apr 29, 2010 at 1:28 PM, Jeremy Hise <jhise at ledcity.net> wrote:
>
> Hiya,
>
> So I've recently been put in charge of a tech department at my company.
> One issue that we are trying to get a handle on is a good way to get our
> PHP applications from a development/staging environment to a production
> server. The production servers are accessible via ssh/ftp/etc. One quick
> thought would be to install a subversion client on the server and have
> that export the application to a spot where a build script could then set
> it up. However, is there a "best-practices" way of doing this?
>
> Thanks!
>
> jeremy
>
> _______________________________________________
> New York PHP Users Group Community Talk Mailing List
> http://lists.nyphp.org/mailman/listinfo/talk
>
> http://www.nyphp.org/Show-Participation
>
>
>
>
>
>
>
> _______________________________________________
> New York PHP Users Group Community Talk Mailing List
> http://lists.nyphp.org/mailman/listinfo/talk
>
> http://www.nyphp.org/Show-Participation
>
>
>
> _______________________________________________
> New York PHP Users Group Community Talk Mailing List
> http://lists.nyphp.org/mailman/listinfo/talk
>
> http://www.nyphp.org/Show-Participation


Jeremy Hise
Application Developer

ledCity.net