• SVN - Subversion Instructions (was CVS)#

  • rthrash Reply #1, 7 years, 1 month ago

    Reply
    Our preliminary CVS server can be accessed via the following method:

    host: victorland.com
    access via: SSH2 port 22
    CVS root: /var/lib/cvs

    initial module: modx

    You'll need to create an SSH2 DSA key pair in order to get access to the CVS server.

    In Mac OS X, download the latest version of SSH Agent and MacCVS Client (links from www.versiontracker.com).

    In SSH Agent, generate your SSH2 key pair by selecting File > New > Identity. This will prompt you to save a file in ~/.ssh. Choose DSA as the type and you can leave the default 2048 bits. I named mine "id_dsa" and saved it in the default location.

    To share your public key (ending in .pub ... never share the private key part!), you'll need to copy the contents of the file, most easily done via using the terminal command:
    tail ~./ssh/id_dsa.pub


    My public key looks like the following:
    ssh-dss AAAAB3NzaC1kc3MAAAEBALKGhzNbY6vpkwswFeqfCjGEue7WB3r0ve5yyaKNC9FFq8QViCST
    4/Un6D3Da1SHEF9rJjyekkv66sBsahlwf3oLhOOuj4Vw/cg5il44jiw1rBqZgTgLFA/KvYvEIl6Ik6Ga
    M0l7wza2uly7R/sP4yVhXt9ydRj2KqVU60SCoz7ho8JbRM/x7s1ZeoWpluP3OgLKGoQgz3aFTgkUwUIQ
    bCgJ0lN6tzZ4Tq1cR1Oaxmidch5Hv+g2ch+etG5TSdozwwD/7iy2N6PItFVkDjHKUSmLxX9bX2badqaJ
    3JAtimBJXzi8ZqmgM80+No2aowpCpOfNWaT2pL7Z9z3h669PDIMAAAAVAKRRhWQ0lCf/WGSa9AoNK7RF
    gIE1AAABAFABuWWXdcMN5iVSa0hHcFjsZOVsRsGGFr50Zj3bzKSceVpMJQfLcd9soF30BgsTmo+SoKnh
    N27qn137i9mm1/6JYOb6s1ujojmbq+0fQwyptxuuoz7IbcrPOpDPE1cgP2mfHFPtffyPm8B4kxEudEIb
    efsQj+Lkj4KhS/192loLzBNdWSG0gLDl9MZTSrld//NgDBFyhyn5kZrEalibW+qdWXjRrcUSriXsyOyI
    GV7KJKTym4ib+1tEluzEK9u56hNcLMK2xUNZkvH7hFsX1VlyEl7pwmn5Dhb57+OfOqmxxnHIp+xQ5XCA
    nqilT/sWePaQsDNHZIqosbr/5ixTxiUAAAEAJF+sCPmc1emC1Epo20JVYEae7f55R4JtsCjc9GXvVeSN
    g5R3hMHtr+q2X1zvLNNgL+/C6jsiNFtIP+jZ3lmHaR2Knjc2WlNSGSfPWcZ3mNd66XlvX4buOipQp2+9
    IRiTKJ2fXnZukL0gR6/GbhhSGM8AXHEpbCksxxzEVHaj3VclzhHbilhMHOQdx12kKEdW3IEAGPQ3l6V7
    swMIYh0gz1cjK1Tqm66GJP75Jwm+Qeg8hyZe8sHQwthzWEF8QYCnArJJjWnoZLQDXt6WO6SNIhVGxAWJ
    wpCxa2TspXqUMEfnMl2VBu8vBRJhD3rMVbStZopi7hiB3Nf4qBZ7C6pOqg== rthrash@AluBook.local
    


    Email this public key to victor@victorland.com, along with your requested SSH login name. Once you receive word back that it's been installed, test it by entering the following command in your terminal:
    ssh username@victorland.com

    Replace "username" above with your actual username. You should be prompted to add victorland.com to your known hosts file. Do so (this is key to making it work in MacCVS client).

    Here's a screenshot of my Mac CVS client access configuration:

    Working with MacCVS, I typically follow the following general workflow:
      * Create the connection profile (above)
      * Select the Repository > Check Out... menu item
      * Enter "modx" as the module name
      * Select Library/Webserver/Documents as my Folder (this is the web root on Mac OS X systems if anyone is curious)
      * Leave the rest of the settings as is and you're done
      [/list:u]

      MacCVS Client will then create a directory in your Web Root folder called "modx" and download the files. This is called your "sandbox".

      Before starting to work with the files, I always update my sandbox first to make sure you have the latest/greatest version of the files:
      [list]
      * Menu: File > Open Sandbox (cmd-o)
      * Select the "modx" folder in your web root
      * A new window opens showing the files in your sandbox
      * Select the top "modx" directory in this window
      * Menu: Sandbox > Update (cmd-u)
      [/list:u]

      You'll now have an updated copy. When you make changes to the files in your local sandbox, they'll show up red in MacCVS Client. If you want to check those/commit those changes back to the CVS repository, you select the file or files in the Sandbox window and use the menu: Sandbox > Commit... (cmd-i).

      Anyone want to post a Quick Start Guide for Putty on Windows?
    [/list]


  • opengeek Reply #2, 7 years, 1 month ago

    Reply
    Here are some instructions for using PuTTyGen on Windows to generate a proper SSH2 public key:

    First, if you don't already have it, download PuTTy from http://www.chiark.greenend.org.uk/~sgtatham/putty/, and install it on your system. I used the Windows installer version. Make sure you get the whole package that includes all the various components.

    Next, run PuttyGen.exe and at the bottom of window, select the following values:
      Type of key to generate: SSH2 DSA[/list:u]
      [list]Number of bits in a generated key: 2048[/list:u]
      Click Generate and move the mouse randomly over the blank area of the field labeled Key until the process is done. This generates random seeding for the generation of your private key.

      Once the key has been generated. Click Save Private Key, and choose a secure location (but that does not have any spaces in the folder names, I found out the hard way) to save your file that you should never share or make accessible to anyone. The saved file will have a PPK extension.

      You can Save Public Key as well, but this is not important. What is important is the field labeled Key which now contains the public key part that you need to provide. Just cut and paste this public key part into a file or message, and send it in.

      For more detailed information than I can provide on using PuTTy and WinCVS, go to http://www.bsdconsulting.no/wincvs-ssh/ for a great tutorial.
    [/list]


  • Zombie Reply #3, 7 years, 1 month ago

    Reply
    Quick question: The key I sent you was 1024 bits because that's what was mentioned in one of the previous posts. Should I regenerate a 2048 bit one?


  • rthrash Reply #4, 7 years, 1 month ago

    Reply
    If it works, let it work. Otherwise, we'll have to wait 'til Victor gets back from Sonoma on Monday.



  • Zombie Reply #5, 7 years, 1 month ago

    Reply
    Well, I never heard back after sending the new public key this morning.

    Any ideas if the new key worked?


  • rthrash Reply #6, 7 years, 1 month ago

    Reply
    I have no idea... he was in a hurry to get out of town.

    Have you tried connecting?


  • Zombie Reply #7, 7 years, 1 month ago

    Reply
    Have you tried connecting?

    Just sat down to do that very thing, Sir. I'll report back once I have a result.


  • Zombie Reply #8, 7 years, 1 month ago

    Reply
    No joy, it never accepts my key.

    I guess I'll wait til Monday. -sigh-


  • sottwell Reply #9, 7 years, 1 month ago

    Reply
    I just keep getting a "timeout", but I'm not real sure what I'm supposed to be using for a password. When I gave Victor my public key and username, there was no mention of a password. I think I missed something somewhere.


  • opengeek Reply #10, 7 years, 1 month ago

    Reply
    I just keep getting a "timeout", but I'm not real sure what I'm supposed to be using for a password. When I gave Victor my public key and username, there was no mention of a password. I think I missed something somewhere.

    The password you need is for your private key. You should have provided a passphrase for the private key when you created it.