RE: [Sandweb-devel] SandWeb usage

[Alex R. <al...@un...>]

Robert,

1. Regarding working with pserver and being able to see users different
from www user, I managed to make SandWeb to work properly when I
specified username:password in the username field in repository
configuration and left the original password blank and marked "remember
password" checkbox.
I think you can add :$vcs_password after $vcs_username when you are
creating the CVSROOT variable.

       elsif ( $connection eq 'pserver' ) {
                $root = ":pserver:$vcs_username\@$server:$root";
                $vcs = 1;

2. Regarding the rest of the issues, we are going to write the callback
scripts and will send you after we are done.

Thanks.

-----Original Message-----
From: Robert Helmer [mailto:ro...@ro...] 
Sent: Tuesday, December 28, 2004 11:34 PM
To: al...@un...
Cc: san...@li...
Subject: Re: [Sandweb-devel] SandWeb usage

al...@un... wrote:

>1. Pre/Post triggers. I need the ability to modify files before actual
>commit and after checkout (before the file is actualy downloaded from
>sandbox area). The sandbox area is really irrelevant - I want to
download
>all files to client PC and work on them there. That's why I thought of
>modifying download/upload methods in File.pm. The cvs -t/-f wrappers
>supportsuch a functionality but they were disabled in current version
of
>cvs due to bug found theie implementation. The CodeFab project has some
old
>version of cvs with -t/-f support but it is not good enough becuase
there
>is no error handling.
>
>  
>

Yes I agree that CVS's support for triggers is rather weak. I would not 
object to doing this in SandWeb, I tossed around similar ideas before, 
when I used to work with a larger programming team.

>2. Regarding the complete project downloading - I mean downloading
project
>files to client PC and not to repository, currently I can download only
>file by file by clicking on download link after entering each file. I
want
>to download the complete repository to client PC by one click.
>
>  
>

There is some experimental code in the SandWeb CVS repository that 
supports downloading the whole
checkout as a TAR file. It could use testing, and should release with 
the next SandWeb version. There is no projected date for the next 
release right now. This feature could be implemented pretty trivially on

the release branch as well.

>3. Regarding the user access registration. I do not want to open unix
user
>for every developer, I prefer maintaining them in CVSROOT/passwd file
or by
>SandWeb native user management. I saw that setting CVSUSER environment
>variable can solve the problem. Can you set this variable in cvs.pm
before
>invoking the cvs commands?
>  
>

I have not tried it, although it sounds like it could be an acceptable 
way of dealing with that issue (I agree that having the Apache user be 
responsible for all checkins is not good; I have considered outright 
dropping non-SSH support over this issue but some people seem to use it,

and I see use local repositories sometimes too). I prefer to use the 
system authentication because I consider CVS's mechanisms (such as 
pserver) too weak to use (for example: storing passwords in ~/.cvspass, 
no encryption, weak password file).

>4. Another issue: if the text file is very big, the file preview take a
lot
>of time. As a workaround - I modified the template file and changed
>TMPL_VAR to TMPL_IF statement. I think we should have  some engine to
>allow/disalow preview of files based on their extensions.
>  
>

Currently, SandWeb uses the Unix "file" command to determine if a file 
appears to be text or binary, and the preview is done based on that. 
Perhaps there should be a file size limit too? I can't think of a good 
way to use file extensions in this case; can you elaborate?


Thanks,
Rob