migration to sulab servers

[b]

When the last little bugs in this thing have been worked out we should do a couple things to ease persistence over time:

1. move the deployment to an AWS instance owned by the Su Lab
2. move the code into a repo under the sulab/ bitbucket account (or sulab github). This can simply be a fork and push from the starinformatics repo where it lives now. At this time probably rename this one knowledge.bio.py or something like that.
3. Add the files needed to build the database to the repo as downloadable archives, if allowed, or links to where they came from if not.
4. initialize a new repo in a sulab owned repo for the next phase of development.

None of this is time sensitive, but important for completion. Hope to see this by the end of September. When you are ready Richard, let me know and I will set up the necessary permissions etc.

[Richard Bruskiewich]

OK. When all of the other issues are covered, we'll attend to this one.

[Richard Bruskiewich]

Item 1) completed ... Yay!