Working with External Servers Check In Out (k)
i wanted pick brains out there.
we have 3 dreamweaver programs here. have 1 internal server, 1
external web server , client's web server.
here's how work:
on our internal server create multiple folders website:
artist1_webiste_ourserver
artist1_website_theirserver
artist2_webiste_ourserver
artist2_website_theirserver
artist3_webiste_ourserver
artist3_website_theirserver
the theirserver folder linked via dreamweaver client's live
website server. check-in/out enabled in dreamweaver.
that works fine , dreamweaver doesn't choke on permissions issues.
here's run trouble:
client has major changes need approved before going live.
we use ourserver these.
my question workflow , how guys handle sort
of thing.
how handle major upgrades site while leaving client's
live site untouched , giving them way view new changes?
-kirk
we have 3 dreamweaver programs here. have 1 internal server, 1
external web server , client's web server.
here's how work:
on our internal server create multiple folders website:
artist1_webiste_ourserver
artist1_website_theirserver
artist2_webiste_ourserver
artist2_website_theirserver
artist3_webiste_ourserver
artist3_website_theirserver
the theirserver folder linked via dreamweaver client's live
website server. check-in/out enabled in dreamweaver.
that works fine , dreamweaver doesn't choke on permissions issues.
here's run trouble:
client has major changes need approved before going live.
we use ourserver these.
my question workflow , how guys handle sort
of thing.
how handle major upgrades site while leaving client's
live site untouched , giving them way view new changes?
-kirk
make 3 dreamweaver programmers not programs.
w. kirk lutz wrote:
> wanted pick brains out there.
>
> have 3 dreamweaver programs here. have 1 internal server, 1
> external web server , client's web server.
>
> here's how work:
> on our internal server create multiple folders website:
> artist1_webiste_ourserver
> artist1_website_theirserver
> artist2_webiste_ourserver
> artist2_website_theirserver
> artist3_webiste_ourserver
> artist3_website_theirserver
>
> theirserver folder linked via dreamweaver client's live
> website server. check-in/out enabled in dreamweaver.
>
> works fine , dreamweaver doesn't choke on permissions issues.
>
> here's run trouble:
>
> client has major changes need approved before going live.
> use ourserver these.
>
> question workflow , how guys handle sort
> of thing.
>
> how handle major upgrades site while leaving client's
> live site untouched , giving them way view new changes?
>
> -kirk
w. kirk lutz wrote:
> wanted pick brains out there.
>
> have 3 dreamweaver programs here. have 1 internal server, 1
> external web server , client's web server.
>
> here's how work:
> on our internal server create multiple folders website:
> artist1_webiste_ourserver
> artist1_website_theirserver
> artist2_webiste_ourserver
> artist2_website_theirserver
> artist3_webiste_ourserver
> artist3_website_theirserver
>
> theirserver folder linked via dreamweaver client's live
> website server. check-in/out enabled in dreamweaver.
>
> works fine , dreamweaver doesn't choke on permissions issues.
>
> here's run trouble:
>
> client has major changes need approved before going live.
> use ourserver these.
>
> question workflow , how guys handle sort
> of thing.
>
> how handle major upgrades site while leaving client's
> live site untouched , giving them way view new changes?
>
> -kirk
More discussions in Dreamweaver support forum
adobe
Comments
Post a Comment