Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to firstname.lastname@example.org.
ok, maybe I wasn't clear enough about my setup. I am of course, the only user of my sandbox (btw, what would be the point of having several users using the same sandbox instead of several sandboxes ?). Actually, I am for the moment the only user of this repository. The point to put this sandbox on a network shared drive is that it's actually hosted by my samba/apache linux server and the apache server can access my sandbox files (most of them are .php or .html) directly. When you deal with web developpment, you spend a lot of time adding/fixing visual effects in your html code and you'd like to see the results often and quickly through you web browser accessing your web server. For instance, let's say you're building an html table with some column widths to adjust. You would do something like that : 1. Edit your html file in your sandbox (table.html for instance). 2. Save it 3. Go to your browser window and render your modified html file (Shit-Ctrl-R for instance). Here, the browser is accessing the web server (because there may be some dynamic stuff in your code). The URL is something like http://mywebserver/mysandbox/table.html. 4. See the result 5. If something is to be adjusted, go back to 1. You may have to do that 2 or 3 times a minute ! So I don't think that to commit the files between stages 2. and 3. (as I read it in a previous thread) is an acceptable solution since it takes a lot of time compared to the time consumed by the other stages. And I also think that it would also 'pollute' the CVS repository by putting some potential broken files in it (your working html file could contain typos, your php files may not even compile, ...). But I understand that this may not be a problem for some users because tags can help dealing with that. Once again, the point of a shared drive sandbox is not to share the sandbox with other users, but to make it accessible to the web browser. Hope this could clarify my needs. -Patrick Bo Berglund wrote: > On Wed, 18 Jun 2003 16:02:41 +0000 (UTC), patrick.olinet at ard.fr > (Patrick Olinet) wrote: > > ... > >>- I think it's a common setup, specially when you deal with web >>developpment and you want your remote web server to access your sandbox >>web files (in my case, my web server is also on my linux box). To put a >>web server locally on the Windows machine isn't a solution since it >>requires you to duplicate its installation/configuration for each web >>developper. It could be a lot of work and that's too error-prone. >> > > ... > I fear that what you write also implies that there are several > developers who access the same sandbox (why would it otherwise be an > issue with the web server configuration). This is a really big > security hole in my mind and should never happen. > > > /Bo > (Bo Berglund, developer in Sweden)