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".
  • TracBackup – Opus Project
    Notification Since Trac uses a database backend some extra care is required to safely create a backup of a project environment Luckily trac admin has a command to make backups easier hotcopy Note Trac uses the hotcopy nomenclature to match that of Subversion to make it easier to remember when managing both Trac and Subversion servers Creating a Backup To create a backup of a live TracEnvironment simply run trac admin path to projenv hotcopy path to backupdir trac admin will lock the database while copying The resulting backup directory is safe to handle using standard file based backup tools like tar or dump restore Please note that hotcopy command does not overwrite target directory and when such exists hotcopy ends with error Command failed Errno 17 File exists This is discussed in 3198 Restoring a Backup Backups are simply a copied snapshot of the entire project environment directory including the SQLite database To restore an environment from a backup simply stop the process running Trac i e the Web server or tracd restore the directory structure from the backup and restart the service Note Automatic backup of environments that don t use SQLite as database backend is not supported

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


  • TracImport – Opus Project
    imported from Bugzilla bugs bug 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

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

  • TracFineGrainedPermissions – Opus Project
    permission policies are specified is quite 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

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

  • TracAdmin – Opus Project
    repospath Create and initialize a new environment from arguments hotcopy backupdir Make a hot backup copy of an environment resync Re synchronize trac with the repository resync rev Re synchronize only the given rev upgrade Upgrade database to current version deploy directory Extract static resources from Trac and all plugins permission list user List permission rules permission add user action action Add a new permission rule permission remove user action action Remove permission rule wiki list List wiki pages wiki remove page Remove wiki page wiki export page file Export wiki page to file or stdout wiki import page file Import wiki page from file or stdin wiki dump directory Export all wiki pages to files named by title wiki load directory Import all wiki pages from directory wiki upgrade Upgrade default wiki pages to current version ticket remove number Remove ticket ticket type list Show possible ticket types ticket type add value Add a ticket type ticket type change value newvalue Change a ticket type ticket type remove value Remove a ticket type ticket type order value up down Move a ticket type up or down in the list priority list Show possible ticket priorities priority add value Add a priority value option priority change value newvalue Change a priority value priority remove value Remove priority value priority order value up down Move a priority value up or down in the list severity list Show possible ticket severities severity add value Add a severity value option severity change value newvalue Change a severity value severity remove value Remove severity value severity order value up down Move a severity value up or down in the list component list Show available components component add name owner Add a new component component rename name newname Rename a component component remove name Remove

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

  • WikiRestructuredText – Opus Project
    installed If not already available on your operating system you can download it at the RST Website Install docutils using easy install docutils Do not use the package manager of your OS e g apt get install python docutils because Trac will not find docutils then More information on RST reStructuredText Website http docutils sourceforge net rst html RST Quick Reference http docutils sourceforge net docs rst quickref html Using RST in Trac To specify that a block of text should be parsed using RST use the rst processor TracLinks in reStructuredText Trac provides a custom RST directive trac to allow TracLinks from within RST text Example rst This is a reference to a ticket a ticket trac 42 Trac allows an even easier way of creating TracLinks in RST using the custom trac role Example rst This is a reference to ticket 12 trac To learn how to use Trac see TracGuide trac For a complete example of all uses of the trac role please see WikiRestructuredTextLinks Syntax highlighting in reStructuredText There is a directive for doing TracSyntaxColoring in RST as well The directive is called code block Example rst code block python class Test def TestFunction self pass Will result in the below code block python class Test def TestFunction self pass Wiki Macros in reStructuredText For doing Wiki Macros in RST you use the same directive as for syntax highlighting i e code block To work you must use a version of trac that has 801 applied Wiki Macro Example rst code block RecentChanges Trac 3 Will result in the below 09 28 09 TracUnicode TracFineGrainedPermissions TracBackup Or a more concise Wiki Macro like syntax is also available rst code block RecentChanges Trac 3 Bigger RST Example The example below should be mostly self explanatory rst FooBar

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

  • TracNotification – Opus Project
    the SMTP server can handle local 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

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

  • TracModWSGI – Opus Project
    directory to Apache You can create 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

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

  • TracRevisionLog – Opus Project
    to what has been done on the branch It s also possible to indicate that one wants to see what happened before a Copy or Rename change by selecting the Follow copies mode This will cross all copies or renames changes Each time the name of the path changes there will be an additional indentation level That way the changes on the different paths are easily grouped together visually It s even possible to go past an Add change in order to see if there has been a Delete change on that path before that Add This mode corresponds to the mode called Show only adds moves and deletes While quite useful at times be aware that this operation is quite resource intensive Finally there s also a checkbox Show full log messages which controls whether the full content of the commit log message should be displayed for each change or only a shortened version of it The Revision Log Information For each revision log entry there are 7 columns shown The first column contains a pair of radio buttons and should used for selecting the old and the new revisions that will be used for viewing the actual changes A color code similar to the one used for the changesets indicating kind of change Clicking on this column refreshes the revision log so that it restarts with this change The Date at which the change was made The Revision number displayed as xyz This is a link to the TracBrowser using that revision as the base line The Changeset number displayed as xyz This is a link to the TracChangeset view The Author of the change The Log Message which contains either a summary or the full commit log message depending on the value of the Show full log

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