| | 59 | == ROPP deployment === |
| | 60 | |
| | 61 | ROPP can be deployed using the following command: |
| | 62 | |
| | 63 | {{{ |
| | 64 | fab -H graswww2 -f /usr/local/bin/deploy_romsaf_web.py deploy_ropp |
| | 65 | }}} |
| | 66 | |
| | 67 | The command will call `prepare_ropp` and `backup_ropp` and install the new ROPP version. |
| | 68 | |
| | 69 | In case of errors use: |
| | 70 | {{{ |
| | 71 | fab -H graswww2 -f /usr/local/bin/deploy_romsaf_web.py restore_ropp |
| | 72 | }}} |
| | 73 | |
| | 74 | To rollback the changes |
| | 75 | |
| | 76 | == Website Deployment, Major Change == |
| | 77 | |
| | 78 | For major website releases e.g. version changes from 3.0 to 3.1. First the version needs to be tagged and the file `https://svn.grassaf.org/garf/branches/operational/externals.txt` needs to be updated with the tagged name and checked in. |
| | 79 | |
| | 80 | Then run: |
| | 81 | {{{ |
| | 82 | fab -H graswww2 -f /usr/local/bin/deploy_romsaf_web.py deploy_website |
| | 83 | }}} |
| | 84 | |
| | 85 | |
| | 86 | |
| | 87 | |
| | 88 | |
| | 89 | |