closed livingstoneonline/livingstoneonline#90

Add LEAP-XSLT to deployment form

nigelgbanks

Alter: https://github.com/livingstoneonline/LEAP-XSLT

To have three branches (dev,stage,prod) and add it's deployment to the deployment form in the admin section of the site.

nigelgbanks

Should be sorted now, branches added and deployment setup.

awisnicki

Great thank you. Does this mean that the way I tried to update them yesterday on the site by using http://livingstonestage.lib.umd.edu/admin/config/development/livingstone (which didn't work, ) will now work?

nigelgbanks

Yup

On Wed, Nov 2, 2016 at 6:30 PM, awisnicki notifications@github.com wrote:

Great thank you. Does this mean that the way I tried to update them yesterday on the site by using http://livingstonestage.lib. umd.edu/admin/config/development/livingstone (which didn't work, ) will now work?

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/livingstoneonline/livingstoneonline/issues/90#issuecomment-257957392, or mute the thread https://github.com/notifications/unsubscribe-auth/AAdvzWfOXGNBSPPw-AVZEzVjb8x-L8qDks5q6NbJgaJpZM4Kmm-e .

##

Nigel Banks nigel.g.banks@gmail.com

awisnicki

OK, so two quick question as there are now six branchs to this repo. First, it looks like gh-pages are now in sync with dev/stage/prod. Is that correct? Second, henceforth we are only using dev/stage/prod, so I should ignore gh-pages. Is that correct?

nigelgbanks

We should always make gh-pages match prod, as the downloaded TEI documents themselves will point to the gh-pages branch.

nigelgbanks

gh-pages is a special branch provided by github for hosting webpages.