From 62309ac829c57c6315d0d33a374ccb4802f28b47 2015-01-09 16:53:08 From: Michael A. Guravage Date: 2015-01-09 16:53:08 Subject: [PATCH] Elaborated on how to archive a site. --- diff --git a/README.txt b/README.txt index 305689eb81a0e4095bd41cae245e6ef56e4b0099..5e3d984994aa97bd5adb5b414a5402fc2acddf84 100644 --- a/README.txt +++ b/README.txt @@ -80,13 +80,31 @@ you browser to the url: localhost:8000. Uploading the generated HTML to a server ---------------------------------------- -The Pelican Makefile contains several targets for uploading its generated HTML. List all make's targets with:: +The Pelican Makefile contains several targets for uploading its +generated HTML. List all make's targets with:: make -n To use rsync, edit the Makefile and customize the values of SSH_HOST, -SSH_USER anad SSH_Target_DIR. Of course, this assumes you've already -spoken with someone at ITF to arrange a CWI vhost to host your site. +SSH_USER and SSH_Target_DIR. + + +If CWI is hosting your site, SSH_HOST and SSH_TARGET_DIR name the host +and document root configured for you by ITF staff. + + +Archiving your site +------------------- + +The url from which you cloned the cwi-pelican-template repository is +called the clone's 'origin.' To archive your clone you should change +its origin to point to a new repository and push it there. For +example, if I had created a new repository at scm.cwi.nl named +itf-pelican-site, I could push my site there with the following two +commands:: + +git remote add origin https://guravage@scm.cwi.nl/ITF/itf-pelican-site +git push -u origin master Creating new Pelican projects