Working live

[JL Amerson]

Why shouldn't I work on my site live? This is what I do and so far it's been
fine but I'm sure there are valid reasons not to do this.
--

JoAnn

Do not meddle in the affairs of cats, for they are subtle and will piss on
your computer.
--Bruce Graham

 

[Bob Lehmann]

Working local and then publishing is best practice. I've never worked on a
site live.

But....
As long you have some kind of version control to fall back on in case you
mess something up, it should be OK. Except, what if someone goes to a page
while you're working on it, and it's not working correctly.

Bob Lehmann

 

[Joe Rohn]

Hi JoAnn,

The main and only reason in my mind not to work live..if you make a mistake
and don't catch it right away..it's there for all to see!

Outside of that..just make sure you have a backup (publish down in your
case)

Now coming from someone who has a hard time with their, they're, there, not
to mention affects, effects, insure, ensure, weather and whether I have no
problems working live!

--
Joe

Forum Crafters:
http://www.forumcrafters.com
FrontPage Users Forums:
http://www.timeforweb.com/frontpage

 

[chris leeds]

you could "break" something.
you could accidentally overwrite your changes when publishing the web off
your local server.
it may consume resources from the server that don't need to be.
probably a bunch of other stuff but I do it all the time to test asp stuff
my local server won't do. then I right click the page and select 'publish
selected files' and shoot it down to my local copy.

 

[Steve Easton]

Just in case you break something.
Also, I always work local and then publish because then I always have an
up_to_date *backup* should a server crash.
;-)

--
Steve Easton
MS MVP FrontPage
95isalive
This site is best viewed..................
...............................with a computer