This adds what I mentioned in #8 of splitting showcase.js to have an internal version (ie one that allows post requests) and an external one. I also fetch showcase.js every time we run now (similar to index.html) as it seems to have the most changes we make. As this could break if they break their setup I back it up first. Another option to avoid ever overriding existing content would be an --update-main-scripts flag users could use (we would want to keep index.html the same then too if not used).
This would also allow for more divergence between internal showcase.js and external if we need it.
This adds what I mentioned in #8 of splitting showcase.js to have an internal version (ie one that allows post requests) and an external one. I also fetch showcase.js every time we run now (similar to index.html) as it seems to have the most changes we make. As this could break if they break their setup I back it up first. Another option to avoid ever overriding existing content would be an --update-main-scripts flag users could use (we would want to keep index.html the same then too if not used).
This would also allow for more divergence between internal showcase.js and external if we need it.