ViewVC - Version Control Browser Interface
ViewVC is a browser interface for CVS and Subversion version control repositories. It generates templatized HTML to present navigable directory, revision, and change log listings. It can display specific versions of files as well as diffs between those versions. Basically, ViewVC provides the bulk of the report-like functionality you expect out of your version control tool, but much more prettily than the average textual command-line program output.
- Support CVS and Subversion repositories.
- Filesystem-accessible CVS repositories (with limited CVSNT support).
- Filesystem-accessible and remote Subversion repositories.
- Path-based authorization, including Subversion access file support.
- Template-driven output generation.
- Line-based annotation/blame display.
- Syntax highlighting support.
- Colorized, side-by-side differences.
- Revision graph capabilities (via integration with
cvsgraph) (CVS only).
- Individually configurable virtual host support.
- Tarball generation.
- By tag/branch for CVS.
- By revision and (sub)directory for Subversion.
- Optional commits database and query interface.
- Supports file-based commits for both CVS and Subversion.
- RSS feed generation for committed changes.
- Localization support based on the Accept-Language request header.
- Regexp-based file filtering.
- Ability to run either as CGI script or as a standalone server.
- File-based configuration (no code tweaks required)!
The only hard software requirement for running ViewVC is a suitable version of Python. The specifics of that, as well as all other requirements, depend on what you want to do with the tool. As those have changed somewhat over the years, it's best to consult the INSTALL file of the specific ViewVC release you wish to evaluate for its exact requirements. Here are pointers to the INSTALL files for the current major release lines:
Un-official nightly builds are available at http://viewvc.org/nightly/
We've tried to ensure that ViewVC URLs are stable, and that even when we deprecate a particular URL syntax, we continue to support the handling of it (using HTTP redirects to point browsers to the new form of that URL). We know that ViewVC URLs get bookmarked, and nobody likes when their bookmarked URLs suddenly stop working.
Across patch releases of ViewVC (when only the Z component of version X.Y.Z changes), we do our best to avoid configuration file changes that would modify the behavior of existing ViewVC installations. For example, we may add new configuration options, but their default values will cause no change in behavior. Likewise, we may add new template data dictionary variables, but will not require their use in existing templates or modify the behavior of previously existing data dictionary items. This makes it much easier for folks who need to upgrade quickly to get security or other bug fixes. That said, across major and minor releases, all bets are off, and chances are good that we've done some major plumbing. When upgrading your ViewVC instance across major or minor version numbers, you'll almost certainly want to consult the "Upgrading HOWTO" document in the
docs/ directory of the release archive for tips on how to migrate your configuration files and any template customizations you've made into their new formats.
Some notes for contributing to ViewVC's source code are include in our HACKING.md document.
Questions or Concerns?
Feel free to use our Issue Tracker to ask questions, make feature requests, report bugs, etc. In yesteryear, we had mailing lists for this kind of thing, but those have been discontinued.
ViewVC Docker Images
GitHub user @cmanley has graciously assembled Docker images for running ViewVC. See his work at https://github.com/cmanley/viewvc-docker.
Copyright © 1999-2020 The ViewCVS Group. All rights reserved.
By using ViewVC, you agree to the terms and conditions set forth below:
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.