nchase/memetica

persist files in intermediary state

Closed this issue · 4 comments

persist files in intermediary state

Guessing that I meant this as something like "we should burn files out somewhere, somehow, because eventually this won't be on heroku."

we should burn out files in a postinstall task. postinstall can just run the publish script.

we can be sure to only run it where NODE_ENV=production.

previous comment would have been a great solution if we had pandoc in the deployed-to environment.

implemented in b961544 and then hastily followed-up by something that will work where we don't have pandoc: just make a separate branch where the generated files are in version control and use that as the branch to push to the deploy environment.

considering this done.