Changes between Version 22 and Version 23 of WhySQLite

Timestamp:

Oct 28, 2010, 10:18:07 AM (14 years ago)

Author:

anonymous

Comment:

—

WhySQLite

@@ -68 +68 @@
    * [-] "Other problems" is not an argument (haui at haumacher.de)
    * [-] If there really are "other problems", this could be solved by using a repository different from the project repository for storing issues and wiki pages.
+   * [+] This would require the user running the webserver to have write access to the subversion repo. You really don't want to do that if you care about security.
+   * [+] Trac can only use direct file access to access subversion repos (correct me if I'm wrong), your subversion repo may be using an incompatible access method (e.g. we use ssh+svn so write access is only possible by the ssh user)
  6. If you use a continuous build system such as [http://cruisecontrol.sourceforge.net/ CruiseControl], all of a sudden changing wiki pages (and thus checking them into SVN) would cause spurious rebuilds of your project.
    * [-] CruiseControl (and presumably other continuous build systems) can be configured to only rebuild when a certain subset of the repository changes.  For example you can configure CruiseControl to only look at changes to the "trunk/src" directory, not the "trunk/wiki" directory.