Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Documentation Changes #89

Merged
merged 1 commit into from Apr 23, 2012

Conversation

Projects
None yet
2 participants
Contributor

dellis23 commented Feb 27, 2012

I've added a number of extra instructions to help the newbie get past some of the issues I had when setting up django-facebook. Some of the issues may be obvious to the non-layman, but I think they are obscure enough that they will help the average user.

This is my first pull request, so let me know if I've done something egregiously wrong or silly.

@dellis23 dellis23 Numerous updates to documentation based on issues I had setting up, a…
…s well as issues found in issues area of github.
8df579f

Do you think I should drop the dependency on django_registration or django_userena.
The process of setting those up seems to cause a lot of confusion.
What do you think?

Contributor

dellis23 commented Mar 12, 2012

I'm not sure. I personally was using Django Registration before doing this, so I didn't mind the integration. I suppose cleaving it off and providing a very simple, very clean interface for connecting django-facebook to django registration (or anything else, for that matter), could be a step in a positive direction.

If you'd like to do this, I can try to help you out. Let me know how you'd like to tackle it.

@tschellenbach tschellenbach added a commit that referenced this pull request Apr 23, 2012

@tschellenbach tschellenbach Merge pull request #89 from dellis23/master
Documentation Changes
cd8e75c

@tschellenbach tschellenbach merged commit cd8e75c into tschellenbach:master Apr 23, 2012

Owner

tschellenbach commented Apr 23, 2012

Thanks for the contribution,

sorry for the slow merge.
We were a bit occupied with scaling Fashiolista.com

Cheers,
Thierry

Contributor

dellis23 commented Apr 23, 2012

Ah, no problem, I understand.

What sort of issues did you guys face when scaling? Any special
technologies? I'm working on a project right now that's going to need to
scale pretty well, and it's a challenge I haven't faced before. We ended
up going with MongoDB for the database for its schemaless design and ease
of sharding.

Good luck with Fashiolista. If you have to scale, that's good news :-)

  • Dan

On Mon, Apr 23, 2012 at 7:37 AM, Thierry Schellenbach <
reply@reply.github.com

wrote:

Thanks for the contribution,

sorry for the slow merge.
We were a bit occupied with scaling Fashiolista.com

Cheers,
Thierry


Reply to this email directly or view it on GitHub:

#89 (comment)

Owner

tschellenbach commented Apr 23, 2012

We're running Postgres, Redis and SOLR as the main data layers.
Depends on the project. We're not storing a lot of data, just have a lot of users.

What project are you working on?

Contributor

dellis23 commented Apr 23, 2012

We're doing a fantasy sports betting site.

On Mon, Apr 23, 2012 at 8:49 AM, Thierry Schellenbach <
reply@reply.github.com

wrote:

We're running Postgres, Redis and SOLR as the main data layers.
Depends on the project. We're not storing a lot of data, just have a lot
of users.

What project are you working on?


Reply to this email directly or view it on GitHub:

#89 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment