Re: Sharing /usr/local/www
Kyrre Nygard wrote: At 10:45 27.05.2006, Beech Rintoul wrote: On Saturday 27 May 2006 00:32, Kyrre Nygard wrote: Hello! I have a team of designers working on web 2.0 like sites. I have added them all to this box, now I'm wondering what's the most convenient way of giving them all access to /usr/local/www? My temporary solution has been to add all users with UID and GID 80, and then ln -s /usr/local/www ~/collabo for each user. If users have their original UID instead of www's then somehow they can't read or write to /usr/local/www. I thought sharing the same GID was sufficient, but obviously it isn't. I find this very strange. Some of them prefer just using FTP, so then being able to click on collabo@ and go straight to /usr/local/www is very convenient for them. But is there a better way? Thanks, Kyrre CVS is your friend. But there are also a ton of php scripts out there to do what you want. Beech -- Yeah I hear a lot of people like CVS. But I fail to realize how it might assist me though. I'm not setting up a code repository, this is an actual WWW root where a lot of different websites are hosted. Please correct me if I'm wrong. And what PHP scripts are you talking about? Thanks a lot, Kyrre ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I think the easiest way would be to add them all to a similar group (www, perhaps) and chown -R user:group /usr/local/www; chmod -R g+rw /usr/local/www This will give whatever group you specify read, and write access to the directory. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sharing /usr/local/www
At 11:50 27.05.2006, Daniel A. wrote: Hi Kyrre. Have you tried chmodding the www dir to be group-writable? Also, as someone else has suggested, SVN og CVS might be a good idea. They would not solve the problem you have right now, but they might help you avoid some possible problems with many people editing the same batch of files - sharing violations. What if two people start editing the same files on their own workstations, and both upload the changes? What about version control? et cetera, ad nauseam. Offcourse, non-repository development is possible, and I've done it myself without any issues whatsoever, but you're the one who decides what's best for your development. Actually no I did not chmod www to be group writable. Silly me! :) But I'm wondering. If I were to use SVN for my www, wouldn't I then in reality have two different wwws, one for SVN and one which I later export for Apache? This is what confuses me a little ... Thanks a lot, Kyrre ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sharing /usr/local/www
Kyrre Nygard wrote: At 11:50 27.05.2006, Daniel A. wrote: Hi Kyrre. Have you tried chmodding the www dir to be group-writable? Also, as someone else has suggested, SVN og CVS might be a good idea. They would not solve the problem you have right now, but they might help you avoid some possible problems with many people editing the same batch of files - sharing violations. What if two people start editing the same files on their own workstations, and both upload the changes? What about version control? et cetera, ad nauseam. Offcourse, non-repository development is possible, and I've done it myself without any issues whatsoever, but you're the one who decides what's best for your development. Actually no I did not chmod www to be group writable. Silly me! :) But I'm wondering. If I were to use SVN for my www, wouldn't I then in reality have two different wwws, one for SVN and one which I later export for Apache? That is exactly how it does work ;) This is what confuses me a little ... Thanks a lot, Kyrre ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sharing /usr/local/www
* Kyrre Nygard [EMAIL PROTECTED] [2006-05-27 11:12:19 +0200]: I have a team of designers working on web 2.0 like sites. I have added them all to this box, now I'm wondering what's the most convenient way of giving them all access to /usr/local/www? CVS is your friend. Yeah I hear a lot of people like CVS. But I fail to realize how it might assist me though. Kyrre, CVS is a version control tool. A version control tool manages changes to information, sometimes among multiple people. It sounds like to me like you really need a version control tool for what you want to do. CVS is a good choice for this, Subversion is better. Yes, there might be scripts that accomplish this, but most (good) version control tools will: - allow you to manage changes to data over time - remember every change ever made to your data, allowing you to recover older versions, or see the history of how it changed - allow access across networks, which allows it to be used by people on different computers - give you the ability for various people to modify and manage (i.e. collaborate on) the same set of data from their respective locations (The above was paraphrased from Version Control with Subversion, by Collins-Sussman, Fitzpatrick, and Pilato, v1.2, Ch 1.) You will run into this problem over and over again. Do yourself a favor and learn how to use a good version control system now, or else you will find yourself doomed to reinvent it, poorly. (Apologies to H. Spencer.) Thomas -- N.J. Thomas [EMAIL PROTECTED] Etiamsi occiderit me, in ipso sperabo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sharing /usr/local/www
On Saturday 27 May 2006 01:12, Kyrre Nygard wrote: At 10:45 27.05.2006, Beech Rintoul wrote: On Saturday 27 May 2006 00:32, Kyrre Nygard wrote: Hello! I have a team of designers working on web 2.0 like sites. I have added them all to this box, now I'm wondering what's the most convenient way of giving them all access to /usr/local/www? My temporary solution has been to add all users with UID and GID 80, and then ln -s /usr/local/www ~/collabo for each user. If users have their original UID instead of www's then somehow they can't read or write to /usr/local/www. I thought sharing the same GID was sufficient, but obviously it isn't. I find this very strange. Some of them prefer just using FTP, so then being able to click on collabo@ and go straight to /usr/local/www is very convenient for them. But is there a better way? Thanks, Kyrre CVS is your friend. But there are also a ton of php scripts out there to do what you want. Beech -- Yeah I hear a lot of people like CVS. But I fail to realize how it might assist me though. I'm not setting up a code repository, this is an actual WWW root where a lot of different websites are hosted. Please correct me if I'm wrong. And what PHP scripts are you talking about? Thanks a lot, Kyrre Take a look at http://www.hotscripts.com there is a lot of stuff in there for dealing with multiple users (some commercial, some not). Ultimately if you're doing that level of hosting you'll probably want something like cpanel, but cpanel itself is very pricey. Beech -- --- Beech Rintoul - Sys. Administrator - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | Alaska Paradise \ / - NO HTML/RTF in e-mail | 201 East 9Th Avenue Ste.310 X - NO Word docs in e-mail | Anchorage, AK 99501 / \ - Please visit Alaska Paradise - http://www.alaskaparadise.com --- pgp2ZNOCgp6qs.pgp Description: PGP signature
Re: Sharing /usr/local/www
On Saturday 27 May 2006 01:12, Kyrre Nygard wrote: Yeah I hear a lot of people like CVS. But I fail to realize how it might assist me though. I'm not setting up a code repository, this is an actual WWW root where a lot of different websites are hosted. Please correct me if I'm wrong. You are wrong. CVS is a version control system. It's often used to control software development, but can be used to control any kind of text(*) document development. --Alex (*) You can store binary files as well, but it is less efficient when they change as it cannot keep diffs, just complete changed files. OK for reasonable sized gifs/jpegs etc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sharing /usr/local/www
On Saturday 27 May 2006 00:32, Kyrre Nygard wrote: Hello! I have a team of designers working on web 2.0 like sites. I have added them all to this box, now I'm wondering what's the most convenient way of giving them all access to /usr/local/www? My temporary solution has been to add all users with UID and GID 80, and then ln -s /usr/local/www ~/collabo for each user. If users have their original UID instead of www's then somehow they can't read or write to /usr/local/www. I thought sharing the same GID was sufficient, but obviously it isn't. I find this very strange. Some of them prefer just using FTP, so then being able to click on collabo@ and go straight to /usr/local/www is very convenient for them. But is there a better way? Thanks, Kyrre CVS is your friend. But there are also a ton of php scripts out there to do what you want. Beech -- --- Beech Rintoul - Sys. Administrator - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | Alaska Paradise \ / - NO HTML/RTF in e-mail | 201 East 9Th Avenue Ste.310 X - NO Word docs in e-mail | Anchorage, AK 99501 / \ - Please visit Alaska Paradise - http://www.alaskaparadise.com --- pgpTvuAh9eagI.pgp Description: PGP signature
Re: Sharing /usr/local/www
At 10:45 27.05.2006, Beech Rintoul wrote: On Saturday 27 May 2006 00:32, Kyrre Nygard wrote: Hello! I have a team of designers working on web 2.0 like sites. I have added them all to this box, now I'm wondering what's the most convenient way of giving them all access to /usr/local/www? My temporary solution has been to add all users with UID and GID 80, and then ln -s /usr/local/www ~/collabo for each user. If users have their original UID instead of www's then somehow they can't read or write to /usr/local/www. I thought sharing the same GID was sufficient, but obviously it isn't. I find this very strange. Some of them prefer just using FTP, so then being able to click on collabo@ and go straight to /usr/local/www is very convenient for them. But is there a better way? Thanks, Kyrre CVS is your friend. But there are also a ton of php scripts out there to do what you want. Beech -- Yeah I hear a lot of people like CVS. But I fail to realize how it might assist me though. I'm not setting up a code repository, this is an actual WWW root where a lot of different websites are hosted. Please correct me if I'm wrong. And what PHP scripts are you talking about? Thanks a lot, Kyrre ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sharing /usr/local/www
Kyrre Nygard wrote: Hello! I have a team of designers working on web 2.0 like sites. I have added them all to this box, now I'm wondering what's the most convenient way of giving them all access to /usr/local/www? My temporary solution has been to add all users with UID and GID 80, and then ln -s /usr/local/www ~/collabo for each user. If users have their original UID instead of www's then somehow they can't read or write to /usr/local/www. I thought sharing the same GID was sufficient, but obviously it isn't. I find this very strange. Some of them prefer just using FTP, so then being able to click on collabo@ and go straight to /usr/local/www is very convenient for them. But is there a better way? Thanks, Kyrre ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Hi Kyrre. Have you tried chmodding the www dir to be group-writable? Also, as someone else has suggested, SVN og CVS might be a good idea. They would not solve the problem you have right now, but they might help you avoid some possible problems with many people editing the same batch of files - sharing violations. What if two people start editing the same files on their own workstations, and both upload the changes? What about version control? et cetera, ad nauseam. Offcourse, non-repository development is possible, and I've done it myself without any issues whatsoever, but you're the one who decides what's best for your development. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
