Opened 18 years ago
Closed 18 years ago
#4066 closed defect (worksforme)
is-it-possible-to-disable-the-version-control-component (no)
Reported by: | paul at m.e.i. dot net | Owned by: | Jonas Borgström |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | version control | Version: | 0.10 |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
This doesn't seem to actually do anything.
http://trac.edgewall.org/wiki/TracFaq#is-it-possible-to-disable-the-version-control-component
Setting the svn dir to /dev/null is rather problematic when you issue the initenv, as it generates a horrible looking error, but otherwise seems to init the env ok.
However, even after adding the the version*=disabled code from that wiki entry, the timeline is still broken with a "/dev/null does not appear to be a Subversion repository" and I was rather hoping the browse source button would disappear alltogether.
I'm not very good at python, but having perused the code, I can't see where there are any self.config.get()s that go anywhere near components/versioncontrol in any file in the trac install.
Attachments (0)
Change History (2)
comment:1 by , 18 years ago
comment:2 by , 18 years ago
Component: | general → version control |
---|---|
Resolution: | → worksforme |
Status: | new → closed |
Paul, the advice to use /dev/null was wrong (I just fixed the FAQ). You should simply leave the field blank when creating a new environment, i.e. don't specify any path, and all should be well.
To fix your specific setup, go in your trac.ini file and set the repository_dir
entry to empty, like that:
[trac] repository_dir =
Actually, the solution to most of this is to this is to add "and restart apache if you're using fcgi or the like" to the wiki entry … Sorry I'm not usually a moron.
Though trac-admin still generates the heinous error if you set the repository to devnull in any case.