michaelfox + deployment 31
StealJS - Script Manager - Jupiter JavaScript Consulting
december 2010 by michaelfox
There's a lot more to making JavaScript apps than writing JavaScript. StealJS is a collection of command and browser based JavaScript utilities that make building, packaging, sharing, and consuming JavaScript applications easy.
deployment
javascript
packaging
organization
require
december 2010 by michaelfox
37signals's fast_remote_cache at master - GitHub
september 2010 by michaelfox
A faster version of Capistrano's remote_cache deployment strategy
capistrano
deployment
github
git
september 2010 by michaelfox
Deploying websites with Git | News | Phil Sturgeon
may 2010 by michaelfox
Back in 2008 I wrote an article describing how you can use Subversion as a very simple deployment method from your local box, through testing environments to your live servers. Since then I have been using Git to track all client work and personal projects, so I modified this approach to work with Git.
It sounds a little crazy to some people, but really deploying websites with a version control system makes a lot of sense. When you develop on your local box you can change any number of files throughout a codebase and trying to manually remember what files have been changed can be a pain in the nadgers.
You either need to use your VCS (Subversion, Git, Mercurial, etc) to give you a list of changes files so you can manually go around re-uploading each of them, but this can take a long time on a large application.
git
deployment
live
production
workflow
vcs
versioncontrol
deploy
testing
environment
It sounds a little crazy to some people, but really deploying websites with a version control system makes a lot of sense. When you develop on your local box you can change any number of files throughout a codebase and trying to manually remember what files have been changed can be a pain in the nadgers.
You either need to use your VCS (Subversion, Git, Mercurial, etc) to give you a list of changes files so you can manually go around re-uploading each of them, but this can take a long time on a large application.
may 2010 by michaelfox
pascaldevink's Patterns at master - GitHub
april 2010 by michaelfox
Full blown project sampling some design patterns, PHPUnit, Phing and Hudson
phpunit
phing
hudson
project
build
deployment
test
unittesting
continuousintegration
april 2010 by michaelfox
Deploying websites with Git
february 2010 by michaelfox
Back in 2008 I wrote an article describing how you can use Subversion as a very simple deployment method from your local box, through testing environments to your live servers. Since then I have been using Git to track all client work and personal projects, so I modified this approach to work with Git.
It sounds a little crazy to some people, but really deploying websites with a version control system makes a lot of sense. When you develop on your local box you can change any number of files throughout a codebase and trying to manually remember what files have been changed can be a pain in the nadgers.
You either need to use your VCS (Subversion, Git, Mercurial, etc) to give you a list of changes files so you can manually go around re-uploading each of them, but this can take a long time on a large application.
Another option is re-uploading your entire site through FTP which is even more annoying, if not potentially dangerous to live servers as it can destroy file permissions, remove user-uploaded content, confuse cache systems and show programming errors throughout the site as files are deleted and replaced by the FTP client.
FTP clients tried making this easier for us by adding Syncronize features but they just compare dates so they are as useful as a chocolate teapot if you are trying to do careful deployments.
We clearly need another option, and thats where VCS deployments come in. In this case, Git.
git
deployment
development
php
production
workflow
github
from google
It sounds a little crazy to some people, but really deploying websites with a version control system makes a lot of sense. When you develop on your local box you can change any number of files throughout a codebase and trying to manually remember what files have been changed can be a pain in the nadgers.
You either need to use your VCS (Subversion, Git, Mercurial, etc) to give you a list of changes files so you can manually go around re-uploading each of them, but this can take a long time on a large application.
Another option is re-uploading your entire site through FTP which is even more annoying, if not potentially dangerous to live servers as it can destroy file permissions, remove user-uploaded content, confuse cache systems and show programming errors throughout the site as files are deleted and replaced by the FTP client.
FTP clients tried making this easier for us by adding Syncronize features but they just compare dates so they are as useful as a chocolate teapot if you are trying to do careful deployments.
We clearly need another option, and thats where VCS deployments come in. In this case, Git.
february 2010 by michaelfox
related tags
ant ⊕ apache ⊕ app ⊕ automation ⊕ beautifier ⊕ bestpractices ⊕ branching ⊕ bugtracking ⊕ build ⊕ building ⊕ cache ⊕ capistrano ⊕ cocoa ⊕ compression ⊕ continuousintegration ⊕ cruisecontrol ⊕ css ⊕ database ⊕ debugging ⊕ delta ⊕ deploy ⊕ deployment ⊖ development ⊕ distributed ⊕ effeciency ⊕ environment ⊕ fossil ⊕ git ⊕ github ⊕ graph ⊕ hook ⊕ hudson ⊕ image ⊕ inspiration ⊕ install ⊕ javascript ⊕ list ⊕ live ⊕ mac ⊕ min ⊕ model ⊕ opensource ⊕ organization ⊕ osx ⊕ packaging ⊕ pake ⊕ performance ⊕ phing ⊕ php ⊕ phpundercontrol ⊕ phpunit ⊕ production ⊕ project ⊕ python ⊕ question ⊕ reference ⊕ require ⊕ ruby ⊕ scm ⊕ script ⊕ security ⊕ stackoverflow ⊕ staging ⊕ subversion ⊕ svn ⊕ test ⊕ testing ⊕ tools ⊕ tutorial ⊕ ubuntu ⊕ unittesting ⊕ utilities ⊕ utility ⊕ vcs ⊕ versioncontrol ⊕ virtualbox ⊕ warehouse ⊕ webdev ⊕ wordpress ⊕ workflow ⊕Copy this bookmark: