is a wiki engine based on a cvs/svn a good idea?

Discussion in 'Python' started by =?ISO-8859-2?Q?piotr_mali=F1ski?=, May 31, 2006.

  1. I'm planning to wite a fully featured wiki in Python in one of
    frameworks. I've seen some notes about wiki/documentation management
    scripts that use SVN as a data storage/versioning.
    I've been using SVN a bit but I don't know if it's a good idea to use
    it in a wiki engine. Pro: versioning / diffs, Cons: you need your own
    svn/cvs repository, can pyLucene or Xapwrap index this?
    =?ISO-8859-2?Q?piotr_mali=F1ski?=, May 31, 2006
    #1
    1. Advertising

  2. =?ISO-8859-2?Q?piotr_mali=F1ski?=

    Damjan Guest

    > I'm planning to wite a fully featured wiki in Python in one of
    > frameworks. I've seen some notes about wiki/documentation management
    > scripts that use SVN as a data storage/versioning.


    Cool

    > I've been using SVN a bit but I don't know if it's a good idea to use
    > it in a wiki engine. Pro: versioning / diffs, Cons: you need your own
    > svn/cvs repository, can pyLucene or Xapwrap index this?


    You can certanly index the svn checkout if nothing else.

    --
    damjan
    Damjan, May 31, 2006
    #2
    1. Advertising

  3. piotr maliski a écrit :
    > I'm planning to wite a fully featured wiki in Python


    Then first have a look at both moinmoin and Trac. Good part of the job
    is already done.

    > in one of
    > frameworks. I've seen some notes about wiki/documentation management
    > scripts that use SVN as a data storage/versioning.
    > I've been using SVN a bit but I don't know if it's a good idea to use
    > it in a wiki engine.


    This has been discussed for Trac, cf:
    http://projects.edgewall.com/trac/wiki/TighterSubversionIntegration
    http://projects.edgewall.com/trac/wiki/WhySQLite

    > Pro: versioning / diffs,
    > Cons: you need your own svn/cvs repository,
    > can pyLucene or Xapwrap index this?
    Bruno Desthuilliers, Jun 1, 2006
    #3
  4. =?ISO-8859-2?Q?piotr_mali=F1ski?=

    R. P. Dillon Guest

    TWiki, written in perl, makes extensive use of versioning/diff
    functionality you mention through the use of RCS, which, IIRC, is the
    basis for CVS. This method eliminates the need for the repository as
    such, and merely requires the presence of the RCS files (and RCS).

    Unless you _want_ to host your data on a separate machine than the one
    hosting the wiki, you might consider RCS as an alternative to CVS.

    OTOH, it is clearly a good idea to base your software on such a tool,
    given that TWiki does it and has proven to be quite successful. =)

    Rick

    piotr malin'ski wrote:
    > I'm planning to wite a fully featured wiki in Python in one of
    > frameworks. I've seen some notes about wiki/documentation management
    > scripts that use SVN as a data storage/versioning.
    > I've been using SVN a bit but I don't know if it's a good idea to use
    > it in a wiki engine. Pro: versioning / diffs, Cons: you need your own
    > svn/cvs repository, can pyLucene or Xapwrap index this?
    R. P. Dillon, Jun 2, 2006
    #4
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Replies:
    1
    Views:
    360
    Sybren Stuvel
    Apr 10, 2006
  2. Andrea Gavana

    Simple SVN/CVS-like library in Python?

    Andrea Gavana, Feb 7, 2007, in forum: Python
    Replies:
    0
    Views:
    267
    Andrea Gavana
    Feb 7, 2007
  3. Replies:
    10
    Views:
    1,220
    Big K
    Feb 2, 2005
  4. Robert Oschler

    Wiki engine used by Ruby Wiki?

    Robert Oschler, Jun 17, 2004, in forum: Ruby
    Replies:
    3
    Views:
    219
    Erik Veenstra
    Jun 25, 2004
  5. Rob Muhlestein
    Replies:
    0
    Views:
    71
    Rob Muhlestein
    Dec 30, 2006
Loading...

Share This Page