LoggerHead : Is there any way to block users from downloading files from the repository

Asked by Vijaya Kumar

Any way to block users from downloading file from the repository using LoggerHead?
We need some control on it, since it is open to all and everyone can download all project files.

Option 1) Team1 should be able to download all files and Team2 shouldn't see the download option.
Option 2) Disable the download option for all.

FYI., i dont want to do this in apache by giving additional login credentials for users

Question information

Language:
English Edit question
Status:
Answered
For:
loggerhead Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Matthew Revell (matthew.revell) said :
#1

Hi,

Are you talking about running your own local instance of Loggerhead?

Revision history for this message
Vijaya Kumar (vijayakumar-cm) said :
#2

yes.. I'm running this loggerhead on my project.
It has several repositories and everyone can access all of those. Issue is everyone can also download those project files, so i want them to protect from downloading all files..

Is there any option just to restrict the download files option via logger head?

Revision history for this message
Martin Pool (mbp) said :
#3

Not at present. You could patch loggerhead to add this, or you can just
block people from the whole repository.

Revision history for this message
Francis J. Lacoste (flacoste) said :
#4

That's not directly related to Loggerhead, but there is sloecode that allows you to set up ACL on bazaar repositories:
http://how-bazaar.blogspot.com/2011/03/announcing-sloecode.html

Revision history for this message
Vijaya Kumar (vijayakumar-cm) said :
#5

how exactly this option (--prefix) works ?

I run this command - ./serve-branches --port=8080 --prefix=/loggerhead /bzr

I'm able to open loggerhead in - http://host.com:8080/

Revision history for this message
Martin Pool (mbp) said :
#6

.. cmdoption:: --prefix

    Set the supplied value as the CGI ``SCRIPT_NAME`` for the application.

    This option is intended for use when serving Loggerhead behind a
    reverse proxy, with Loggerhead being "mounted" at a directory below
    the root. E.g., if the reverse proxy translates requests for
    ``http://example.com/loggerhead`` onto the standalone Loggerhead process,
    that process should be run with ``--prefix=/loggerhead``.

Can you help with this problem?

Provide an answer of your own, or ask Vijaya Kumar for more information if necessary.

To post a message you must log in.