opentwincities / ndia-django Goto Github PK

As discussed in #1, having the backend default to use SQLite would allow new developers to get started quickly. To balance this with the need and want to use other databases, I'm thinking of chaning the backend to do the following:

1. The default behavior is to use SQLite and store data in ndia.db
2. If there is a config.py file, use values from that to override default dabase connection values
3. If the DATABASE_URL environment variable is set, us that as the database host address. In this case, if no config.py file exists, assume the database is Postgres.

I made a new app ndia_calendar within my fork of ndia-django and I wanted to write down a few thoughts on what I want to build. Anyone can add here what they want to see added.

• A unified internal user space where events can be logged, and organizations added. The django admin is ok for now but a real working site would have a more customized and stylized user space.
  -The Category model should have a colorpicker to choose a color for each category (spectrum.js)
  -
• A slick searchable interface that will consume the api:
  My thoughts are that we should put effort into using time data as well as geographical data. We could even include bus line data so a person could search for "computer lab" events at 8am on Fridays after 10/10/2015 near the 6 line. This page should be part calendar part map.
• The api should use the django-rest-framework as it is more fully featured.
• A commenting system where users log in via a Social app (python-oath-social)

More to come

We're pretty early in the development process and we don't really have specs. But, it's never too early to test. At the very least, we can test that we're getting expected content types and HTTP statuses for on success and errors.

Gathering information on API queries and responses will be vauable for a number of reasons, including providing us as developers with information about how end users are interacting with this data, and providing information about the types and locations of services that residents are looking for that can be relayed to government and organization decision makers.

I feel like this is still ticket is still in discovery - I'm not really sure what kind of analytics we're interested in, not do I have solid thoughts on how to implement. So, let's talk about that first.

Trying to get up and running locally but I'm experiencing a couple snags. I don't have any prior experience with django.

python manage.py runserver

=> python: can't open file 'manage.py': [Errno 2] No such file or directory

ok so I try:

python ndiaDjango/manage.py runserver

=> ...
ImportError: Could not import settings 'ndiaDjango.settings' (Is it on sys.path? Is there an import error in the settings file?): No module named config

Maybe an example ndiaDjango.settings file would help?

It was mentioned at the NDIA Hackday that people were thinking about having a way to get data into the system without entering the data into a form. I have thought about the basics of how that could happen. We could use Scrapy (we would have to use Python 2.7) which has scheduling to collect data on events from the public library or other sites. This would be stored in a database table for unconfirmed events. The way it would be entered into the regular event database table would be if it is selected by a person who looks at it and confirms it. This would make it easier on the people who are entering events so 100 or 200 or 1000 events a month don't have to be entered into the database manually.

Basically do this: https://devcenter.heroku.com/articles/getting-started-with-django