Please double check the docs deployment environment is correct

[timlinux]

@rduivenvoorde also can you double check that we have these workflows set up right:

• commits to master get published automatically to docs.inasafe.org ? (nightly)
• commits to develop get published automatically to staging.docs.inasafe.org ? (hourly)

And also double check

• in the configs that the master nginx is pointing to the /home/data/docs.inasafe.org folder
• the staging site is being served off kartoza5 and has the correct nginx etc configs

Note we want only production sites to happen on inasafe-docker server

• Staging service description https://github.com/inasafe/inasafe/wiki/Service-staging.docs.inasafe.org
• Live service description https://github.com/inasafe/inasafe/wiki/Service-docs.inasafe.org

CC

@Charlotte-Morgan @adissadis

[Charlotte-Morgan]

hi @timlinux - it would be great the above workflow was in place. It would mean that we can work on docs in dev but not need to do all our own compiling etc. This means we can work from remote locations and not need all the various software installed .. yay would have made life much easier with the recent review of socialisation training

[timlinux]

@rduivenvoorde also please check the service descriptions are up to date

[rduivenvoorde]

ok, today created a dev build on 213.133.111.115 rebuilding hourly

also updated dns at cloudflare, BUT deliberatly NOT caching it there. So the hourly build should be reflected at staging.docs.inasafe.org

[rduivenvoorde]

removed staging build env from 5.9.160.107 == inasafe-docker

created new env for master in /home/data/docs.inasafe.org

fixed /etc/nginx/docs.inasafe.org.conf to point to /home/data/docs.inasafe.org again

Still TODO: create cronjob for pulling every hour (now only building every hour)

[timlinux]

Thanks for this @rduivenvoorde

@Charlotte-Morgan and @adissadis I though we had agreed to get rid of the user docs in favour of maintaining good context help close to the code. Can we remove those or did I miss something?