Updating the InaSAFE website should be automated

[timlinux]

In describing the process to update the website to Marco I realised that there are too many steps and it is quite likely for something to go wrong, so I think we should automate the process as much as possible. For example we should have a script invoked with a make target:

make update-website

Here is the log from irc of the general logic that should be implemented for the script:

08:39 <@timlinux> cd ..
08:39 <@timlinux> test if inasafe-gh-pages dir exists
08:40 <@timlinux> if no clone inasafe
08:40 <@timlinux> into inasafe-gh-pages
08:40 <@timlinux> cd inasafe-gh-pages
08:40 <@timlinux> git branch --trach gh-pages origin/gh-pages
08:40 <@timlinux> git checkout gh-pages
08:40 <@timlinux> if yes
08:41 <@timlinux> cd inasafe-gh-pages
08:41 <@timlinux> git pull
08:41 <@timlinux> cd ..
08:41 <@timlinux> cd inasafe-dev
08:41 <@timlinux> make docs
08:41 <@timlinux> cd ..
08:41 <@timlinux> cd inasafe-gh-pages
08:41 <@timlinux> rm all generated content
08:42 <@timlinux> cp all generated content from ../inasafe-dev/docs/build/html
08:42 <@timlinux> git status
08:42 <@timlinux> git add any newly arrived files
08:42 <@timlinux> git commit -m 'Automated docs update'
08:42 <@timlinux> git push
08:42 <@timlinux> cd ..
08:42 <@timlinux> cd inasafe-dev

Ultimately we could run this make target using jenkins whenever a commit happens or nightly.

[ismailsunni]

May be we can put the script for generating .rst file (for API doc) https://github.com/AIFDR/inasafe/blob/master/scripts/gen_rst_script.py before make docs so the API documentation is updated also.

[mbernasocchi]

ok