archive-fr.com » FR » O » OPUS-PROJECT.FR

Total: 702

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • TracBrowser – Opus Project
    the file Clicking on the revision number of a file or directory will take you to the TracRevisionLog for that file Note that there s also a Revision Log navigation link that will do the same for the path currently being examined It s also possible to browse directories or files as they were in history at any given repository revision The default behavior is to display the latest revision but another revision number can easily be selected using the View revision input field at the top of the page since 0 11 The color bar next to the Age column gives a visual indication of the age of the last change to a file or directory In the default configuration blue is older and red is newer but this can be configured At the top of the browser page there s a drop down menu which you can use to select some interesting places in the repository for example branches or tags This is sometimes referred to as the browser quickjump facility The precise meaning and content of this menu depends on your backend For Subversion this list contains by default a few branches trunk and any sub folder of the latest branches top level folder and a few tags any sub folder of the latest tags top level folder This can be configured for more advanced cases If you re using a Javascript enabled brower you ll be able to expand and collapse folders in place by clicking on the arrow head at the right side of a folder Alternatively the keyboard can also be used for this use j and k to go to the next or previous entry and o or Enter to toggle between expanded and collapsed state of the selected folder or for visiting

    Original URL path: http://www.opus-project.fr/trac/wiki/TracBrowser (2016-01-11)
    Open archived version from archive


  • TracCgi – Opus Project
    and from trac web import os os environ TRAC ENV path to projectenv Or for TRAC ENV PARENT DIR import os os environ TRAC ENV PARENT DIR path to project parent dir This will make Trac available at http yourhost example org trac If you are using the Apache suEXEC feature please see http trac edgewall org wiki ApacheSuexec On some systems you may need to edit the shebang line in the trac cgi file to point to your real Python installation path On a Windows system you may need to configure Windows to know how to execute a cgi file Explorer Tools Folder Options File Types CGI Mapping Static Resources Out of the box Trac will serve static resources such as style sheets or images itself For a CGI setup though this is highly undesirable because it results in the CGI script being invoked for documents that could be much more efficiently served by the web server directly Web servers such as Apache HTTPD allow you to create Aliases to resources thereby giving them a virtual URL that doesn t necessarily bear any resemblance to the layout of the servers file system We already used this capability above when defining a ScriptAlias for the CGI script and we ll use it now to map requests to the static resources to the directory on the file system that contains them thereby bypassing the processing of such requests by the CGI script Edit the Apache configuration file again and add the following snippet before the ScriptAlias for the CGI script file names and locations changed to match your installation Alias trac chrome common usr share trac htdocs Directory usr share trac htdocs Order allow deny Allow from all Directory Note that whatever URL path you mapped the trac cgi script to the path chrome common is the path you have to append to that location to intercept requests to the static resources For example if Trac is mapped to cgi bin trac cgi on your server the URL of the Alias should be cgi bin trac cgi chrome common Similarly if you have static resources in a projects htdocs directory you can configure apache to serve those resources again put this before the ScriptAlias for the CGI script and adjust names and locations to match your installation Alias trac chrome site path to projectenv htdocs Directory path to projectenv htdocs Order allow deny Allow from all Directory Alternatively you can set the htdocs location configuration option in trac ini trac htdocs location trac htdocs Trac will then use this URL when embedding static resources into HTML pages Of course you still need to make the Trac htdocs directory available through the web server at the specified URL for example by copying or linking the directory into the document root of the web server ln s usr share trac htdocs var www your site com htdocs trac htdocs Note that in order to get this htdocs directory you need first to extract

    Original URL path: http://www.opus-project.fr/trac/wiki/TracCgi (2016-01-11)
    Open archived version from archive

  • TracChangeset – Opus Project
    Each file is shown in a separate section each of which will contain only the regions of the file that are affected by the changeset There are two different styles of displaying the diffs inline or side by side you can switch between those styles using the preferences form The inline style shows the changed regions of a file underneath each other A region removed from the file will be colored red an added region will be colored green If a region was modified the old version is displayed above the new version Line numbers on the left side indicate the exact position of the change in both the old and the new version of the file The side by side style shows the old version on the left and the new version on the right this will typically require more screen width than the inline style Added and removed regions will be colored in the same way as with the inline style green and red respectively but modified regions will have a yellow background In addition various advanced options are available in the preferences form for adjusting the display of the diffs You can set how many lines are displayed before and after every change if the value all is used then the full file will be shown You can toggle whether blank lines case changes and white space changes are ignored thereby letting you find the functional changes more quickly The Different Ways to Get a Diff Examining a Changeset When viewing a repository check in such as when following a changeset link or a changeset event in the timeline Trac will display the exact changes made by the check in There will be also navigation links to the Previous Changeset to and Next Changeset Examining Differences Between

    Original URL path: http://www.opus-project.fr/trac/wiki/TracChangeset (2016-01-11)
    Open archived version from archive

  • TracEnvironment – Opus Project
    to a PostgreSQL database on the same machine called trac that allows access to the user johndoe with the password letmein use postgres johndoe letmein localhost trac Note that due to the way the above string is parsed the and characters cannot be part of the password If PostgreSQL is running on a non standard port for example 9342 use postgres johndoe letmein localhost 9342 trac On UNIX you might want to select a UNIX socket for the transport either the default socket as defined by the PGHOST environment variable postgres user password database or a specific one postgres user password database host path to socket dir Note that with PostgreSQL you will have to create the database before running trac admin initenv See the PostgreSQL documentation for detailed instructions on how to administer PostgreSQL Generally the following is sufficient to create a database user named tracuser and a database named trac createuser U postgres E P tracuser createdb U postgres O tracuser E UTF8 trac When running createuser you will be prompted for the password for the user tracuser This new user will not be a superuser will not be allowed to create other databases and will not be allowed to create other roles These privileges are not needed to run a trac instance If no password is desired for the user simply remove the P and E options from the createuser command Also note that the database should be created as UTF8 LATIN1 encoding causes errors trac s use of unicode in trac SQL ASCII also seems to work Under some default configurations debian one will have run the createuser and createdb scripts as the postgres user For example sudo su postgres c createuser U postgres S D R E P tracuser sudo su postgres c createdb U postgres O tracuser E UTF8 trac Trac uses the public schema by default but you can specify a different schema in the connection string postgres user pass server database schema yourschemaname MySQL Connection String If you want to use MySQL instead you ll have to use a different connection string For example to connect to a MySQL database on the same machine called trac that allows access to the user johndoe with the password letmein the mysql connection string is mysql johndoe letmein localhost 3306 trac Source Code Repository You ll first have to provide the type of your repository e g svn for Subversion which is the default then the path where the repository is located If you don t want to use Trac with a source code repository simply leave the path empty the type information doesn t matter then For some systems it is possible to specify not only the path to the repository but also a scope within the repository Trac will then only show information related to the files and changesets below that scope The Subversion backend for Trac supports this for other types check the corresponding plugin s documentation Example of a configuration for

    Original URL path: http://www.opus-project.fr/trac/wiki/TracEnvironment (2016-01-11)
    Open archived version from archive

  • TracFastCgi – Opus Project
    reference them in the above settings Note that the above will result in different processes in any event even if both are running from the same trac fcgi script Note It s very important the order on which server modules are loaded if mod auth is not loaded BEFORE mod fastcgi then the server will fail to authenticate the user For authentication you should enable mod auth in lighttpd conf server modules select auth backend and auth rules server modules mod auth auth backend htpasswd Separated password files for each project See Conditional Configuration in http trac lighttpd net trac file branches lighttpd merge 1 4 x doc configuration txt HTTP url first auth backend htpasswd userfile path to projenv first htpasswd htaccess HTTP url second auth backend htpasswd userfile path to projenv second htpasswd htaccess Enable auth on trac URLs see http trac lighttpd net trac file branches lighttpd merge 1 4 x doc authentication txt auth require first login method basic realm First project require valid user second login method basic realm Second project require valid user Note that lighttpd I use version 1 4 3 stopped if password file doesn t exist Note that lighttpd doesn t support valid user in versions prior to 1 3 16 Conditional configuration is also useful for mapping static resources i e serving out images and CSS directly instead of through FastCGI Aliasing functionality is needed server modules mod alias Setup an alias for the static resources alias url trac chrome common usr share trac htdocs Use negative lookahead matching all requests that ask for any resource under trac EXCEPT in trac chrome common and use FastCGI for those HTTP url trac chrome common Even if you have other fastcgi server declarations for applications other than Trac do NOT use here fastcgi server trac trac socket tmp trac fastcgi sock bin path fcgi binary check local disable bin environment TRAC ENV path to projenv The technique can be easily adapted for use with multiple projects by creating aliases for each of them and wrapping the fastcgi server declarations inside conditional configuration blocks Also there is another way to handle multiple projects and it s to use TRAC ENV PARENT DIR instead of TRAC ENV and use global auth let s see an example This is for handling multiple projects alias url trac path to trac htdocs fastcgi server projects trac socket tmp trac sock bin path fcgi binary check local disable bin environment TRAC ENV PARENT DIR path to parent dir of projects And here starts the global auth configuration auth backend htpasswd auth backend htpasswd userfile path to unique htpassword file trac htpasswd HTTP url projects login auth require method basic realm trac require valid user Changing date time format also supported by lighttpd over environment variable LC TIME fastcgi server trac trac socket tmp trac fastcgi sock bin path fcgi binary check local disable bin environment TRAC ENV path to projenv LC TIME ru RU For details about languages

    Original URL path: http://www.opus-project.fr/trac/wiki/TracFastCgi (2016-01-11)
    Open archived version from archive

  • TracFineGrainedPermissions – Opus Project
    critical as policies will be examined in the sequence provided A policy will return either True False or None for a given permission check Only if the return value is None will the next permission policy be consulted If no policy explicitly grants the permission the final result will be False i e no permission For example if the authz file contains wiki WikiStart WIKI VIEW wiki PrivatePage john WIKI VIEW and the default permissions are set like this john WIKI VIEW jack WIKI VIEW anonymous has no WIKI VIEW Then All versions of WikiStart will be viewable by everybody including anonymous PrivatePage will be viewable only by john other pages will be viewable only by john and jack mod authz svn like permission policy At the time of this writing the old fine grained permissions system from Trac 0 10 and before used for restricting access to the repository has not yet been converted to a permission policy component but from the user point of view this makes little if no difference That kind of fine grained permission control needs a definition file which is the one used by Subversion s mod authz svn More information about this file format and about its usage in Subversion is available in the Subversion Book Per Directory Access Control Example r branches calc bug 142 harry rw sally r branches calc bug 142 secret harry Everyone has read access by default branches calc bug 142 harry has read write access sally read only branches calc bug 142 secret harry has no access sally has read access inherited as a sub folder permission Trac Configuration To activate fine grained permissions you must specify the authz file option in the trac section of trac ini If this option is set to null or not

    Original URL path: http://www.opus-project.fr/trac/wiki/TracFineGrainedPermissions (2016-01-11)
    Open archived version from archive

  • TracImport – Opus Project
    activity field changes bug attachments user names and passwords put into a htpasswd file The script provides a number of features to ease the conversion such as PRODUCT KEYWORDS Trac doesn t have the concept of products so the script provides the ability to attach a ticket keyword instead IGNORE COMMENTS Don t import Bugzilla comments that match a certain regexp STATUS KEYWORDS Attach ticket keywords for the Bugzilla statuses not available in Trac By default the VERIFIED and RELEASED Bugzilla statuses are translated into Trac keywords For more details on the available options see the configuration section at the top of the script Sourceforge Ticket data can be imported from Sourceforge using the sourceforge2trac py script available in the contrib directory of the Trac distribution Mantis NB The mantis2trac script now lives at http trac hacks org wiki MantisImportScript You can always get the latest version from http trac hacks org changeset latest mantisimportscript old path filename mantisimportscript format zip Mantis bugs can be imported using the attached script Currently the following data is imported from Mantis bugs bug comments bug activity field changes attachments as long as the files live in the mantis db not on the filesystem If you use the script please read the NOTES section at the top of the file and make sure you adjust the config parameters for your environment mantis2trac py has the same parameters as the bugzilla2trac py script mantis2trac Imports a bug database from Mantis into Trac Usage mantis2trac py options Available Options db MySQL dbname Mantis database tracenv path to trac env Full path to Trac db environment h host MySQL hostname Mantis DNS host name u user MySQL username Effective Mantis database user p passwd MySQL password Mantis database user password c clean Remove current Trac tickets before

    Original URL path: http://www.opus-project.fr/trac/wiki/TracImport (2016-01-11)
    Open archived version from archive

  • TracIni – Opus Project
    by Enscript For each a tuple mimetype mode quality has to be specified where mimetype is the MIME type mode is the corresponding Enscript mode to be used for the conversion and quality is the quality ratio associated to this conversion That can also be used to override the default quality ratio used by the Enscript render which is 2 since 0 10 enscript path Path to the Enscript executable max preview size Maximum file size for HTML preview since 0 9 mime map List of additional MIME types and keyword mappings Mappings are comma separated and for each MIME type there s a colon separated list of associated keywords or file extensions since 0 10 php path Path to the PHP executable since 0 9 tab width Displayed tab width in file preview since 0 9 notification admit domains Comma separated list of domains that should be considered as valid for email addresses such as localdomain always notify owner Always send notifications to the ticket owner since 0 9 always notify reporter Always send notifications to any address in the reporter field always notify updater Always send notifications to the person who causes the ticket property change ignore domains Comma separated list of domains that should not be considered part of email addresses for usernames with Kerberos domains mime encoding Specifies the MIME encoding scheme for emails Valid options are base64 for Base64 encoding qp for Quoted Printable and none for no encoding Note that the no encoding means that non ASCII characters in text are going to cause problems with notifications since 0 10 smtp always bcc Email address es to always send notifications to addresses do not appear publicly Bcc since 0 10 smtp always cc Email address es to always send notifications to addresses can be seen by all recipients Cc smtp default domain Default host domain to append to address that do not specify one smtp enabled Enable SMTP email notification smtp from Sender address to use in notification emails smtp from name Sender name to use in notification emails smtp password Password for SMTP server since 0 9 smtp port SMTP server port to use for email notification smtp replyto Reply To address to use in notification emails smtp server SMTP server hostname to use for email notifications smtp subject prefix Text to prepend to subject line of notification emails If the setting is not defined then the project name prefix If no prefix is desired then specifying an empty option will disable it since 0 10 1 smtp user Username for SMTP server since 0 9 ticket subject template A Genshi text template snippet used to get the notification subject since 0 11 use public cc Recipients can see email addresses of other CC ed recipients If this option is disabled the default recipients are put on BCC since 0 10 use short addr Permit email address without a host domain i e username only The SMTP server should accept those addresses and either append a FQDN or use local delivery since 0 10 use tls Use SSL TLS to send notifications since 0 10 project admin E Mail address of the project s administrator admin trac url Base URL of a Trac instance where errors in this Trac should be reported This can be an absolute or relative URL or to reference this Trac instance An empty value will disable the reporting buttons since 0 11 3 descr Short description of the project footer Page footer text right aligned icon URL of the icon of the project name Name of the project url URL of the main project web site usually the website in which the base url resides query default anonymous query The default query for anonymous users The query is either in query language syntax or a URL query string starting with as used in query Trac links since 0 11 2 default query The default query for authenticated users The query is either in query language syntax or a URL query string starting with as used in query Trac links since 0 11 2 items per page Number of tickets displayed per page in ticket queries by default since 0 11 report items per page Number of tickets displayed per page in ticket reports by default since 0 11 items per page rss Number of tickets displayed in the rss feeds for reports since 0 11 revisionlog default log limit Default value for the limit argument in the TracRevisionLog since 0 11 roadmap stats provider Name of the component implementing ITicketGroupStatsProvider which is used to collect statistics on groups of tickets for display in the roadmap views search min query length Minimum length of query string allowed when performing a search svn branches List of paths categorized as branches If a path ends with then all the directory entries found below that path will be included tags List of paths categorized as tags If a path ends with then all the directory entries found below that path will be included ticket default cc Default cc list for newly created tickets default component Default component for newly created tickets default description Default description for newly created tickets default keywords Default keywords for newly created tickets default milestone Default milestone for newly created tickets default owner Default owner for newly created tickets default priority Default priority for newly created tickets default resolution Default resolution for resolving closing tickets since 0 11 default severity Default severity for newly created tickets default summary Default summary title for newly created tickets default type Default type for newly created tickets since 0 9 default version Default version for newly created tickets max comment size Don t accept tickets with a too big comment since 0 11 2 max description size Don t accept tickets with a too big description since 0 11 preserve newlines Whether Wiki formatter should respect the new lines present in the Wiki text If set to default this is equivalent to

    Original URL path: http://www.opus-project.fr/trac/wiki/TracIni (2016-01-11)
    Open archived version from archive