#156 closed enhancement (fixed)
Using Trac without subversion.
Reported by: | Jonas Borgström | Owned by: | Christian Boos |
---|---|---|---|
Priority: | normal | Milestone: | 0.10 |
Component: | version control | Version: | 0.5.2 |
Severity: | normal | Keywords: | |
Cc: | eric-trac@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
It should be possible to use Trac without having a subversion repository. The wiki and ticket system alone can be useful.
Attachments (1)
Change History (16)
comment:1 by , 20 years ago
comment:2 by , 20 years ago
Agree wholeheartedly! Without svn it would be excellent for sysadmins as a combined ticketing/documentation system.
comment:3 by , 20 years ago
What is proposed as the storage mechanism for the wiki, if not SVN? SQL? Stacks of diffs? CVS? I don't see how "not using SVN" will help as such.
Why not build up some scripts and a bundled SVN client/libraries, using the FSFS SVN backend? The idea here is to encapsulate SVN, and Berkley DB, to the point where they become irrelevant as entities. Does it really matter what happens "inside" a wiki?
If the wiki grows large enough to out grow a generic back end, then manage it as the full-blooded service it has become (Berkley DB, and the rest of it).
comment:4 by , 20 years ago
Subversion isn't being used to store the Wiki pages, they are stored in the SQLite database. Subversion is really only used in read-only mode, for providing views on the repositories.
comment:6 by , 20 years ago
Severity: | normal → enhancement |
---|
comment:7 by , 19 years ago
I did this with one Trac I set up because they were using Perforce as the version control system. So I just created an empty Subversion repository and point Trac at that. It was slightly annoying to have to set up Subversion on that machine and create an extra repository, but not that annoying.
comment:8 by , 19 years ago
Milestone: | 1.0 → 0.9 |
---|---|
Owner: | changed from | to
Status: | new → assigned |
The web_ui refactoring made it possible to disable the version control related modules, within the trac.ini file:
[disabled_components] trac.versioncontrol.web_ui = yes
What's left to be done is making the initialization
of the SVN repository optional in trac-admin
.
comment:10 by , 19 years ago
Cc: | added |
---|
comment:12 by , 19 years ago
Component: | general → version control |
---|
The current vc-refactoring branch (source:sandbox/vc-refactoring@2511) has this feature.
comment:13 by , 19 years ago
Milestone: | 0.9.1 → 0.9.2 |
---|
comment:14 by , 19 years ago
Milestone: | 0.9.3 → 1.0 |
---|---|
Resolution: | → fixed |
Status: | assigned → closed |
The vc-refactoring
branch has been merged in [2669], which allows Trac to be initialized without a Subversion repository. The specifics still need a bit of polish, but the basics are there now.
comment:15 by , 19 years ago
Milestone: | 1.0 → 0.10 |
---|
Definitely! I just wanted to replace bugzilla, not migrate my whole project to subversion. This is not modular.