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".
  • CamelCase – Opus Project
    s an option ignore missing pages in wiki to simply ignore links to missing pages when the link is written using the CamelCase style instead of that word being replaced by a gray link followed by a question mark That can be useful when CamelCase style is used to name code artifacts like class names and there s no corresponding page for them There s an option split page names

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


  • TracStandalone – Opus Project
    fullpath environmentname htpasswd fullpath environmentname fullpath environmentname Tracd provides support for both Basic and Digest authentication The default is to use Digest to use Basic authentication replace auth with basic auth in the examples below You must still specify a dialogic realm which can be an empty string by trailing the BASICAUTH with a comma Support for Basic authentication was added in version 0 9 The general format for using authentication is tracd p port auth base project dir password file path realm project path where base project dir is the base directory of the project note this doesn t refer to the project name and it is case sensitive even for windows environments password file path path of the password file realm realm project path path of the project Example tracd p 8080 auth project1 path to users htdigest mycompany com path to project1 Of course the digest file can be be shared so that it is used for more than one project tracd p 8080 auth project1 path to users htdigest mycompany com auth project2 path to users htdigest mycompany com path to project1 path to project2 Another way to share the digest file is to specify for the project name tracd p 8080 auth path to users htdigest mycompany com path to project1 path to project2 If using the s parameter for serving a Trac environment from the root of a domain one must use for the project name How to set up an htdigest password file If you have Apache available you can use the htdigest command to generate the password file Type htdigest to get some usage instructions or read this page from the Apache manual to get precise instructions You ll be prompted for a password to enter for each user that you create For the name of the password file you can use whatever you like but if you use something like users htdigest it will remind you what the file contains As a suggestion put it in your projectname conf folder along with the trac ini file Note that you can start tracd without the auth argument but if you click on the Login link you will get an error Generating Passwords Without Apache If you don t have Apache available you can use this simple Python script to generate your passwords from optparse import OptionParser The md5 module is deprecated in Python 2 5 try from hashlib import md5 except ImportError from md5 import md5 realm trac build the options usage usage prog options parser OptionParser usage usage parser add option u username action store dest username type string help the username for whom to generate a password parser add option p password action store dest password type string help the password to use parser add option r realm action store dest realm type string help the realm in which to create the digest options args parser parse args check options if options username is None or options password is None

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

  • TracCgi – Opus Project
    add the following code between try 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

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

  • TracEnvironment – Opus Project
    connection string For example to connect 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

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

  • WikiFormatting – Opus Project
    2 And numbered lists can also be given an explicit number 3 Item 3 Display Item 1 Item 1 1 Item 1 1 1 Item 1 1 2 Item 1 1 3 Item 1 2 Item 2 Item 1 Item 1 a Item 1 b Item 1 b i Item 1 b ii Item 2 And numbered lists can also be given an explicit number Item 3 Note that there must be one or more spaces preceding the list item markers otherwise the list will be treated as a normal paragraph Definition Lists The wiki also supports definition lists Example llama some kind of mammal with hair ppython some kind of reptile without hair can you spot the typo Display llama some kind of mammal with hair ppython some kind of reptile without hair can you spot the typo Note that you need a space in front of the defined term Preformatted Text Block containing preformatted text are suitable for source code snippets notes and examples Use three curly braces wrapped around the text to define a block quote The curly braces need to be on a separate line Example def HelloWorld print Hello World Display def HelloWorld print Hello World Blockquotes In order to mark a paragraph as blockquote indent that paragraph with two spaces Example This text is a quote from someone else Display This text is a quote from someone else Discussion Citations To delineate a citation in an ongoing discussion thread such as the ticket comment area e mail like citation marks etc may be used Example Someone s original text Someone else s reply text My reply text Display Someone s original text Someone else s reply text My reply text Note Some WikiFormatting elements such as lists and preformatted text are lost in the citation area Some reformatting may be necessary to create a clear citation Tables Simple tables can be created like this Cell 1 Cell 2 Cell 3 Cell 4 Cell 5 Cell 6 Display Cell 1 Cell 2 Cell 3 Cell 4 Cell 5 Cell 6 Note that more complex tables can be created using reStructuredText Links Hyperlinks are automatically created for WikiPageNames and URLs WikiPageLinks can be disabled by prepending an exclamation mark character such as WikiPageLink Example TitleIndex http www edgewall com NotAlink Display TitleIndex http www edgewall com NotAlink Links can be given a more descriptive title by writing the link followed by a space and a title and all this inside square brackets If the descriptive title is omitted then the explicit prefix is discarded unless the link is an external link This can be useful for wiki pages not adhering to the WikiPageNames convention Example http www edgewall com Edgewall Software wiki TitleIndex Title Index wiki ISO9000 Display Edgewall Software Title Index ISO9000 Trac Links Wiki pages can link directly to other parts of the Trac system Pages can refer to tickets reports changesets milestones source files and other Wiki pages using the following notations Tickets

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

  • TracFastCgi – Opus Project
    fcgi and second fcgi and 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

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

  • PageTemplates – Opus Project
    pages having a name starting with PageTemplates The initial content of a new page will simply be the content of the chosen template page or a blank page if the special blank page entry is selected When there s actually no wiki pages matching that prefix the initial content will always be the blank page and the list selector will not be shown i e this matches the behavior we

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

  • TracUpgrade – Opus Project
    using MacOSX Library Python 2 X site packages You may also want to remove the Trac cgi bin htdocs templates and wiki default directories that are commonly found in a directory called share trac the exact location depends on your platform This cleanup is not mandatory but it makes it easier to troubleshoot issues later on as you won t waste your time looking at code or templates from a previous release that are not being used anymore As usual make a backup before actually deleting things If you had the webadmin plugin installed you can now uninstall it as it is now part of the Trac code base Upgrade the Trac Environment After restarting Trac should show the instances which need a manual upgrade via the automated upgrade scripts to ease the pain These scripts are run via trac admin trac admin path to projenv upgrade This command will do nothing if the environment is already up to date Note that if you are using a PostgreSQL database this command will fail with the message that the environment can only be backed up when you use an SQLite database This means that you will have to backup the repository and the database manually Then to perform the actual upgrade run trac admin path to projenv upgrade no backup If you are using custom CSS styles or modified templates in the templates directory of the TracEnvironment you will need to convert them to the Genshi way of doing things To continue to use your style sheet follow the instructions at TracInterfaceCustomization SiteAppearance Update the Trac Documentation Every Trac environment includes a copy of the Trac documentation for the installed version As you probably want to keep the included documentation in sync with the installed version of Trac trac admin provides a command to upgrade the documentation trac admin path to projenv wiki upgrade Note that this procedure will of course leave your WikiStart page intact Site Templates The templating engine has changed in 0 11 please look at TracInterfaceCustomization for more information Trac Macros Plugins The Trac macros will need to be adapted as the old style wiki macros are not supported anymore due to the drop of ClearSilver and the HDF they need to be converted to the new style macros see WikiMacros When they are converted to the new style they need to be placed into the plugins directory instead and not wiki macros which is no longer scanned for macros or plugins For CGI users For those who run Trac under the CGI environment run this command in order to obtain the trac cgi file trac admin path to env deploy deploy directory path This will create a deploy directory with the following two subdirectories cgi bin and htdocs Then update your Apache configuration file httpd conf with this new trac cgi location and htdocs location Restart the Web Server If you are not running CGI reload the new Trac code by restarting your web server Known

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