Local site folder on shared network volume - why not?

There are the following comments listed under a
http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_15361&sliceId=1

[Q]> Do not use a local root folder located on a local network.

Your local root folder should not be shared or on a mounted drive.[/Q]

But it doesn't say why..

I would have thought this could be a good idea for companies where multiple
people may be working on a large site. You could still use check-in, check-out
couldn't you?

All of my local sites are on a shared network drive. It's not such a
problem....

--
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
==================


"Alan" <please_dont_mail_me (AT) example (DOT) com> wrote

Your local root folder should not be shared or on a mounted drive.[/Q]

But it doesn't say why..

time and transfer speed for one thing.
Any sitewide operation would be slowed down. Find and Replace, folder list
refresh, and so on. Ten seconds to ten minutes or worse to get the cursor
back to where you had clicked it.


I would have thought this could be a good idea for companies where
multiple
people may be working on a large site. You could still use check-in,
check-out
couldn't you?

checkin/checkout in dw relies on each user having their OWN local site
folder. You request to check out a file. The common remote has a .LCK file
that says that YOU have checked out that file to your local site file so
YOU
can work on it. A group of users defining a common network folder as the
local site location for all of them will not work.

Checkin/checkout is just a dreamweaver thing. It creates mostly invisible
.LCK lock files in the local and remote site locations. If each user has
set up a Local Site Folder on their own machine and a remote that is
shared
is shared with other users, it will work. If the Local Site Folder is a
network location that other users have also defined as THEIR Local Site
Folder the dreamweaver checkin/checkout option will fail in locking out
people from changing a file that someone else already has open.

short version:
If you have a bunch of folks working on live files, somebody has to sort
out
a version control system. They can cost money but prevent losing things.
The
dw checkin/checkout is a bit primitive and can prevent errors when
properly
set up and there a couple of people. It will not prevent a bunch of people
with access from screwing things up.
And if any of them have set up an "RDS" live editing connecting in
dreamweaver, or is are not using macromedia/adobe software that looks for
the .LCK lock files, it fails.

--
Alan
Adobe Community Expert, dreamweaver

http://www.adobe.com/communities/experts/

All of my local sites are on a shared network drive. It's not such a
problem....

--
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
==================


"Alan" <please_dont_mail_me (AT) example (DOT) com> wrote

Your local root folder should not be shared or on a mounted drive.[/Q]

But it doesn't say why..

time and transfer speed for one thing.
Any sitewide operation would be slowed down. Find and Replace, folder list
refresh, and so on. Ten seconds to ten minutes or worse to get the cursor
back to where you had clicked it.


I would have thought this could be a good idea for companies where
multiple
people may be working on a large site. You could still use check-in,
check-out
couldn't you?

checkin/checkout in dw relies on each user having their OWN local site
folder. You request to check out a file. The common remote has a .LCK file
that says that YOU have checked out that file to your local site file so
YOU
can work on it. A group of users defining a common network folder as the
local site location for all of them will not work.

Checkin/checkout is just a dreamweaver thing. It creates mostly invisible
.LCK lock files in the local and remote site locations. If each user has
set up a Local Site Folder on their own machine and a remote that is
shared
is shared with other users, it will work. If the Local Site Folder is a
network location that other users have also defined as THEIR Local Site
Folder the dreamweaver checkin/checkout option will fail in locking out
people from changing a file that someone else already has open.

short version:
If you have a bunch of folks working on live files, somebody has to sort
out
a version control system. They can cost money but prevent losing things.
The
dw checkin/checkout is a bit primitive and can prevent errors when
properly
set up and there a couple of people. It will not prevent a bunch of people
with access from screwing things up.
And if any of them have set up an "RDS" live editing connecting in
dreamweaver, or is are not using macromedia/adobe software that looks for
the .LCK lock files, it fails.

--
Alan
Adobe Community Expert, dreamweaver

http://www.adobe.com/communities/experts/

We would like to have multiple people set up their local site on a shared
network volume (our development server) so we can synchronize with the
production server. Aside from the fact that checkin/checkout do not work
properly without unique local sites, are there other reasons we should not set
up a local site on a shared network volume? Will synchronization still work
properly, even if multiple people are editing on the "local" network copy?

Is that local site protected by any version control environment like
Subversion? If so, then I think you are safe. If not then I think you are
taking a big big risk.

Synchronization will still work, although you may not get what you are
expecting to get if a page is being actively edited?

--
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
==================


"pdrich" <webforumsuser (AT) macromedia (DOT) com> wrote

We would like to have multiple people set up their local site on a shared
network volume (our development server) so we can synchronize with the
production server. Aside from the fact that checkin/checkout do not work
properly without unique local sites, are there other reasons we should not
set
up a local site on a shared network volume? Will synchronization still
work
properly, even if multiple people are editing on the "local" network copy?

Thanks for the feedback. We currently allow editing on the development server
directly by multiple users, and we manually copy the files to production as
needed. We all have the development server's network drive as our local copy,
but we do not sync files with a remote copy within DW.

The difference would be that we'd like to use DW's synchronization to put the
edited files onto the production server (as our remote server). The change
will be to define the production server as the remote site on each person's DW
site to allow them to sync with production.

Common risks of concurrent editing aside, are there known issues with
synchronizing in DW using this approach?

Murray,

You said that you have your local files on a networked drive. What do you use
for your testing server? I set up apache on my c: drive and I have to have the
virtual host on my c: drive as apache can't access a networked drive. I'm
curious how you are set up for testing your stuff?

Mike

I'm
curious how you are set up for testing your stuff?

My production machine is Vista Business. My testing server is on a
networked *nix box (Ubuntu), mapped to the production machine as drive U:.
I'm running PHP/MySQL/Apache on that box, along with the virtual hosts.
It's a tiny bit awkward, but very functional....

--
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
==================


"Mike-H" <webforumsuser (AT) macromedia (DOT) com> wrote

Murray,

You said that you have your local files on a networked drive. What do you
use
for your testing server? I set up apache on my c: drive and I have to have
the
virtual host on my c: drive as apache can't access a networked drive. I'm
curious how you are set up for testing your stuff?

Mike