headers
Taylor Dondich | 5 Aug 20:44

Chora doesn't show CVS repo files, only directories

I successfully installed Horde and Chora (latest release versions), and 
setup the sourceroot file properly to point to a repository directory 
where the webserver user has complete access to it (it owns it).

When I start chora, I can see all the directories, but no files show up 
in the repository.

I've made sure all the paths are setup in chora (via Horde's admin 
setup), am I missing something?

Taylor
--

-- 
Chora mailing list - Join the hunt: http://horde.org/bounties/#chora
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: chora-unsubscribe <at> lists.horde.org
Permalink | Reply | 1 comment |
headers
Jan Schneider | 5 Aug 20:56
Favicon
Gravatar

Re: Chora doesn't show CVS repo files, only directories

Zitat von Taylor Dondich <tdondich <at> itgroundwork.com>:

> I successfully installed Horde and Chora (latest release versions), and
> setup the sourceroot file properly to point to a repository directory
> where the webserver user has complete access to it (it owns it).
>
> When I start chora, I can see all the directories, but no files show up
> in the repository.

Are you sure you are runnig chora against a repository, not a checkout?

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/

--

-- 
Chora mailing list - Join the hunt: http://horde.org/bounties/#chora
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: chora-unsubscribe <at> lists.horde.org
Permalink | Reply | 0 comments |
headers
Augie Schwer | 9 Aug 01:28
Picon
Gravatar

Access Control for seperate source roots?


Subversion allows you with the AuthzSVNAccessFile directive to specify an
ACL; allowing you to define users and groups and permissions on individual
repositories based on that list.

Is there a Chora config option to have my SVN auth. access file be read in and
honored? Or is there a different way to do the same thing within the existing
Chora constructs?

Basically I have two groups; Programming and Operations, and two repositories;
prog and ops, and I want Programming to be able to view the prog repository, 
but not the ops repository, and I want Operations to be able to view both 
repositories.

Any hints?

Augie.

--

-- 
Registered Linux user #229905
GPG Public Key: http://www.schwer.us/schwer.asc
Key fingerprint = 9815 AE19 AFD1 1FE7 5DEE 2AC3 CB99 2784 27B0 C072
Permalink | Reply | 2 comments |
headers
Jan Schneider | 10 Aug 16:45
Favicon
Gravatar

Re: Access Control for seperate source roots?

Zitat von Augie Schwer <augie.schwer <at> gmail.com>:

> Subversion allows you with the AuthzSVNAccessFile directive to specify an
> ACL; allowing you to define users and groups and permissions on individual
> repositories based on that list.
>
> Is there a Chora config option to have my SVN auth. access file be 
> read in and
> honored? Or is there a different way to do the same thing within the existing
> Chora constructs?

config/sourceroots.php is a PHP file, so you can add permission 
checking around the sourceroot definitions.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/

--

-- 
Chora mailing list - Join the hunt: http://horde.org/bounties/#chora
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: chora-unsubscribe <at> lists.horde.org
Permalink | Reply | 1 comment |
headers
Augie Schwer | 16 Aug 19:47
Picon
Gravatar

Re: Access Control for seperate source roots?


On 8/10/05, Jan Schneider <jan <at> horde.org> wrote:
> Zitat von Augie Schwer <augie.schwer <at> gmail.com>:
> > Subversion allows you with the AuthzSVNAccessFile directive to specify an
> > ACL; allowing you to define users and groups and permissions on individual
> > repositories based on that list.
> > Is there a Chora config option to have my SVN auth. access file be
> > read in and
> > honored? Or is there a different way to do the same thing within the existing
> > Chora constructs?
> config/sourceroots.php is a PHP file, so you can add permission
> checking around the sourceroot definitions.

Trac (http://www.edgewall.com/trac/) supports this:

http://projects.edgewall.com/trac/wiki/FineGrainedPermissions

so I am going to start poking at that; thanks.

Augie.

--

-- 
Registered Linux user #229905
GPG Public Key: http://www.schwer.us/schwer.asc
Key fingerprint = 9815 AE19 AFD1 1FE7 5DEE 2AC3 CB99 2784 27B0 C072
Permalink | Reply | 0 comments |
headers
Jan Schneider | 29 Aug 22:05
Favicon
Gravatar

Chora H3 (2.0.1-RC1)

The Horde Team is pleased to announce the first release candidate of the Chora
Repository Viewer version H3 (2.0.1).

Chora is built upon the Horde Application Framework and provides a read-only
browser interface to any number of version control repositories.  Advanced
features include a visual branch view of the repository's history,
pretty-printed output, annotation, patchsets and basic statistics.

Barring any problems, this code will be released as Chora H3 (2.0.1).
Testing is requested and comments are encouraged.
Updated translations would also be great.

Major changes compared to the Chora version H3 (2.0) are:
    * Fixed mime type detection using the PHP fileinfo extension.
    * Added Russian translation.
    * Updated Brazilian Portuguese, Finnish, German, and Norwegian
      translations.

The full list of changes (from version H3 (2.0)) can be viewed here:

http://cvs.horde.org/diff.php/chora/docs/CHANGES?r1=1.100&r2=1.100.2.6&ty=h

The Chora H3 (2.0.1-RC1) distribution is available from the following locations:

    ftp://ftp.horde.org/pub/chora/chora-h3-2.0.1-rc1.tar.gz
    http://ftp.horde.org/pub/chora/chora-h3-2.0.1-rc1.tar.gz

Patches against version H3 (2.0) are available at:

    ftp://ftp.horde.org/pub/chora/patches/patch-chora-h3-2.0-h3-2.0.1-rc1.gz
(Continue reading)

Permalink | Reply | 0 comments |

Gmane