4 ms·
Sounds interesting, though I wouldn't trust MongoDB with my (or anyone else's) data. The problem is that, while building the core of this is easy-ish, the end
by toastdriven 14y ago
Sounds interesting, though I wouldn't trust MongoDB with my (or anyone else's) data.
The problem is that, while building the core of this is easy-ish, the end result should be something very complete & easy to stand up. Our prototype functions (barely, mostly just due to a lack of time), but it's not polished or complete. It's not smooth, easy to use/administer & it doesn't include all the little details that go into successful software projects.
- jrussbowman 14y agoGotcha, I guess I was thinking more along the lines of open source project than actual product. Based on the replies above I see where you're going now. Good luck. Not sure if you're coming back to read this, but I'm curious about why django? Did you choose it because of your comfort level with it or are there advantages django offers for this kind of app? I built a few things with django a while back before I moved on to tornado for everything. Not because django was bad, tornado was just a better fit for what I've been building.
- toastdriven 14y agoPartially due to familiarity, partially due to other projects. Django will be handling the standard webapp things (registration, serving archives, etc). To be clear, there will be a lot of plain Python code handling the other aspects, with a goal being that you could relatively easily replace the Django parts with your favorite tech stack (say Flask or Tornado). Smaller parts making a greater whole.