We use ASP.NET, C# When making an update to one of our websites, we roll out the entire site rather than updating just the pages or sections that have changed. This scares me. Is this a good idea? Should I roll out only the changes? Should I break my site into smaller projects? What is best practice? ...
We use ASP.NET / C#. We work locally, test locally, check in our code and binaries through SVN. On our server, we checkout the latest 'build' from SVN directly into our IIS web directory. Is this a good practice, or is there something else we should be doing for rollouts? ...
We are rolling out a site for a client using IIS tomorrow. I am to take the site down to the general public (Sorry, we are updating message) and allow the client to test over the weekend after we perform the upgrade. If it is successful, I open it to everbody - if not, I rollback. What is the easiest way to put a "We're not open" si...
Hi, I'm using git for my workflow and I have a remote testing server. What would be the best way to do this. Currently I make my changes on my workstation and I commit changes and then push to server. But this would quickly lead to many small commits. I want to avoid setting up testing server on my workstation. And rebasing commits is...
My client has 1000 WordPress blogs hosted on a server for customers. Each one is in its own domain through cpanel and SuPHP, running in CGI mode on Apache2.2. Now he wants me (I'm the PHP programmer) to get WP-Cache loaded out on each of these blogs and not just activated, but enabled. He also wants the timeout value set to 2 days instea...