Setup Continous Deployment for the website

ffledgling commented 9 years ago

Current plan is to have a staging and production version of the website. staging.osdg.iiit.ac.in for staging and osdg.iiit.ac.in as production.

The idea is to have staging.osdg.iiit.ac.in always reflect the master/HEAD, whereas the production or release version can be pinned to a particular revision or tag.

The neat way of doing this would be to have a post commit hooks that trigger either a pull on the website server or a push from github to the website server (which will also have to be a git server for this way of doing things) so that is has the latest version of the website at all times.

This setup will be near identical for the production version, with the only difference of an added 'tag' check.

This is a fairly good starting point -- http://bugfixer.endel.me/2013/08/04/simple-atomic-deployment-with-git/

Current issues I see are:

Weird race conditions when updating the repo and serving content via HTTP
Locking down the server so that this doesn't blow up in our face
Locking down the repo in terms of who has commit rights.

Logistical issues:

Getting a staging.osdg.iiit.ac.in
Figuring out what ports we need for both scenarios, especially for ingress into the production server, then getting access to them.

ffledgling commented 9 years ago

CC: @amoghbl1 Using this to keep track of both the dev and logistic side of things, cc'ing so you can keep an eye/update if you mess around with it as well.

amoghbl1 commented 9 years ago

Will look into the logistics part right now and update you after that. We can't setup the automatic deployment stuff before that!

ffledgling commented 9 years ago

Fair enough, keep me in the loop.

amoghbl1 commented 9 years ago

Looks like the stuff with pulling git repos was just a problem with the proxy settings, looking into those now! Think we should just use http://osdg.iiit.ac.in/staging

OSDG-IIITH / www

Setup Continous Deployment for the website #15