Home My Page Projects Code Snippets Project Openings SML/NJ
Summary Activity Forums Tracker Lists Tasks Docs Surveys News SCM Files

SCM Repository

[smlnj] Diff of /pages/trunk/DEV/sf-howto.html
ViewVC logotype

Diff of /pages/trunk/DEV/sf-howto.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 965, Wed Oct 17 09:55:33 2001 UTC revision 966, Thu Oct 18 14:42:36 2001 UTC
# Line 25  Line 25 
25  This directory contains subdirectories <code>htdocs</code> and <code>cgi-bin</code>.  This directory contains subdirectories <code>htdocs</code> and <code>cgi-bin</code>.
26  <p>  <p>
27    
28  <h3>Login to sourceforge user account</h3>  <h3>Logging in to your sourceforge user account</h3>
29  <pre>  <pre>
30     ssh -l loginname smlnj.sourceforge.net     ssh -l loginname shell.sourceforge.net
31  </pre>  </pre>
32  Your home directory will look something like: <code>/home/users/m/ma/macqueen</code>.  Your home directory will look something like: <code>/home/users/m/ma/macqueen</code>.
33    <p>
34    You can abbreviate the command to (e.g.)
35    <pre>
36       ssh sf-shell
37    </pre>
38    by defining sf-shell as a host alias in your .ssh/config file:
39    <pre>
40        Host = sf-shell
41        HostName = shell.sourceforge.net
42        User = loginname
43    </pre>
44    <p>
45    <h3>Moving files to sourceforge</h3>
46    You can copy an individual html source file (localfile) to your
47    sourceforge home directory by executing a command like:
48    <pre>
49       scp localfile macqueen@smlnj.sourceforge.net:/home/users/m/ma/macqueen
50    </pre>
51    I have not been able to use ftp (from SF) to transfer files into SF.
52    
53  <h3>Setting up CVS access</h3>  <h3>Setting up CVS access</h3>
54  <ol>  <ol>
# Line 46  Line 65 
65  <pre>  <pre>
66       export CVS_RSH=ssh       export CVS_RSH=ssh
67  </pre>  </pre>
68    <p>
69  <li> Run ssh-agent and ssh-add for convenience, to avoid having to repeatedly  <li> Run ssh-agent and ssh-add for convenience, to avoid having to repeatedly
70  type in your ssh passphrase or SourceForge password:  type in your ssh passphrase or SourceForge password:
71  <pre>  <pre>
# Line 60  Line 80 
80  Note that some versions of ssh do not support the -p flag, in which case  Note that some versions of ssh do not support the -p flag, in which case
81  you will have to run ssh-add interactively and type in your pass phrase.  you will have to run ssh-add interactively and type in your pass phrase.
82  Unfortunately, the version of ssh available on the SourceForge shell servers  Unfortunately, the version of ssh available on the SourceForge shell servers
83  is one of these.  is one of these, so ssh-add has to be run manually after login.
84    <p>
85    <li> Create a host entry for cvs.sourceforge.net in your ssh config file (.ssh/config)
86    like the following (replacing loginname with your SF user name, as usual):
87    <pre>
88        Host = sf-smlnj
89        HostName = cvs.smlnj.sourceforge.net
90        User = loginname
91    </pre>
92    This defines a standard alias for the cvs host that agrees with that used
93    the CVS/Root files (in htdocs, for instance).
94    <p>
95  <li> Set CVSROOT:  <li> Set CVSROOT:
96  <pre>  <pre>
97       export CVSROOT=<SF loginname>@cvs.smlnj.sourceforge.net:/cvsroot/smlnj       export CVSROOT=sf-smlnj:/cvsroot/smlnj
98  </pre>  </pre>
99  <li> Execute cvs commands (without needing -d arguments, passwords,  Note the use of the alias "sf-smlnj" defined in the config file from the
100  or pass phrases), e.g.:  previous item.
101    <p>
102    <li> Now you can execute cvs commands without needing -d arguments, passwords,
103    or pass phrases, e.g.:
104  <pre>  <pre>
105       cvs update bugs       cvs update bugs
106  </pre>  </pre>
107  </ol>  </ol>
108    In order to execute cvs commands on the SourceForge shell server, you
109    should run ssh-keygen from your SF account to generate a new ssh key, and
110    then add that key to the end of your .ssh/authorized_keys file.  You can
111    also define CVS_RSH and run ssh-agent in your .profile at
112    SourceForge to make things simpler.
113    
114  <h3> Updating web pages </h3>  <h3> Updating web pages </h3>
115  You can copy an individual html source file (localfile) to the smlnj  The htdocs directory in the smlnj project home directory (/home/groups/s/sm/smlnj)
116  sourceforge site by executing a command like:  contains the web pages for the project.  These web pages can be accessed using
117  <pre>  either of the following URLs:
118     scp localfile loginname@smlnj.sourceforge.net:/home/groups/s/sm/smlnj/htdocs/  <blockquote>
119  </pre>  <a href="http://www.smlnj.org">http://www.smlnj.org</a><br>
120  However, updating the site web pages should be done by working on a  <a href="http://smlnj.sourceforge.net">http://smlnj.sourceforge.net/index.html</a>
121  checked-out copy of the web pages (module "pages" in the project  </blockquote>
122  CVS repository).  The htdocs directory is a CVS working directory created by checking out
123    the htdocs module from the project CVS repository.  The Bell Labs copy
124    (in /home/sml/Doc/WWW/smlnj) is also checked-out from the repository ("htdocs"
125    and "smlnj" are both aliases of the pages module in the repository).  If you
126    have extensive edits to perform on the web pages, we recommend that you check
127    out your own private working copy, make the edits, test them, and commit the changes.
128    After the changes are commited, "cvs update" must be performed in
129    the two directories
130    <blockquote>
131    /home/groups/s/sm/smlnj/htdocs  (at SF)<br>
132    alice:/cm/cs/what/smlnj         (at Bell Labs)
133    </blockquote>
134    to synchronize them with the changed repository.  You can do the
135    update on the htdocs directory yourself as described in the next
136    paragraph, but you may need to send mail to Bell Labs to have the
137    update done on that copy until we set up automatic email notifications
138    of commits to the web pages repository.
139  <p>  <p>
140  Then to actually update the pages, you login to your SourceForge account  To actually update the pages at SF, you login to your SF account
141  and do  and do (e.g.)
142  <pre>  <pre>
143     cd /home/groups/s/sm/smlnj/htdocs     cd /home/groups/s/sm/smlnj/htdocs
144     ... set up cvs ...     ... set up cvs ...
145     export CVSROOT=<loginname>@cvs.smlnj.sourceforge.net:/cvsroot/smlnj     export CVSROOT=sf-smlnj:/cvsroot/smlnj
146     cvs update pages     cvs update htdocs
147  </pre>  </pre>
 In order to do the cvs operations on your SourceForge shell server, it  
 is a good idea to run ssh-keygen there to generate a new ssh key, and  
 then add that key to the end of your .ssh/authorized_keys file.  You can  
 also define CVS_RSH and run ssh-agent in your .profile at  
 SourceForge to make things simpler.  Since the ssh at SourceForge does  
 not appear to accept a pass phrase on standard input, you'll have to run  
 ssh-add interactively after you log in.  
148  <p>  <p>
149      <hr>      <hr>
150      <address><a href="mailto:macqueen@users.sourceforge.net">Dave MacQueen</a></address>      <address><a href="mailto:macqueen@users.sourceforge.net">Dave MacQueen</a></address>

Legend:
Removed from v.965  
changed lines
  Added in v.966

root@smlnj-gforge.cs.uchicago.edu
ViewVC Help
Powered by ViewVC 1.0.0