it would seem that the directory /project/bese/ftr is not getting copied over to $PUBLICFTP/pub/project/bese. -- -Marco Ring the bells that still can ring. Forget your perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen
Maybe /var/ftp/pub/project/<name< should be symlinks to /project/<name>/ftp, and likewise for public_html? Cheers, -- Nikodemus
Nikodemus Siivola <nikodemus@random-state.net> writes:
Maybe /var/ftp/pub/project/<name< should be symlinks to /project/<name>/ftp, and likewise for public_html?
You probably missed my other email: Ok, after popular demand, I have removed the cron approach to updating the www directories for the projects. /project/<project-name>/public_html is now being symlinked to from /var/www/project/<project-name> so any changes you make will be instant. I'm thinking about doing the same with FTP but that would mean I couldn't do the chroot anymore (unless I'm missing something) and I'm not sure we want to do that yet. Still not sure about that one. Perhaps I'm too cautious about security. If none of you get a bad feeling in your stomachs from running the FTP server without a chroot I'll go ahead and do it. Erik.
On Thu, Sep 11, 2003 at 05:11:01PM -0400, Erik Enge wrote:
You probably missed my other email:
I didn't. It must be taking the scenic route ... ;)
I'm thinking about doing the same with FTP but that would mean I couldn't do the chroot anymore (unless I'm missing something) and I'm not sure we want to do that yet.
Ah. Didn't think of chroot issues. What about doing it the other way around: /project/<name>/ftp -> /var/ftp/pub/project/<name>? Cheers, -- Nikodemus
Nikodemus Siivola <nikodemus@random-state.net> writes:
Ah. Didn't think of chroot issues. What about doing it the other way around: /project/<name>/ftp -> /var/ftp/pub/project/<name>?
Ah, didn't think of that. :) Ok, /project/<name>/ftp is a symlink to /var/ftp/pub/project/<name>. Is there anything more but a username you need now, Andreas? Erik.
Erik Enge <erik@nittin.net> writes:
Ah, didn't think of that. :) Ok, /project/<name>/ftp is a symlink to /var/ftp/pub/project/<name>.
/project/PROJECT directories are owned by the same group as the project members, this allows members to create files/directories in the project directories. I don't know if you want to allow this or not. /project/PROJECT/ftp is owned by ftp.nogroup (not the symlink, the actual directory) which makes it impossible for members of the project group to copy/delete files to/from the ftp directory. -- -Marco Ring the bells that still can ring. Forget your perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen
Marco Baringer <mb@bese.it> writes:
/project/PROJECT directories are owned by the same group as the project members, this allows members to create files/directories in the project directories. I don't know if you want to allow this or not.
I don't know. What do y'all think?
/project/PROJECT/ftp is owned by ftp.nogroup (not the symlink, the actual directory) which makes it impossible for members of the project group to copy/delete files to/from the ftp directory.
That's a bug. Fixed; thanks for reporting. Erik.
On Sat, Sep 13, 2003 at 08:16:19AM -0400, Erik Enge wrote:
/project/PROJECT directories are owned by the same group as the project members, this allows members to create files/directories in the project directories. I don't know if you want to allow this or not.
I don't know. What do y'all think?
Gut instinct: disallow everything unnecessary. ,) If nothing else, it will keep the directory structure clear, and if we decide to use "foo" as canonical directory for fnordification we can, without worrying about existing infratructure of non-std projects. The other alternative is to think of /project/<name> as the home-directory of each project, and promise them that things work as expected as long as they have public_html, ftp, etc, but otherwise let them play as they like in their own yard. ...the reason I'm a bit dubious about this is that this is morally equivalent to encouraging people to use the shell-account for actually doing stuff... Which brings me to a different topic: I've been using a few simple scripts to manage linedit things, and have been thinking about making them public after a bit of generalization, for the convenience of other Common-lisp.net users. ...but more on this later. ;) Cheers, -- Nikodemus
Nikodemus Siivola <nikodemus@random-state.net> writes:
On Sat, Sep 13, 2003 at 08:16:19AM -0400, Erik Enge wrote:
I don't know. What do y'all think?
Gut instinct: disallow everything unnecessary. ,) [...]
Agreed. It is easier to add later if it is needed, than to remove it if it causes trouble.
Which brings me to a different topic: I've been using a few simple scripts to manage linedit things, and have been thinking about making them public after a bit of generalization, for the convenience of other Common-lisp.net users. ...but more on this later. ;)
Sounds cool; let us know when you are ready... Regards, Mario.
On 2003-09-12, Erik Enge <erik@nittin.net> wrote:
Ah, didn't think of that. :) Ok, /project/<name>/ftp is a symlink to /var/ftp/pub/project/<name>. Is there anything more but a username you need now, Andreas?
That's great! I'd be interested in sftp, but that has time (: Ready when you are, -- Andreas Fuchs, <asf@acm.org>, asf@jabber.at, antifuchs
participants (5)
-
Andreas Fuchs -
Erik Enge -
Marco Baringer -
Mario Mommer -
Nikodemus Siivola