How_to_update_cytoscape.org

Note: This page is only useful to Cytoscape core developers who have secure access that allows them to modify cytoscape.org

Instructions for updating cytoscape.org

Check out the cyto_web directory from Subversion.
- Note: do a clean check out periodically to make sure temporary files that build up on your local copy are not copied to the website. Also, directories may be added, which would not be checked out with an update.
- The command is:
  - ```
  svn co svn+ssh://gamay.ucsd.edu/cellar/common/svn/cyto_web/trunk cyto_web
```
Only modify content in this directory instead of directly on cytoscape.org. Remember to test and commit your changes. This allows us to collaboratively edit the website without overwriting other people's changes.
When you are done editing, deploy the changes to the website (see below)

Deploying to cytoscape.org

To deploy web site changes to cytoscape.org, from your workstation:

You need to set up a public/private SSH key pair to access the cytoscape.org website.
1. You can do this by going to http://cytoscape.org/menu. Contact Mike Smoot or another Cytoscape developer for the login and password.
2. Once logged in, click on the "Secure Shell" icon and then add your public key. Beware of spaces when you copy your key!
3. Once your keys are correctly configured you should be ready to deploy.
You need to have Apache ant installed and available from the command line (test by typing 'ant' on the command line and seeing if it is found).
Run the script to deploy
1. On Mac OS X or Linux, type: (preferred method)
  - ```
  deploy.sh
```
  This does two things:
  1. runs ant config_prod, so that everything is set up for production.
  2. runs rsync to incrementally and securely update cytoscape.org
    rsync is much more efficent and secure than FTP. So this is the preferred way to do deployments.
2. On Windows, type:
  - ```
  ant deploy -Dpassword=[value]
```
  Where [value] is replaced with the actual password This does two things:
  1. runs ant config_prod, so that everything is set up for production.
  2. copies files over via the ant FTP task. This is slow, so the prefered way to deploy is from a unix based operating system using rsync, above.

Note: you can also use any FTP or SCP client to post files. This might be useful for changes to single files - just make sure the file is in CVS or it will be overwritten next time someone uses the deploy script.