Currently I build my websites on my machine, deploy them to a test machine to see if they still work there and then have to request the sysadmin to deploy them to the qa/production servers.
Time after time that what should be my moment of pride is killed by some deployment procedure that was misunderstood, forgotten or not documented.
Currently the sysadmin copies the files from the dev server to whatever server he sees fit and tries to follow my deploymentProcedures.txt.
Is there no mechanism I can use that makes this transition as frictionless as possible? Things I can think of now are
- Set the connectionstring to production DB
- Set CustomErrors to On
- Check if the correct I/O rights are given to the running account
- Make sure the needed COM objects are available
Something that can make the deployment fase easier for people who are not the programmers.