Modify ↓
#1350 closed enhancement (duplicate)
SVN Decouple
| Reported by: | Owned by: | Jonas Borgström | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | general | Version: | 0.8.1 |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description (last modified by )
Currently Trac does not support remote svn repositories. It lists within the trac-admin tool that this is because the admin requires access to svn.
Why then cant we decouple the svn repo with our project files? Then we can have a small svn repo for the wiki/ticket information and another for the actual project files.
Along with decoupling the svn repo will you guys consider adding the ability to connect to a remote svn repository?
Attachments (0)
Change History (2)
comment:1 by , 20 years ago
| Description: | modified (diff) |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
comment:2 by , 20 years ago
| Description: | modified (diff) |
|---|
Well, actually support for remote repos access it tracked by #493.
Note:
See TracTickets
for help on using tickets.
Trac doesn't actually store any data in the SVN repos. Tickets and wiki pages are stored in an SQLite database.
Support for remote SVN repositories is already tracked by #1350.