Comments on: Better Application Deployment http://www.littlehart.net/atthekeyboard/2009/11/27/better-application-deployment/ Facebook should've be written in unicornSchemaLang, because everyone *knows* that PHP is no good for anything, right? Thu, 09 Sep 2010 20:57:35 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Francis http://www.littlehart.net/atthekeyboard/2009/11/27/better-application-deployment/comment-page-1/#comment-15026 Francis Sat, 19 Dec 2009 23:30:23 +0000 http://www.littlehart.net/atthekeyboard/?p=621#comment-15026 With my clients I've started using 'git push' to deploy to the servers. On the server I have the working copy in a "production branch". I ssh in and check for local modifications, and then do a 'git merge master' if there are none. If there is local modifications I check what's going to be updated 'git diff master' and if nothing conflicts I can just merge. If they've edited some of the same files I have, I can usually just stash their changes and then pop the stash after a merge. It doesn't sound simple, but it keeps me on top of every change and lets me know if they're editing something I should change in the source. That and database migrations have made my job a *lot* easier. With my clients I’ve started using ‘git push’ to deploy to the servers. On the server I have the working copy in a “production branch”. I ssh in and check for local modifications, and then do a ‘git merge master’ if there are none. If there is local modifications I check what’s going to be updated ‘git diff master’ and if nothing conflicts I can just merge. If they’ve edited some of the same files I have, I can usually just stash their changes and then pop the stash after a merge.

It doesn’t sound simple, but it keeps me on top of every change and lets me know if they’re editing something I should change in the source.

That and database migrations have made my job a *lot* easier.

]]> By: Travis Swicegood http://www.littlehart.net/atthekeyboard/2009/11/27/better-application-deployment/comment-page-1/#comment-14902 Travis Swicegood Mon, 30 Nov 2009 15:02:16 +0000 http://www.littlehart.net/atthekeyboard/?p=621#comment-14902 Another option is to use PEAR then use the include_path for files that need to be modified. You end up with base/ and custom/. Tell the client to copy anything out of base/ that they want to modify, then you're set. Just make sure you never package anything in the custom/ directory. Another option is to use PEAR then use the include_path for files that need to be modified. You end up with base/ and custom/. Tell the client to copy anything out of base/ that they want to modify, then you’re set. Just make sure you never package anything in the custom/ directory.

]]>