That was what I tried earlier as all the instructions I saw were telling to do "Enable DAV" (or something like that with mod_dav) in the apache config. However, I currently use Zend Studio with SFTP connection and I would not mind continuing to have secure method with connecting to the server. Therefore using apache is not mandatory. I do not really know what transports are available.

Zend Studio supports both CVS and SVN, but for me CVS seems even more difficult....and lots of comments I've seen, favor SVN instead.

Petri


CM Banker wrote:
What transports desired?? I assume you want to back it behind apache and make it available through apache?

On Feb 5, 2008 4:39 PM, Petri Laihonen <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

    Currently RHEL3 and RHEL4
    With next new server most likely RHEL5.

    All running latest version of apache available from the standard
    repos.

    Petri


    CM Banker wrote:
    Petri,

    Your supported platforms and protocols have an impact on how
    easy  a setup can be...  What targets and platforms are you
    shooting for?


    -C

    On Feb 5, 2008 2:38 PM, Petri Laihonen <[EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>> wrote:

        I've been thinking about starting to use SVN for long time,
        but never found a good step-by-step instructions how to set
        it up successfully. (or did not know how to use correctly)
        All manuals etc. I've followed, never resulted a working
        solution. The closest I ever got was producing all kinds of
        errors when trying to submit something. I do not remember the
        errors anymore, but none of the solutions provided for the
        error worked.

        Does anyone know a good (working) step-by-step instructions
        for SVN?
        I have several different web projects going on simultaneously
        and also need the ability to test online before submitting to
        production.

        Petri


        CM Banker wrote:



        SVN is a good choice.... I've been using it for almost 3
        years...  I have not run across any need to configure it as
        you describe...but


        http://svnbook.red-bean.com/en/1.0/svn-book.html#svn-ch-6-sect-4.4.1

        search for "Example 6.3. A sample configuration for mixed
        authenticated/anonymous access."

        I think it describes what you need.


        On Feb 5, 2008 1:38 PM, Dustin Puryear
        <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

            Any Subversion pros here? Someone I know wants to be
            able to define
            rights such as:

            * user A can add/modify but not delete files
            * user B can do anything

            I've never even tried this with SVN. Ideas?

            --
            Puryear Information Technology, LLC
            Baton Rouge, LA * 225-706-8414
            http://www.puryear-it.com

            Author, "Best Practices for Managing Linux and UNIX Servers"
              http://www.puryear-it.com/pubs/linux-unix-best-practices

            Identity Management, LDAP, and Linux Integration

            _______________________________________________
            General mailing list
            [email protected] <mailto:[email protected]>
            http://mail.brlug.net/mailman/listinfo/general_brlug.net


        ------------------------------------------------------------------------

        _______________________________________________
        General mailing list
        [email protected] <mailto:[email protected]>
        http://mail.brlug.net/mailman/listinfo/general_brlug.net

        _______________________________________________
        General mailing list
        [email protected] <mailto:[email protected]>
        http://mail.brlug.net/mailman/listinfo/general_brlug.net


    ------------------------------------------------------------------------
    _______________________________________________ General mailing
    list [email protected] <mailto:[email protected]>
    http://mail.brlug.net/mailman/listinfo/general_brlug.net

    _______________________________________________
    General mailing list
    [email protected] <mailto:[email protected]>
    http://mail.brlug.net/mailman/listinfo/general_brlug.net


------------------------------------------------------------------------

_______________________________________________
General mailing list
[email protected]
http://mail.brlug.net/mailman/listinfo/general_brlug.net
_______________________________________________
General mailing list
[email protected]
http://mail.brlug.net/mailman/listinfo/general_brlug.net

Reply via email to