include git revision/tag in template app about oghliner

[brendandahl]

Was this based on the old flow of cloning the repo?

It seems we should just take the npm version of oghliner and put that into the index.html file during oghliner bootstrap.

[mykmelez]

Was this based on the old flow of cloning the repo?

This is actually to determine the deployed version of an app based on the template, not to determine the version of the template that was used to create the app.

@wfwalker asked for this when he was debugging an app update whose differences from the previous version of the app were subtle. He wanted to ensure that the app his browser was loading was the new version rather than the old one.

Since the "version" in this case is just the particular Git revision that he deployed, writing the revision ID into the index.html file before deploying it would enable him to figure out what version of the app he's looking at by checking that value in the HTML file.

(Including the version of Oghliner that was used to bootstrap the app would also be useful, as would a reference and link to Oghliner.)

[brendandahl]

@mykmelez Do we still want to do this after @wfwalker's comment of "I think I mostly want to have programmatic knowledge of whether this instance of the app is up to date"?

I think the current issue description could still be a nice feature, but it does make us bring in templating to the template app build step.

[mykmelez]

I think the current issue description could still be a nice feature, but it does make us bring in templating to the template app build step.

Hmm, indeed. I agree, it'd be a nice feature to have (even if it isn't the feature that @wfwalker actually wants!). And I'm ok with adding templating to the template app build step (even though it reminds me of Inception!). But it doesn't need to happen for v1.