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".
  • TracInstall – Opus Project
    although SilverCity 0 9 7 and or GNU Enscript are also possible Refer to TracSyntaxColoring for details pytz to get a complete list of time zones otherwise Trac will fall back on a shorter list from an internal time zone implementation Attention The various available versions of these dependencies are not necessarily interchangable so please pay attention to the version numbers above If you are having trouble getting Trac to work please double check all the dependencies before asking for help on the MailingList or IrcChannel Please refer to the documentation of these packages to find out how they are best installed In addition most of the platform specific instructions also describe the installation of the dependencies Keep in mind however that the information there probably concern older versions of Trac than the one you re installing there are even some pages that are still talking about Trac 0 8 Installing Trac One way to install Trac is using setuptools With setuptools you can install Trac from the subversion repository for example to install release version 0 11 do easy install http svn edgewall org repos trac tags trac 0 11 But of course the python typical setup at the top of the source directory also works python setup py install Note you ll need root permissions or equivalent for this step This will byte compile the python source code and install it as an egg file or folder in the site packages directory of your Python installation The egg will also contain all other resources needed by standard Trac such as htdocs and templates The script will also install the trac admin command line tool used to create and maintain project environments as well as the tracd standalone server Advanced Options To install Trac to a custom location or find out about other advanced installation options run easy install help Also see Installing Python Modules for detailed information Specifically you might be interested in easy install prefix path to installdir or if installing Trac to a Mac OS X system easy install prefix usr local install dir Library Python 2 5 site packages The above will place your tracd and trac admin commands into usr local bin and will install the Trac libraries and dependencies into Library Python 2 5 site packages which is Apple s preferred location for third party Python application installations Creating a Project Environment A Trac environment is the backend storage where Trac stores information like wiki pages tickets reports settings etc An environment is basically a directory that contains a human readable configuration file and various other files and directories A new environment is created using trac admin trac admin path to myproject initenv trac admin will prompt you for the information it needs to create the environment such as the name of the project the type and the path to an existing source code repository the database connection string and so on If you re not sure what to specify for one of

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

  • TracInterfaceCustomization – Opus Project
    1999 xhtml xmlns py http genshi edgewall org py strip Add site specific style sheet head py match head py attrs select select comment text link rel stylesheet type text css href href chrome site style css head body py match body py attrs select Add site specific header div id siteheader Place your header content here div select text Add site specific footer div id sitefooter Place your footer content here div body html Those who are familiar with XSLT may notice that Genshi templates bear some similarities However there are some Trac specific features for example chrome htdocs location is used to specify common htdocs directory from Trac installation site html is one file to contain all your modifications It usually works by the py match element of attribute and it allows you to modify the page as it renders the matches hook onto specific sections depending on what it tries to find and modify them A site html can contain any number of such py match sections for whatever you need to modify This is all Genshi so the docs on the exact syntax can be found there Example snippet of adding introduction text to the new ticket form hide when preview form py match div id content and class ticket form py attrs select py if test req environ PATH INFO newticket and not preview in req args p Please make sure to search for existing tickets before reporting a new one p py if select form This example illustrates a technique of using req environ PATH INFO to limit scope of changes to one view only For instance to make changes in site html only for timeline and avoid modifying other sections use req environ PATH INFO timeline condition in py if test If the environment is upgraded from 0 10 and a site newticket cs file already exists it can actually be loaded by using a workaround providing it contains no ClearSilver processing In addition as only one element can be imported the content needs some sort of wrapper such as a div block or other similar parent container The XInclude namespace must be specified to allow includes but that can be moved to document root along with the others form py match div id content and class ticket form py attrs select xmlns xi http www w3 org 2001 XInclude py if test req environ PATH INFO newticket and not preview in req args xi include href site newticket cs xi fallback xi include py if select form Also note that the site html despite its name can be put in a common templates directory see the inherit templates dir option This could provide easier maintainence and a migration path from 0 10 for larger installations as one new global site html file can be made to include any existing header footer and newticket snippets Project List You can use a custom Genshi template to display the list of projects if you are

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

  • TracLinks – Opus Project
    greater flexibility InterTrac links This can be seen as a kind of InterWiki link specialized for targeting other Trac projects Any type of Trac links could be written in one Trac environment and actually refer to resources present in another Trac environment provided the Trac link is prefixed by the name of that other Trac environment followed by a colon That other Trac environment must be registered under its name or an alias See InterTrac for details A distinctive advantage of InterTrac links over InterWiki links is that the shorthand form of Trac links usually have a way to understand the InterTrac prefixes For example links to Trac tickets can be written T234 if T was set as an alias for Trac links to Trac changesets can be written trac 1508 Server relative links It is often useful to be able to link to objects in your project that have no built in Trac linking mechanism such as static resources newticket a shared register page on the server etc To link to resources inside the project use either an absolute path from the project root or a relative link from the URL of the current page Changed in 0 11 newticket Create a new ticket home Display newticket home To link to another location on the server outside the project use the location link syntax Changed in 0 11 register Register Here Display Register Here Quoting space in TracLinks Immediately after a TracLinks prefix targets containing space characters should be enclosed in a pair of quotes or double quotes Examples wiki The whitespace convention attachment the file txt or attachment the file txt attachment the file txt ticket 123 Escaping Links To prevent parsing of a TracLink you can escape it by preceding it with a exclamation mark NoLinkHere 42 is not a link either Display NoLinkHere 42 is not a link either Parameterized Trac links The Trac links target Trac resources which have generally more than one way to be rendered according to some extra parameters For example a Wiki page can accept a version or a format parameter a report can make use of dynamic variables etc Any Trac links can support an arbitrary set of parameters written in the same way as they would be for the corresponding URL Some examples wiki WikiStart format txt ticket 1 version 1 newticket component module1 create a ticket for module1 TracLinks Reference The following sections describe the individual link types in detail as well as several notes advanced usage of links attachment links The link syntax for attachments is as follows attachment the file txt creates a link to the attachment the file txt of the current object attachment the file txt wiki MyPage creates a link to the attachment the file txt of the MyPage wiki page attachment the file txt ticket 753 creates a link to the attachment the file txt of the ticket 753 Note that the older way putting the filename at the end is still

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

  • TracLogging – Opus Project
    option in trac ini stderr Output all log entries to console tracd only syslog UNIX Send all log messages to the local syslogd via named pipe dev log By default syslog will write them to the file var log messages eventlog Windows Use the system s NT Event Log for Trac logging Log Levels The verbosity level of logged messages can be set using the log level option in trac ini The log level defines the minimum level of urgency required for a message to be logged and those levels are CRITICAL Log only the most critical typically fatal errors ERROR Log failures bugs and errors WARN Log warnings non interrupting events INFO Diagnostic information log information about all processing DEBUG Trace messages profiling etc Log Format Starting with Trac 0 10 4 see 2844 it is possible to set the output format for log entries This can be done through the log format option in trac ini The format is a string which can contain any of the Python logging Formatter variables Additonally the following Trac specific variables can be used basename s The last path component of the current environment path s The absolute path for the current

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

  • TracModPython – Opus Project
    locations different from root while having the possibility of placing a custom home page for root in your DocumentRoot folder You can also use the same authentication realm for all of the projects using a LocationMatch directive LocationMatch projects login AuthType Basic AuthName Trac AuthUserFile var trac htpasswd Require valid user LocationMatch Virtual Host Configuration Below is the sample configuration required to set up your trac as a virtual server i e when you access it at the URLs like http trac mycompany com VirtualHost DocumentRoot var www myproject ServerName trac mycompany com Location SetHandler mod python PythonInterpreter main interpreter PythonHandler trac web modpython frontend PythonOption TracEnv var trac myproject PythonOption TracUriRoot Location Location login AuthType Basic AuthName MyCompany Trac Server AuthUserFile var trac myproject htpasswd Require valid user Location VirtualHost This does not seem to work in all cases What you can do if it does not Try using LocationMatch instead of Location Location may in your server setup refer to the complete host instead of simple the root of the server This means that everything including the login directory referenced below will be sent to python and authentication does not work i e you get the infamous Authentication information missing error If this applies to you try using a sub directory for trac instead of the root i e web and web login instead of and login For a virtual host that supports multiple projects replace TracEnv var trac myproject with TracEnvParentDir var trac Note DocumentRoot should not point to your Trac project env As Asmodai wrote on trac suppose there s a webserver bug that allows disclosure of DocumentRoot they could then leech the entire Trac environment Troubleshooting In general if you get server error pages you can either check the Apache error log or enable the PythonDebug option Location projects myproject PythonDebug on Location For multiple projects try restarting the server as well Expat related segmentation faults This problem will most certainly hit you on Unix when using Python 2 4 In Python 2 4 some version of Expat an XML parser library written in C is used and if Apache is using another version this results in segmentation faults As Trac 0 11 is using Genshi which will indirectly use Expat that problem can now hit you even if everything was working fine before with Trac 0 10 See Graham Dumpleton s detailed explanation and workarounds for the issue Form submission problems If you re experiencing problems submitting some of the forms in Trac a common problem is that you get redirected to the start page after submission check whether your DocumentRoot contains a folder or file with the same path that you mapped the mod python handler to For some reason mod python gets confused when it is mapped to a location that also matches a static resource Problem with virtual host configuration If the Location directive is used setting the DocumentRoot may result in a 403 Forbidden error Either remove the DocumentRoot directive

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

  • TracModWSGI – Opus Project
    a wsgi files which handles all this for you by running the TracAdmin command deploy If you have installed trac and eggs in a path different from the standard one you should add that path by adding the following code on top of the wsgi script import site site addsitedir usr local trac lib python2 4 site packages Change it according to the path you installed the trac libs at After you ve done preparing your wsgi script add the following to your httpd conf WSGIScriptAlias trac usr local trac mysite apache mysite wsgi Directory usr local trac mysite apache WSGIApplicationGroup GLOBAL Order deny allow Allow from all Directory Here the script is in a subdirectory of the Trac environment In order to let Apache run the script access to the directory in which the script resides is opened up to all of Apache Additionally the WSGIApplicationGroup directive ensures that Trac is always run in the first Python interpreter created by mod wsgi this is necessary because the Subversion Python bindings which are used by Trac don t always work in other subinterpreters and may cause requests to hang or cause Apache to crash as a result After adding this configuration restart Apache and then it should work To test the setup of Apache mod wsgi and Python itself ie without involving Trac and dependencies this simple wsgi application can be used to make sure that requests gets served use as only content in your wsgi script def application environ start response start response 200 OK Content type text html return html body Hello World body html See also the mod wsgi installation instructions for Trac For troubleshooting tips see the mod python troubleshooting section as most Apache related issues are quite similar plus discussion of potential application issues when

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

  • TracNavigation – Opus Project
    the main modules enabled in Trac and accessible for the current user metanav corresponds to the meta navigation bar by default positioned above the main navigation bar and below the Search box It contains the Log in Logout Help Guide etc entries This navigation bar is meant to access some global information about the Trac project and the current user Note that it is still not possible to customize the

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

  • TracNotification – Opus Project
    addresses and map the username login to a local mailbox See also smtp default domain Do not use this option with a public SMTP server mime encoding since 0 10 E mail notifications are always sent in 7 bit mode This option allows to select the MIME encoding scheme Supported values base64 default value works with any kind of content May cause some issues with touchy anti spam anti virus engines qp or quoted printable best for european languages more compact than base64 not recommended for non ASCII text less compact than base64 none no encoding Use with plain english only ASCII E mails with non ASCII chars won t be delivered ticket subject template since 0 11 A Genshi text template snippet used to get the notification subject Either smtp from or smtp replyto or both must be set otherwise Trac refuses to send notification mails The following options are specific to email delivery through SMTP smtp server SMTP server used for notification messages smtp port since 0 9 Port used to contact the SMTP server smtp user since 0 9 User name for authentication SMTP account smtp password since 0 9 Password for authentication SMTP account use tls since 0 10 Toggle to send notifications via a SMTP server using TLS such as GMail Example Configuration SMTP notification smtp enabled true smtp server mail example com smtp from notifier example com smtp replyto myproj projects example com smtp always cc ticketmaster example com theboss myproj example com Customizing the e mail subject The e mail subject can be customized with the ticket subject template option which contains a Genshi text template snippet The default value is prefix ticket id summary The following variables are available in the template env The project environment see env py prefix The prefix defined in smtp subject prefix summary The ticket summary with the old value if the summary was edited ticket The ticket model object see model py Individual ticket fields can be addressed by appending the field name separated by a dot e g ticket milestone Sample Email 42 testing Id 42 Status assigned Component report system Modified Fri Apr 9 00 04 31 2004 Severity major Milestone 0 9 Priority lowest Version 0 6 Owner anonymous Reporter jonas example com Changes component changset view search system priority low highest owner jonas anonymous cc daniel example com daniel example com jonas example com status new assigned Comment I m interested too Ticket URL http example com trac ticket 42 My Project http myproj example com Using GMail as the SMTP relay host Use the following configuration snippet notification smtp enabled true use tls true mime encoding base64 smtp server smtp gmail com smtp port 587 smtp user user smtp password password where user and password match an existing GMail account i e the ones you use to log in on http gmail com Alternatively you can use smtp port 25 You should not use smtp port 465 It will not work

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