Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

travis support #57

Open
kracekumar opened this issue Mar 28, 2012 · 7 comments
Open

travis support #57

kracekumar opened this issue Mar 28, 2012 · 7 comments

Comments

@kracekumar
Copy link
Collaborator

Add travis support to brubeck, http://travis-ci.org/

@j2labs
Copy link
Owner

j2labs commented Mar 28, 2012

Neat. Would definitely like to support Travis.

Do you have any idea what the current gaps are? We have some tests, but no nose support yet, though we're not far from it either.

On Mar 28, 2012, at 1:19 AM, kracekumar [email protected] wrote:

Add travis support to brubeck, http://travis-ci.org/


Reply to this email directly or view it on GitHub:
#57

@kracekumar
Copy link
Collaborator Author

I haven't fully explored brubeck so I am providing suggestion from my limited experience.

Improvements

  1. Add readthedocs suppport to documentation.
  2. We need more users to consider brubeck is production quality framework.
  3. As a community we need to have real time examples. E.G: Web Based IRC client, Real Time Stock updates with REST API for mobile(if backboning is complete).
  4. All show case application should be live and running.
  5. Some real life example like how to host brubeck in webfaction, heroku, aws.
  6. Code snippets like how to connect couch DB, use celery and others important production quality to integrate with brubeck,
  7. we need to find out what are most frequently used third partly packages (celery, sentry, zeromq) and examples.
  8. How Django & Brubeck can co-exists, this is possible because Django can run on mongrel2 with wsigd.
    9, We should make sure brubeck is production quality web framework with constant release and improvements.
  9. Often write blog post about brubeck and other python new discovery and get traffic via hackerne.ws, reddit etc...
  10. Posting in hackerne.ws and reddit gives us valuable information about what other frameworks opnion on brubeck.
  11. Follow lean startup methodoly, build -> measure -> learn, follow the cycle.
  12. Release new feature and see the response.

Since I haven't explored completely brubeck, i just asked myself, If I am creator or co-author of a web framework, how will I make it better for pythonista?

@kracekumar
Copy link
Collaborator Author

did i misunderstand yur question ?

@j2labs
Copy link
Owner

j2labs commented Apr 3, 2012

I think this list is excellent, Krace.

Writing more inline.

On Mar 28, 2012, at 10:45 AM, kracekumar [email protected] wrote:

I haven't fully explored brubeck so I am providing suggestion from my limited experience.

Improvements

  1. Add readthedocs suppport to documentation.

This would be great.

  1. We need more users to consider brubeck is production quality framework.

Agreed. What gaps do you see that make this hard?

  1. As a community we need to have real time examples. E.G: Web Based IRC client, Real Time Stock updates with REST API for mobile(if backboning is complete).

Backboning is indeed complete and in master. Check out http://github.com/j2labs/todos

I agree about having more examples. I have been collecting demos, but I think it might be time to get more comprehensive examples together.

I also have: https://github.com/j2labs/readify & https://github.com/j2labs/buckly

Jordan Orelli and Seth Murphy built a chat system, backed by Redis: https://github.com/jordanorelli/chatify

Seth also built oauth clients for Brubeck, but I can't recall the URL. (typing this on the subway)

  1. All show case application should be live and running.

I'd be happy to host stuff on brubeck.io.

  1. Some real life example like how to host brubeck in webfaction, heroku, aws.

Agreed! Quickness is going to be helpful here.

  1. Code snippets like how to connect couch DB, use celery and others important production quality to integrate with brubeck,

Also agreed.

I would like to use the QuerySet interface for anything involving a database.

What type of environments do you typically see? Perhaps we could mock some of those in hopes of getting a prototype together that's close to behaving how people need it.

  1. we need to find out what are most frequently used third partly packages (celery, sentry, zeromq) and examples.
  2. How Django & Brubeck can co-exists, this is possible because Django can run on mongrel2 with wsigd.

Showing them both behind Mongrel2 would be awesome. Do you have any experience running Django behind Mongrel2.

I suspect the config would look almost the same as having nginx as an up streaming proxy, too.

This would be a cool environment to build in Quickness too. Let people experiment quickly.

9, We should make sure brubeck is production quality web framework with constant release and improvements.

I agree!

  1. Often write blog post about brubeck and other python new discovery and get traffic via hackerne.ws, reddit etc...

I have tried to do this on my blog, but I think we could share a blog and provide better info to our users.

  1. Posting in hackerne.ws and reddit gives us valuable information about what other frameworks opnion on brubeck.
  2. Follow lean startup methodoly, build -> measure -> learn, follow the cycle.
  3. Release new feature and see the response.

Agreed! I think we should be experimental before we get to 1.0 and nail down some clean ideas.

Specifically, I think Brubeck should be able to do most of the redundant stuff in building web services. Long polling, templates, rest apis, auth, oauth, nonblocking I/O, etc.

Ideally, it would offer a lot of the same experience as Django, but with different, leaner nuts and bolts.

Since I haven't explored completely brubeck, i just asked myself, If I am creator or co-author of a web framework, how will I make it better for pythonist

My advice would be to never just learn how something works. Always ask why it was designed a certain way. That will inform your creative efforts.

From there, you just need to build the best ideas you know of every time you build something.

Lots of smart folks will tell you how to be better. Listen to them. Especially if they're well-read.

@j2labs
Copy link
Owner

j2labs commented Apr 4, 2012

Here is a link to @sethmurphy's oauth-client: https://github.com/sethmurphy/BrubeckOAuth

Seth's gh also includes a MySQL queryset using pymysql and a Brubeck file uploader.

This cracks me up too: https://github.com/sethmurphy/BrubeckUploader/blob/master/brubeckuploader/handlers.py#L25 - This will go in core very soon! I'm updating the demo projects first though. Just updated buckly!

@kracekumar
Copy link
Collaborator Author

  1. We need more users to consider brubeck is production quality framework.
    Agreed. What gaps do you see that make this hard?

I feel having real public facing site should boost this.

  1. Code snippets like how to connect couch DB, use celery and others important production quality to integrate with brubeck,
    Also agreed. I would like to use the QuerySet interface for anything involving a database. What type of environments do you typically see? Perhaps we could mock some of those in hopes of getting a prototype together that's close to behaving how people need it.

If we can show examples how to single Query set to connect to MySQL, Postgres, Oracle, Redis, Mongo, Cassanda, Couch should be fine. We might have section like code snippets where people can submit the snippet and review can be done accordingly.

  1. we need to find out what are most frequently used third partly packages (celery, sentry, zeromq) and examples.
  2. How Django & Brubeck can co-exists, this is possible because Django can run on mongrel2 with wsigd.
    Showing them both behind Mongrel2 would be awesome. Do you have any experience running Django behind Mongrel2. I suspect the config would look almost the same as having nginx as an up streaming proxy, too. This would be a cool environment to build in Quickness too. Let people experiment quickly.

I don't experience with Django probably I can try Flask this weekend.

My advice would be to never just learn how something works. Always ask why it was designed a certain way. That will inform your creative efforts. From there, you just need to build the best ideas you know of every time you build something. Lots of smart folks will tell you how to be better. Listen to them. Especially if they're well-read.

Yes, learn from smart people :)

@kracekumar
Copy link
Collaborator Author

Now travis supports nosetests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants