Trac is an enhanced wiki and issue tracking system for software development projects (mirror)

Overview

About Trac

Trac is a minimalistic web-based software project management and bug/issue tracking system. It provides an interface to the Git and Subversion revision control systems, an integrated wiki, flexible issue tracking and convenient report facilities.

Trac is distributed using the modified BSD License.

  • For installation instructions, please see INSTALL.rst or the trac/wiki/default-pages/TracInstall page for complete, up-to-date instructions
  • If you are upgrading from a previous Trac version, please read UPGRADE.rst or the trac/wiki/default-pages/TracUpgrade page for complete, up-to-date instructions

You might also want to take a look at the RELEASE.rst and ChangeLog files for more information about this release.

Otherwise, the primary source of information is the main Trac web site:

<https://trac.edgewall.org/>

We hope you enjoy it,

/The Trac Team

Comments
  • Accept more general Basic Auth password file format

    Accept more general Basic Auth password file format

    The trac standalone can use Apache's htpasswd files for authentication. Although Apache creates an htpasswd file with format user:password, it understands files with additional components after those first two. For example, dokuwiki uses the format user:password:Real Name:email:groups to provide additional information on each user. Such a file also works with Apache and nginx HTTP Basic Auth; they just ignore the remaining fields. But tracd breaks, because it expects exactly two components.

    Perhaps more importantly, other tools respect comments in htpasswd. So, for example, if you want to disable user joey12, you can comment out that user's line by putting # in front. But tracd just processes that as #joey12, which could potentially allow a login under that name.

    This pull request adds the ability to handle those more general htpasswd file formats. It simply removes everything after a #, and then only takes the first two components of any remaining lines.

    [Technically, Apache only considers a line a comment if it begins with #; I think this behavior is safer for htpasswd files, especially since this makes it less likely that this function will dump passwords to the error log.]

    opened by moble 6
  • Trunk

    Trunk

    I would like to start getting some feedback on integrating this back into the main trunk. Here is what I have.

    • New batch modify module.
    • Batch modify UI integrated into query page.
    • New permission (TICKET_BATCH_MODIFY)
    • Added a new page to the TracGuide and updated the TOC macro.
    • Wrote tests against new module.

    I still have a couple of outstanding issues as well.

    • One of the new batch tests fails. Right now I think the problem is with the test itself. I cannot reproduce the error through a running Trac instance. I'm probably doing something wrong with the EnvironmentStub.
    • I don't have any tests on my query page integration. Are there any examples of permission testing I can look at? I want to test that batch data is only added when the user has the appropriate permission.
    • The documentation page I added to the wiki feels off. I don't feel like I'm explaining the configuration options in a clean way. Suggestions welcome.
    opened by CuriousCurmudgeon 5
  • mimeview/api: new config setting [mimeviewer] mime_map_patterns

    mimeview/api: new config setting [mimeviewer] mime_map_patterns

    Purpose: enable Trac to determine MIME types for syntax highlighting not just simply by file extension, but more powerfully by regex file name matching. This is done by introducing a new trac.ini parameter 'mime_map_patterns' in section [mimeviewer].

    How to test:

    • Add this to trac.ini, section [mimeviewer]: mime_map_patterns = text/x-python:.py.
    • Add a Python source file to your source code repository, but rename it to something containing 'py' without the defauly '.py' extension, e.g. 'test_py_file'
    • Restart Trac
    • Check in a web browser if your new repository file is correctly highlighted as a Python file

    This patch was initially developed for the Freetz [1] project by Alexander Kriegisch and used there [2] successfully ever since it was suggested in Ticket #10437 [3] in October 2012.

    Freetz usage exampe: mime_map_patterns = text/x-kconfig:.*Config.in.*|external.in.*|standard-modules.in

    [1] http://freetz.org [2] http://freetz.org/browser/trunk/tools/developer/mime_map_patterns.trac.patch [3] http://trac.edgewall.org/ticket/10437#comment:5

    opened by kriegaex 1
  • mimeview/api: new config setting [mimeviewer] mime_map_patterns

    mimeview/api: new config setting [mimeviewer] mime_map_patterns

    Purpose: enable Trac to determine MIME types for syntax highlighting not just simply by file extension, but more powerfully by regex file name matching. This is done by introducing a new trac.ini parameter 'mime_map_patterns' in section [mimeviewer].

    How to test:

    • Add this to trac.ini, section [mimeviewer]: mime_map_patterns = text/x-python:.py.
    • Add a Python source file to your source code repository, but rename it to something containing 'py' without the defauly '.py' extension, e.g. 'test_py_file'
    • Restart Trac
    • Check in a web browser if your new repository file is correctly highlighted as a Python file

    This patch was initially developed for the Freetz [1] project by Alexander Kriegisch and used there [2] successfully ever since it was suggested in Ticket #10437 [3] in October 2012.

    Freetz usage exampe: mime_map_patterns = text/x-kconfig:.*Config.in.*|external.in.*|standard-modules.in

    [1] http://freetz.org [2] http://freetz.org/browser/trunk/tools/developer/mime_map_patterns.trac.patch [3] http://trac.edgewall.org/ticket/10437#comment:5

    opened by kriegaex 1
  • This change facilitates better ordering of search results.

    This change facilitates better ordering of search results.

    I was looking for a solution to enhance the usefulness of trac search results. Stock trac seems to sort search results by the date of last change, which might not always be what users expect. Looking for a medium solution between using complete indexing server as suggested in https://trac.edgewall.org/wiki/AdvancedSearch and the current solution, I suggest a medium solution (with regard to both complexity and quality), ordering the results based on occurrence of the search word in page/ticket title, headers and content.

    The ISearchSource get_search_results() gets an optional sixth value in the return tuple called order which is supposed to contain a quadtuple which is to be composed of

    • rating for pagename/filename
    • rating for headings
    • rating for description/content
    • timestamp The order parameter is then used to sort search results. The ratings are evaluated in above order. In each case, a higher value will signify a more relevant search result.
    opened by NetSpida 0
  • Enhanced Search Result Ordering

    Enhanced Search Result Ordering

    I was looking for a solution to enhance the usefulness of trac search results. Stock trac seems to sort search results by the date of last change, which might not always be what users expect. Looking for a medium solution between using complete indexing server as suggested in https://trac.edgewall.org/wiki/AdvancedSearch and the current solution, I suggest a medium solution (with regard to both complexity and quality), ordering the results based on occurrence of the search word in page/ticket title, headers and content.

    The ISearchSource get_search_results() gets an optional sixth value in the return tuple called order which is supposed to contain a quadtuple which is to be composed of

    • rating for pagename/filename
    • rating for headings
    • rating for description/content
    • timestamp The order parameter is then used to sort search results. The ratings are evaluated in above order. In each case, a higher value will signify a more relevant search result.
    opened by NetSpida 0
  • Enhanced Search Result Ordering

    Enhanced Search Result Ordering

    I was looking for a solution to enhance the usefulness of trac search results. Stock trac seems to sort search results by the date of last change, which might not always be what users expect. Looking for a medium solution between using complete indexing server as suggested in https://trac.edgewall.org/wiki/AdvancedSearch and the current solution, I suggest a medium solution (with regard to both complexity and quality), ordering the results based on occurrence of the search word in page/ticket title, headers and content.

    The ISearchSource get_search_results() gets an optional sixth value in the return tuple called order which is supposed to contain a quadtuple which is to be composed of

    • rating for pagename/filename
    • rating for headings
    • rating for description/content
    • timestamp The order parameter is then used to sort search results. The ratings are evaluated in above order. In each case, a higher value will signify a more relevant search result.
    opened by NetSpida 1
Owner
Edgewall Software
Edgewall Software
Patchwork is a web-based patch tracking system designed to facilitate the contribution and management of contributions to an open-source project.

Patchwork Patchwork is a patch tracking system for community-based projects. It is intended to make the patch management process easier for both the p

Patchwork 220 Nov 29, 2022
A simple version control system built on top of Git

Gitless Gitless is a version control system built on top of Git, that is easy to learn and use: Simple commit workflow Track or untrack files to contr

Gitless 1.7k Dec 22, 2022
ViewVC is a browser interface for CVS and Subversion version control repositories.

ViewVC - Version Control Browser Interface ViewVC is a browser interface for CVS and Subversion version control repositories. It generates templatized

ViewVC 270 Dec 30, 2022
MoinMoin Wiki Development (2.0+), unstable, for production please use 1.9.x.

MoinMoin - a wiki engine in Python MoinMoin is an easy to use, full-featured and extensible wiki software package written in Python. It can fulfill a

MoinMoin Wiki Engine 240 Dec 22, 2022
A python package for your Kali Linux distro that find the fastest mirror and configure your apt to use that mirror

Kali Mirror Finder Using Single Python File A python package for your Kali Linux distro that find the fastest mirror and configure your apt to use tha

MrSingh 6 Dec 12, 2022
Bagas Mirror&Leech Bot is a multipurpose Telegram Bot written in Python for mirroring files on the Internet to our beloved Google Drive. Based on python-aria-mirror-bot

- [ MAYBE UPDATE & ADD MORE MODULE ] Bagas Mirror&Leech Bot Bagas Mirror&Leech Bot is a multipurpose Telegram Bot written in Python for mirroring file

null 4 Nov 23, 2021
A wiki system with complex functionality for simple integration and a superb interface. Store your knowledge with style: Use django models.

django-wiki Django support The below table explains which Django versions are supported. Release Django Upgrade from 0.7.x 2.2, 3.0, 3.1 0.5 or 0.6 0.

django-wiki 1.6k Dec 28, 2022
Source-o-grapher is a tool built with the aim to investigate software resilience aspects of Open Source Software (OSS) projects.

Source-o-grapher is a tool built with the aim to investigate software resilience aspects of Open Source Software (OSS) projects.

Aristotle University 5 Jun 28, 2022
A command-line utility that creates projects from cookiecutters (project templates), e.g. Python package projects, VueJS projects.

Cookiecutter A command-line utility that creates projects from cookiecutters (project templates), e.g. creating a Python package project from a Python

null 18.6k Dec 30, 2022
A command-line utility that creates projects from cookiecutters (project templates), e.g. Python package projects, VueJS projects.

Cookiecutter A command-line utility that creates projects from cookiecutters (project templates), e.g. creating a Python package project from a Python

null 18.6k Jan 2, 2023
A command-line utility that creates projects from cookiecutters (project templates), e.g. Python package projects, VueJS projects.

Cookiecutter A command-line utility that creates projects from cookiecutters (project templates), e.g. creating a Python package project from a Python

null 18.7k Jan 8, 2023
Repository tracking all OpenStack repositories as submodules. Mirror of code maintained at opendev.org.

OpenStack OpenStack is a collection of interoperable components that can be deployed to provide computing, networking and storage resources. Those inf

Mirrors of opendev.org/openstack 4.6k Dec 28, 2022
A bot framework for Reddit to manage threads, wiki pages, widgets, menus and more.

Sub Manager Sub Manager is a bot framework for Reddit to automate a variety of tasks on one or more subreddits, and can be configured and run without

r/SpaceX 3 Aug 26, 2022
Nicely is a real-time Feedback and Intervention Program Depression is a prevalent issue across all age groups, socioeconomic classes, and cultural identities.

Nicely is a real-time Feedback and Intervention Program Depression is a prevalent issue across all age groups, socioeconomic classes, and cultural identities.

null 1 Jan 16, 2022
WikidPad is a single user desktop wiki

What is WikidPad? WikidPad is a Wiki-like notebook for storing your thoughts, ideas, todo lists, contacts, or anything else you can think of to write

WikidPad 176 Dec 14, 2022
Main repository of the zim desktop wiki project

Zim - A Desktop Wiki Editor Zim is a graphical text editor used to maintain a collection of wiki pages. Each page can contain links to other pages, si

Zim Desktop Wiki 1.6k Dec 30, 2022
Unofficial Meteor Client wiki

Welcome to the Unofficial Meteor Client wiki! Meteor FAQs | A rewritten and better FAQ page. Installation Guide | A guide on how to install Meteor Cli

Anti Cope 0 Feb 21, 2022
Discord bot for the IOTA Wiki

IOTA Wiki Bot Discord bot for the IOTA Wiki Report Bug · Request Feature About The Project This is a Discord bot for the IOTA Wiki. It's currently use

IOTA Community 2 Nov 14, 2021