Skip to content
This repository has been archived by the owner on Feb 8, 2019. It is now read-only.

Use Django for backend #66

Closed
starcalibre opened this issue Jun 26, 2015 · 2 comments
Closed

Use Django for backend #66

starcalibre opened this issue Jun 26, 2015 · 2 comments

Comments

@starcalibre
Copy link
Member

The more I think about, the more sense this makes to me. On top of the advantage of having access to the scipy stack in the backend, it'll be much easier for users to run the UI locally. All they'll need is Python, which should be installed on pretty much any bioinformaticians/biologists machine. You can't say the same for Node.js, which is still a JS hipster's thing (but an exciting one none the less IMO) :P

Coupled with an embedded database, everything would be able to run without any dependencies beyond Python! WHOAH! :D

Our backend isn't overly complicated, just a bunch of GET requests that query Mongo so it shouldn't be overly difficult. I'll just need to learn Django, which I'm happy to do because I'd like to add it to my skillset.

@jni
Copy link
Contributor

jni commented Jun 29, 2015

I obviously love this idea, and am annoyed at myself that I didn't push more for it at the start. =) Plus, I can totally dictate style discussions now, rather than argue about the JS way of doing things and how much I dislike it. =P

This might seem like a slightly lower priority for the time being, though. What do you think?

It also looks like the Bokeh guys have made a lot of progress since last year, and might have the right tools for us now.

@starcalibre
Copy link
Member Author

Actioned in #73 except we chose Flask. Django was a little heavyweight for our requirements.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants