Subject: Home Depot Spring Rewards - Expiring Soon

From: Window Installation Update <[email-masked]>
Date: Wed, 04 Jun 2014 08:56:36 -0700

** As a Valued Subscriber to our publications, you have been chosen to receive an unique offer:

(1) New Windows Installation

Recipient: Ipp-archive
Expiration:click to check availability -> http://www.madeply.com/view/window/installation/info.index 

Confirm Size and Quantity Below: 
http://www.madeply.com/view/window/installation/info.index

Home Depot Spring Rewards
Issued 06/04/2014

We hope that you enjoyed this DIY remodel Update
If you would like to stop further messages write Update Notice Messages
118 Kecks Lane
Ruff Dale, PA 15679 or visit http://www.madeply.com/3hrn.skejr

In case of error(s) in the new code, do you reset per commit or the entire pull? (Or is only 1 possible?)   Rudie Sep 27 '10 at 13:19
This is close. It starts just fine but wont let me stop anything. I was able to log out and back in and then kill the node process. Forever didn't restart it. So I am thinking something about how it works isn't compatible with DH.   you can't kill the node process because Forever itself runs on node! I've added some usage instructions to my answer, including how to stop a process. I've been using this on my VPS and it's worked like a charm.   forever stop 0 had an error and things just kind of fell apart from there. I have been trying to do this without root on its own user so that I can clean up easily once I find the right solution. That may be my problem. I will look into it some more. I had something wrong with npm that was causing problems. With npm and node installed correctly forever works great. What I ended up doing was adding the forever start commands to a cronjob set to run on restart. I am now working on a little node app that will let me start and stop forever procs. Th
 ere's an alternative to Forever which uses node's native cluster API
@Rudie: If you need to roll back changes on the deployment server, then you can use git reset to move back among the latest changes (all commits, not just the whole pull). If you need to roll back something specific that's not the latest commit, then you can use git revert but that should probably be used in emergencies only (git revert creates a new commit that undoes the effect of some previous commit).Just out of curiousity: why do you think hooks would be more trouble than it's worth for this?  When using hooks for this, the actual web server docs directory is changed by an automatic background process. Logging in lets me have more control over exactly when changes are applied to the docs directory. Also, it's easier to fix when things go wrong. Hooks might be more appropriate if committers don't have sufficient access to log in to the web server. I was about to post a list of what I do at my Windows/.NET shop, but it's more or less what you've got here. +1   Daniel Schaffer Jan 
 8 '09 at 20:21
  	  	
have you encountered any disadvantages for having a svn co as a production environment? I really can't think of any disadvantages but it doesn't seem "clean" to have a svn co as production? Why not an svn export or rsync?   ChrisR Nov 10 '10 at 18:11
  	  	
Because of the basic difference between a co and an export - you can't push specific changes, you have to export the entire application again. It's a very important difference that makes life that much easier   Eran Galperin Nov 10 '10 at 22:50
18	  	
Why put up the site down screen? If you run a directory of releases/, and point liveSite/ via a symlink to your folder in releases/, then you can completely checkout the site into a new releases/ folder and flip the symlink over instantaneously once the co is done? No need for downtime (unless you are the poor sob that makes a request during that symlink switch).   Joseph Lust May 20 '11 at 20:38
  	  	
@EranGalperin Somewhat unrelated question: did you write the schema deltas script yourself, or is it some open library?   Artem Goutsoul Oct 16 '12 at 9:06
1	  	
Who is responsible for doing all those tasks such as update SVN on production and symlinkin the new release? Is it phing? Is it jenkins?   drgomesp Jul 14 '13 at 15:00
  	  	
@EranGalperin, how do you rollback the changes if the tests fail once you've updated the production c/o?   blacktie24 Oct 5 '13 at 18:22
  	  	
And it seems the downtime of server is unnecessarily high