Re: [WebDNA] Client wants backup copy of site
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 104290
interpreted = N
texte = Terry Wilson wrote: > I'm bidding on a job for an org and have a phone interview tomorrow. > They are coming away from a php website that was abandoned by the > previous (volunteer) web developer. There's a person on the committee > who does old-school web design, i.e., static sites. She has requested > that the new site be periodically archived onto CD and given to them so > they don't run into the issue they are now having. I'm sure she imagines > the site is something that can just be opened in Dreamweaver and > updated, or something. Anyway, what is the accepted practice for this > type of request? Give them the WebDNA pages as is, encrypt parts of it, > tell them this isn't how it's done... what? I generally assure people > that I have a whole team (you guys!) behind me if the worst would > happen, but I understand they need reassurance too. > > Thanks, > Terry Hi Terry, My .02�.. For the backup.. I would take the WebDNA pages "as is" route and and educate the person that dynamic sites are programs that do not simply open in WYSIWYG apps very well... Regarding encryption... trying to retain a customer by encryption or not giving them key aspects of the site just takes too much effort (if that is what you meant by encrypting parts of it).. if my customer wants to go from me to one of you guys, then fine, they should be able to do that IMO. I try and retain customers through quality of service and then go from there... but that's just me... I'm not retiring anytime soon, and more than one of my clients have left (to take their services in-house, or to copy my code to some other language ;-).... so, my methods may not be ideal for some. ) For backup strategy.. If you are on a *nix box, you can almost automate it.. I would use rsync to get an exact replica.. I usually do this manually, but it could be done via crontab. (rsync copies only changes, and is very accurate) Once you have a backup, you could then do a tape archive, or just burn to CD as-is. (tar would be a smaller file size but would have to be opened via a compression utility or the command line) Generally, CD's/DVD's as an archive method is just fine and something the customer can understand.. but you probably want to charge them for the time/resources it takes to manage that kind of system. Man, I'm wordy this new year. Donovan -- Donovan Brooke WebDNA Software Corporation http://www.webdna.us **[Square Bracket Utopia]**
Associated Messages, from the most recent to the oldest:
Terry Wilson wrote: > I'm bidding on a job for an org and have a phone interview tomorrow. > They are coming away from a php website that was abandoned by the > previous (volunteer) web developer. There's a person on the committee > who does old-school web design, i.e., static sites. She has requested > that the new site be periodically archived onto CD and given to them so > they don't run into the issue they are now having. I'm sure she imagines > the site is something that can just be opened in Dreamweaver and > updated, or something. Anyway, what is the accepted practice for this > type of request? Give them the WebDNA pages as is, encrypt parts of it, > tell them this isn't how it's done... what? I generally assure people > that I have a whole team (you guys!) behind me if the worst would > happen, but I understand they need reassurance too. > > Thanks, > Terry Hi Terry, My .02�.. For the backup.. I would take the WebDNA pages "as is" route and and educate the person that dynamic sites are programs that do not simply open in WYSIWYG apps very well... Regarding encryption... trying to retain a customer by encryption or not giving them key aspects of the site just takes too much effort (if that is what you meant by encrypting parts of it).. if my customer wants to go from me to one of you guys, then fine, they should be able to do that IMO. I try and retain customers through quality of service and then go from there... but that's just me... I'm not retiring anytime soon, and more than one of my clients have left (to take their services in-house, or to copy my code to some other language ;-).... so, my methods may not be ideal for some. ) For backup strategy.. If you are on a *nix box, you can almost automate it.. I would use rsync to get an exact replica.. I usually do this manually, but it could be done via crontab. (rsync copies only changes, and is very accurate) Once you have a backup, you could then do a tape archive, or just burn to CD as-is. (tar would be a smaller file size but would have to be opened via a compression utility or the command line) Generally, CD's/DVD's as an archive method is just fine and something the customer can understand.. but you probably want to charge them for the time/resources it takes to manage that kind of system. Man, I'm wordy this new year. Donovan -- Donovan Brooke WebDNA Software Corporation http://www.webdna.us **[Square Bracket Utopia]**
Donovan Brooke
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
RE: Missing contexts on NT (1997)
[subtotal] and others (1997)
SKU (1997)
WebDNA iTools patch (2006)
includes and cart numbers (1997)
Shared Webstar Directory (1998)
include (1998)
forming a SKU (1999)
RAM variables (1997)
Cart questions (1997)
More about BIAP W*API.... (1998)
practicing safe queries.. (2000)
urls (2005)
Windows nt service pack 3 upgrade (1997)
Practice runs ? (1997)
Re:Copyright ? (1997)
serial number (1998)
Associative lookup style? + bit more (1997)
Re[4]: Problem with new formvariables (2000)
UPDATE PROBLEM (1997)