I've been developing an art show management application (in both the general and Django senses) for the past few years, and have had it up on sourceforge and github for a while. It's very close to being "complete" and I'd like to make sure its as useful as possible to as wide an audience.
However, i'd like to distribute it in a form that is useful to both parties that want a "drop in and go" installation, and others that might use it as an app in a larger Django site. However, the two seem at loggerheads: The first suggests I should have a single check out or download that includes the artshow app, the project, settings files (with instructions to modify certain parts). While the second suggests I should have a python module usable as a Django app, and include instructions on the required additions to middleware, context processors, and app-specific settings, and ensure it's installable from PyPI. Catering for the one makes it harder for the other. Does anyone have suggestions on the "better" solution, or even some combination that caters to both well? Project is currently here: http://github.com/chmarr/artshow-jockey/ Its currently in the former state, but with some "replaceable" components split out as a separate app. This was done mostly to demonstrate how to create a replaceable "Person" model, and did it in a way that shows that it's already effectively replaced. As is, the installation instructions for the django-noob are very simple, and I'd like to keep that attribute. Also, I'm considering rolling "peeps" "tinyreg" and the other "replaceable" modules back into the "artshow" module regardless... if anything to just make it look cleaner. One idea that came to mind is to have the github repository show as a "stand alone application", just as it is now, but have the PyPI package only download the "artshow" component. Anyone that wants to both use artshow in their own Django site, but use the git checkout for the module, can simply check artshow-jockey out somewhere and put that into the python path. Does that seem feasible? -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/9UP1mtJh24YJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
