Publish visualizer on-line

[aymanhab]

Would be great to test bug fixes to standalone visualizer if we can push the code on the repo to a live server (e.g. heroku) to streamline the process.

[jenhicks]

Sounds great. Let me know if we need a paid heroku account.

[chrisdembia]

@aymanhab I have the account info for heroku.

[aymanhab]

Thanks @chrisdembia, is that what you use to public doxygen? I guess the trick is to not include our account credentials in public files. What was your strategy?

[chrisdembia]

Oh I see what you mean now... you want a git push to update a web server, using travis or appveyor? Just like we have for myosin.sourceforge.net?

sourceforge.net might only handle static sites, so we may need to use heroku.

Here are instructions on how to integrate heroku and traivs: https://docs.travis-ci.com/user/deployment/heroku/.

The account credentials are stored in encrypted form in .travis.yml.

The doxygen for 3.3 is hosted on simtk.