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".
  • TracChangeset (diff) – Opus Project
    diff view 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 42 43 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 44 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 45 46 In addition various advanced options are available in the preferences form for adjusting the display of the diffs 47 You can set how many lines are displayed before and after every change 48 if the value all is used then the full file will be shown 49 You can toggle whether blank lines case changes and white space changes are ignored thereby letting you find the functional changes more quickly 50 51 52 The Different Ways to Get a Diff 53 54 Examining a Changeset 55 56 When viewing a repository check in such as when following a 57 changeset wiki TracLinks link or a changeset event in the 58 wiki TracTimeline timeline Trac will display the exact

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


  • TracEnvironment (diff) – Opus Project
    same machine called trac that allows access to the 42 user johndoe with the password letmein use 43 44 postgres johndoe letmein localhost trac 45 46 Note that due to the way the above string is parsed the and characters cannot be part of the password 47 48 If PostgreSQL is running on a non standard port for example 9342 use 49 50 postgres johndoe letmein localhost 9342 trac 51 52 53 On UNIX you might want to select a UNIX socket for the transport 54 either the default socket as defined by the PGHOST environment variable 55 56 postgres user password database 57 58 or a specific one 59 60 postgres user password database host path to socket dir 61 62 63 Note that with PostgreSQL you will have to create the database before running 64 trac admin initenv 65 66 See the http www postgresql org docs PostgreSQL documentation for detailed instructions on how to administer http postgresql org PostgreSQL 67 Generally the following is sufficient to create a database user named tracuser and a database named trac 68 69 createuser U postgres E P tracuser 70 createdb U postgres O tracuser E UTF8 trac 71 72 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 73 74 Under some default configurations debian one will have run the createuser and createdb scripts as the postgres user For example 75 76 sudo su postgres c createuser U postgres S D R E P tracuser 77 sudo su postgres c createdb U postgres O tracuser E UTF8 trac 78 79 80 Trac uses the public schema by default but you can specify a different schema in the connection string 81 82 postgres user pass server database schema yourschemaname 83 84 85 MySQL Connection String 86 87 If you want to use MySQL instead you ll have to use a 88 different connection string For example to connect to a MySQL 89 database on the same machine called trac that allows access to the 90 user johndoe with the password letmein the mysql connection string is 91 92 mysql johndoe letmein localhost 3306 trac 93 94 95 Source Code Repository 96 97 You ll first have to provide the type of your repository e g svn for Subversion 98 which is the default then the path where the repository is located 99 100 If you don t want to use Trac with a source code repository simply leave the path empty 101 the type information

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

  • TracFastCgi (diff) – Opus Project
    112 113 114 Note that you will need to add a new entry to fastcgi server for each separate Trac instance that you wish to run Alternatively you may use the TRAC ENV PARENT DIR variable instead of TRAC ENV as described above 115 and you may set one of the two in trac fcgi instead of in lighttpd conf 116 using bin environment as in the section above on Apache configuration 117 118 For using two projects with lighttpd add the following to your lighttpd conf 119 120 fastcgi server first 121 first 122 socket tmp trac fastcgi first sock 123 bin path fcgi binary 124 check local disable 125 bin environment 126 TRAC ENV path to projenv first 127 128 129 second 130 second 131 socket tmp trac fastcgi second sock 132 bin path fcgi binary 133 check local disable 134 bin environment 135 TRAC ENV path to projenv second 136 137 138 139 140 Note that field values are different If you prefer setting the environment 141 variables in the fcgi scripts then copy rename trac fcgi e g to 142 first fcgi and second fcgi and reference them in the above settings 143 Note that the above will result in different processes in any event even 144 if both are running from the same trac fcgi script 145 146 div class important 147 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 148 149 For authentication you should enable mod auth in lighttpd conf server modules select auth backend and auth rules 150 151 server modules 152 153 mod auth 154 155 156 157 auth backend htpasswd 158 159 Separated password files for each project 160 See Conditional Configuration in 161 http trac lighttpd net trac file branches lighttpd merge 1 4 x doc configuration txt 162 163 HTTP url first 164 auth backend htpasswd userfile path to projenv first htpasswd htaccess 165 166 HTTP url second 167 auth backend htpasswd userfile path to projenv second htpasswd htaccess 168 169 170 Enable auth on trac URLs see 171 http trac lighttpd net trac file branches lighttpd merge 1 4 x doc authentication txt 172 173 auth require first login 174 method basic 175 realm First project 176 require valid user 177 178 second login 179 method basic 180 realm Second project 181 require valid user 182 183 184 185 186 187 Note that lighttpd I use version 1 4 3 stopped if password file doesn t exist 188 189 Note that lighttpd doesn t support valid user in versions prior to 1 3 16 190 191 Conditional configuration is also useful for mapping static resources i e serving out images and CSS directly instead of through FastCGI 192 193 Aliasing functionality is needed 194 server modules mod alias 195 196 Setup an alias for the static resources 197 alias url trac chrome common usr share trac htdocs 198 199 Use negative lookahead matching all requests that ask for any resource under trac EXCEPT in 200 trac chrome common and use FastCGI for those 201 HTTP url trac chrome common 202 Even if you have other fastcgi server declarations for applications other than Trac do NOT use here 203 fastcgi server trac 204 trac 205 socket tmp trac fastcgi sock 206 bin path fcgi binary 207 check local disable 208 bin environment 209 TRAC ENV path to projenv 210 211 212 213 214 215 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 216 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 217 218 This is for handling multiple projects 219 alias url trac path to trac htdocs 220 221 fastcgi server projects 222 trac 223 224 socket tmp trac sock 225 bin path fcgi binary 226 check local disable 227 bin environment 228 TRAC ENV PARENT DIR path to parent dir of projects 229 230 231 232 And here starts the global auth configuration 233 auth backend htpasswd 234 auth backend htpasswd userfile path to unique htpassword file trac htpasswd 235 HTTP url projects login 236 auth require 237 238 method basic 239 realm trac 240 require valid user 241 242 243 244 245 246 Changing date time format also supported by lighttpd over environment variable LC TIME 247 248 fastcgi server trac 249 trac 250 socket tmp trac fastcgi sock 251 bin path fcgi binary 252 check local disable 253 bin environment 254 TRAC ENV path to projenv 255 LC TIME ru RU 256 257 258 259 260 For details about languages specification see trac TracFaq TracFaq question 2 13 261 262 Other important information like http trac lighttpd net trac wiki TracInstall this updated TracInstall page wiki TracCgi MappingStaticResources and this are useful for non fastcgi specific installation aspects 263 264 If you use trac 0 9 read http lists edgewall com archive trac 2005 November 005311 html about small bug 265 266 Relaunch lighttpd and browse to http yourhost example org trac to access Trac 267 268 Note about running lighttpd with reduced permissions 269 270 If nothing else helps and trac fcgi doesn t start with lighttpd settings server username www data server groupname www data then in the bin environment section set PYTHON EGG CACHE to the home directory of www data or some other directory accessible to this account for writing 271 272 273 Simple LiteSpeed Configuration 274 275 The FastCGI front end was developed primarily for use with alternative webservers such as http www litespeedtech com LiteSpeed 276 277 LiteSpeed web server is an event driven asynchronous Apache replacement designed from the ground up to be secure scalable and operate with minimal resources LiteSpeed can

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

  • TracFineGrainedPermissions (diff) – Opus Project
    permission policies are specified is quite critical 32 as policies will be examined in the sequence provided 33 34 A policy will return either True False or None for a given permission check 35 Only if the return value is None will the next permission policy be consulted 36 If no policy explicitly grants the permission the final result will be False 37 i e no permission 38 39 For example if the authz file contains 40 41 wiki WikiStart 42 WIKI VIEW 43 44 wiki PrivatePage 45 john WIKI VIEW 46 47 48 and the default permissions are set like this 49 50 john WIKI VIEW 51 jack WIKI VIEW 52 anonymous has no WIKI VIEW 53 54 55 Then 56 All versions of WikiStart will be viewable by everybody including anonymous 57 PrivatePage will be viewable only by john 58 other pages will be viewable only by john and jack 59 60 61 mod authz svn like permission policy 62 63 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 64 65 That kind of fine grained permission control needs a definition file which is the one used by Subversion s mod authz svn 66 More information about this file format and about its usage in Subversion is available in the http svnbook red bean com svnbook book html svn ch 6 sect 4 4 2 Subversion Book Per Directory Access Control 67 68 Example 69 70 71 r 72 73 branches calc bug 142 74 harry rw 75 sally r 76 77 branches calc bug 142 secret 78

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

  • TracImport (diff) – Opus Project
    data is imported from Bugzilla 26 27 bugs 28 bug activity field changes 29 bug attachments 30 user names and passwords put into a htpasswd file 31 32 The script provides a number of features to ease the conversion such as 33 34 PRODUCT KEYWORDS Trac doesn t have the concept of products so the script provides the ability to attach a ticket keyword instead 35 36 IGNORE COMMENTS Don t import Bugzilla comments that match a certain regexp 37 38 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 39 40 For more details on the available options see the configuration section at the top of the script 41 42 Sourceforge 43 44 Ticket data can be imported from Sourceforge using the http trac edgewall org browser trunk contrib sourceforge2trac py sourceforge2trac py script available in the contrib directory of the Trac distribution 45 46 Mantis 47 48 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 49 50 Mantis bugs can be imported using the attached script 51 52 Currently the following data is imported from Mantis 53 bugs 54 bug comments 55 bug activity field changes 56 attachments as long as the files live in the mantis db not on the filesystem 57 58 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 59 60 mantis2trac py has the same parameters as the bugzilla2trac py script 61 62 mantis2trac Imports a bug database from Mantis into Trac

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

  • TracIni (diff) – Opus Project
    trac ini file and delete the entries that would 21 otherwise override those set in the global file 22 23 24 Reference 25 26 This is a brief reference of available configuration options 27 28 TracIni 29 30 31 components components section 32 This section is used to enable or disable components provided by plugins as well as by Trac itself The component to enable disable is specified via the name of the option Whether its enabled is determined by the option value setting the value to enabled or on will enable the component any other value typically disabled or off will disable the component 33 34 The option name is either the fully qualified name of the components or the module package prefix of the component The former enables disables a specific component while the latter enables disables any component in the specified package module 35 36 Consider the following configuration snippet 37 38 components 39 trac ticket report ReportModule disabled 40 webadmin enabled 41 42 43 The first option tells Trac to disable the wiki TracReports report module The second option instructs Trac to enable all components in the webadmin package Note that the trailing wildcard is required for module package matching 44 45 See the Plugins page on About Trac to get the list of active components requires CONFIG VIEW wiki TracPermissions permissions 46 47 See also TracPlugins 48 49 ticket custom ticket custom section 50 51 In this section you can define additional fields for tickets See TracTicketsCustomFields for more details 52 53 ticket workflow ticket workflow section 54 since 0 11 55 56 The workflow for tickets is controlled by plugins 57 By default there s only a ConfigurableTicketWorkflow component in charge 58 That component allows the workflow to be configured via this section in the trac ini file 59 See TracWorkflow for more details 60 61 milestone groups milestone groups section 62 since 0 11 63 64 As the workflow for tickets is now configurable there can be many ticket states 65 and simply displaying closed tickets vs all the others is maybe not appropriate 66 in all cases This section enables one to easily create groups of states 67 that will be shown in different colors in the milestone progress bar 68 69 Example configuration the default only has closed and active 70 71 closed closed 72 closed order 0 sequence number in the progress bar 73 closed query args group resolution optional extra param for the query 74 closed overall completion true indicates groups that count for overall completion percentage 75 76 new new 77 new order 1 78 new css class new 79 new label new 80 81 active one catch all group is allowed 82 active order 1 83 active css class open CSS class for this interval 84 active label in progress Displayed label for this group 85 86 87 The definition consists in a comma separated list of accepted status 88 Also means any status and could be

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

  • TracInstall (diff) – Opus Project
    hasn t been updated since 0 84 so it may or may not work 75 76 Other Python Utilities 77 http docutils sourceforge net docutils version 0 3 9 for WikiRestructuredText 78 http pygments pocoo org Pygments for syntax highlighting although http silvercity sourceforge net SilverCity 0 9 7 and or http gnu org software enscript enscript html GNU Enscript are also possible Refer to TracSyntaxColoring for details 79 http pytz sf net pytz to get a complete list of time zones otherwise Trac will fall back on a shorter list from an internal time zone implementation 80 81 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 trac MailingList MailingList or trac IrcChannel IrcChannel 82 83 Please refer to the documentation of these packages to find out how they are best installed In addition most of the trac TracInstallPlatforms 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 84 85 Installing Trac 86 87 One way to install Trac is using setuptools 88 With setuptools you can install Trac from the subversion repository for example 89 to install release version 0 11 do 90 91 easy install http svn edgewall org repos trac tags trac 0 11 92 93 94 But of course the python typical setup at the top of the source directory also works 95 96 python setup py install 97 98 99 Note you ll need root permissions or equivalent for this step 100 101 This will byte compile the python source code and install it as an egg file or folder in the site packages directory 102 of your Python installation The egg will also contain all other resources needed by standard Trac such as htdocs and templates 103 104 The script will also install the wiki TracAdmin trac admin command line tool used to create and maintain wiki TracEnvironment project environments as well as the wiki TracStandalone tracd standalone server 105 106 Advanced Options 107 108 To install Trac to a custom location or find out about other advanced installation options run 109 110 easy install help 111 112 113 Also see http docs python org inst inst html Installing Python Modules for detailed information 114 115 Specifically you might be interested in 116 117 easy install prefix path to installdir 118 119 or if installing Trac to a Mac OS X system 120 121 easy install prefix usr local install dir Library Python 2 5 site packages 122 123 124 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

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

  • TracInterfaceCustomization (diff) – Opus Project
    css 74 href href chrome site style css 75 head 76 77 body py match body py attrs select 78 Add site specific header 79 div id siteheader 80 Place your header content here 81 div 82 83 select text 84 85 Add site specific footer 86 div id sitefooter 87 Place your footer content here 88 div 89 body 90 html 91 92 93 Those who are familiar with XSLT may notice that Genshi templates bear some similarities However there are some Trac specific features for example href chrome site style css attribute references template placed into environment s htdocs In a similar fashion chrome htdocs location is used to specify common htdocs directory from Trac installation 94 95 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 96 and modify them A site html can contain any number of such py match sections for whatever you need to modify This is all http genshi edgewall org Genshi so the docs on the exact syntax can be found there 97 98 99 Example snippet of adding introduction text to the new ticket form hide when preview 100 101 102 xml 103 form py match div id content and class ticket form py attrs select 104 py if test req environ PATH INFO newticket and not preview in req args 105 p Please make sure to search for existing tickets before reporting a new one p 106 py if 107 select 108 form 109 110 111 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 112 113 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 114 115 xml 116 form py match div id content and class ticket form py attrs select 117 xmlns xi http www w3 org 2001 XInclude 118 py if test req environ PATH INFO newticket and not preview in req args 119 xi include href site newticket cs xi fallback xi include 120 py if 121 select 122 form 123 124 125 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

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