FP Best Practices: How to manage versions

[tcarnahan]

I maintain a small web site for an organization. I
maintain the development area on my computer and upload
to the host.

Can someone suggest the best way to manage versions. I
need to make changes to pages, test them, test the links,
test it on the host, then when I'm sure it is ready,
replace the existing web pages. I am always worrried
about overwriting my "active" content while working on a
draft.

Can anyone suggest the best way to keep this from
happening during development?

 

[Rick Budde]

This depends on the type of website you work on.

If your website is relatively simple and does not use
anything that requires server side scripting (database,
ASP pages, etc.), then just test your changes on your
disk based web using Front Page and View in Browser.

If your website is more complex, you should obtain
another host site where you can make changes without
interferring with your live site. Once your changes are
operating, publish them to your production site.

 

[Andrew Murray]

What OS are you running?

If you have Windows 98, then it comes with "personal web server" which allows you
to use your PC like a web server and to publish to http://localhost/

or if you have Windows 2K or XP professional it has IIS included (not installed
by default)
and you can test the site this way, including server extension features, if you
install them on your machine.

then you can test everything and it will function like the live site but won't
be.

then you can publish when you're sure everything works.

Else, you could sign up for a second hosting service to use as a test platform.

 

[=?Windows-1252?Q?Rob_Giordano_\=28aka:_Crash_Gordo]

or create a subweb to test in



| What OS are you running?
|
| If you have Windows 98, then it comes with "personal web server" which allows you
| to use your PC like a web server and to publish to http://localhost/
|
| or if you have Windows 2K or XP professional it has IIS included (not installed
| by default)
| and you can test the site this way, including server extension features, if you
| install them on your machine.
|
| then you can test everything and it will function like the live site but won't
| be.
|
| then you can publish when you're sure everything works.
|
| Else, you could sign up for a second hosting service to use as a test platform.
|
|
| | > I maintain a small web site for an organization. I
| > maintain the development area on my computer and upload
| > to the host.
| >
| > Can someone suggest the best way to manage versions. I
| > need to make changes to pages, test them, test the links,
| > test it on the host, then when I'm sure it is ready,
| > replace the existing web pages. I am always worrried
| > about overwriting my "active" content while working on a
| > draft.
| >
| > Can anyone suggest the best way to keep this from
| > happening during development?
|
|