On my Django site I would like users to communicate with each other in several ways:
Forum
Private messages
Chat with rooms and saved history
Could you suggest me ready solutions for this? Especially for chat.
Also, is it possible to integrate Google Wave in Django?
Sounds like Pinax would be a great fit for you. It has most of what you've listed already bundled.
here's a django based Ajax Chat:
http://pythonhaven.wordpress.com/2009/04/26/django-powered-ajax-chat-part-1/
Related
Are there any plug and play blog APPS for django,if so please point me to the sources for it.
I am actually looking something like word press which is of cousre difficult to integrate with django.
Thanks..
We looked into this a few months ago for our site and found that Mezzanine and Zinnia were the two best options available, and both are regularly-maintained.
Mezzanine gives you a slicker interface than Zinnia and has disqus comment integration, and has recently added Akismet integration for spam filtering on comments.
django-blog-it - complete customization and ready to use with one click installer. You can try it by hosting on your own or deploy to Heroku with a button click.
Features:
Dynamic blog articles
Blog pages
Contact us page (configurable)
google analytics
List item
SEO compliant
Actually I'm not sure but I think you might look at this one.
Also project Pinax contains blog.
I am trying to create a portal.
The portal should allow multiple user logins. The users are customers and upon login they should be able to check their sales, repository and stuff like that. Users won't need to be post blog, or anything like that, just simple checking of their daily sales.
As the admin, i, of course, should be able to edit all accounts.
I am contemplating to use a CMS such as Drupal, unless there is no such solutions, maybe a framework such as RoR would work too.
My question is, which open source CMS/framework should I use?
I would recommend you try Drupal because you can create your sales and repository info as "content". If it's suitable it would be much more productive and less error-prone than coding up something from scratch.
A common misconception of Drupal is that it is only suited for editorial written content like blog posts or articles. By using CCK and views you can quickly set up some CRUD functionality and more.
Here's a nice intro to CCK.
That sounds like pretty standard requirements for a extranet site, django or RoR seem a obvious choice. CMS's like Drupal, django-cms, Plone etc. are more concerned with content such as texts.
Choose your tool according to your current skills. I myself prefer django, but RoR will be better if you already know ruby.
CMS won't suit you because they are basically designed for managing content. Your requirements seem to far simple from that. If you are familiar with python, you can do such a site in 20 mins using Django.
I have no experience with Ruby of RoR!
I am currently working an a webapp, using mongoengine and django, which will require users to create an account from a registration page. I know MongoEngine has an authentication backend, but does it also include a registration form, etc..., like django itself does? If not, are there any example projects which show how to implement this? The only open-source mongoengine project I've found is django-mumblr, but I can't find the examples I want in it.
I'm not interested in alternative options, such as MongoKit or mango for handling authentication.
I am just getting started with django and mongoDB, so please excuse my lack of knowledge. Thanks in advance for the help!
Not tried it out yet, but https://github.com/lig/django-registration-me by http://twitter.com/#!/lig1 looks like it could be a good bet.
Im still fairly new to Django, so please explain things with that in
mind.
I'm trying to create three websites using 2 subdomains and 1 domain:
for the blog, blog.mysite.com
for the forums, forums.mysite.com
for the custom web app, mysite.com
When building the custom web app, I used contrib.auth to make use of
the built-in django provided user models and functionality.
For the forums, I am planning on using SNAPboard (http://
code.google.com/p/snapboard/) with minimal, if any, modifications. On
initial inspection, it looks like it also uses contrib.auth users.
For the blog, I will probably be rolling my own lightweight blogging
app (since that seems to be the Django way and, also, b/c as Bennet
mentions, there is no killer Django Blog app)
Currently, I am considering two features that require some integration
between the three sites. First, I want to have the users of the custom
web app to use the same account to also log into the forums. Second, I
also (but I haven't figured out how I'm going to do this yet) would
like my blog posts to automatically become a topic for discussion in
the forums (this is just an idea I had, I might end up dropping it).
Ok, so to my questions:
1) Again, I'm new to Django, but this integration leads me to believe
the three websites need to be all under one project. Is this correct?
2) How would I accomplish the url structure for the websites that I
described above (blog.mysite.com, etc)? In the project's urls.py, I
don't know how to filter off of subdomains. If it was mysite.com/
forums/, that would be easy, but I don't know how to to catch
forums.mysite.com and forward it to the appropriate Django app.
3) Would I have to make use of the django.contrib.sites framework? I
don't understand that framework fully, but it seems like it's used
when two different websites are using the same django app in the
background. Whereas my three websites are all using different django
apps, but I want them to share a little bit of data.
Thanks for your help.
1) Yes, it's only true way for that
2) Use middleware
3) No, you don't need it.
Is there a good way provide user configurable app settings in Django admin?
Basically I would like to have a nice forms where site owner can easily edit such one off information as his contact information, front page text content, etc. Sort of like a normal admin interface of a model, but limited to only one undeletable item in the model.
I think django constance is the way to go. Alive and compatible with django 1.4.
The third-party project django-dbsettings is ideal for this.
I looked at dbsettings and liked some of what I saw, but I really wanted a more centralized, organized system. So I built django-appsettings. Enjoy :)
Found this: django-livesettings