What is the consensus on the most solid template for a "large" Flask project? I'm considering Flask for a large scale consumer app and find it a great fit, but would like to see an example of a properly organized app with multiple blueprints and routes separate from implementation. I've seen the handful of starter apps on GitHub, but what is generally recommended?
The best template is the one you took the time to read, understand and measure to your needs. There is a topic with many project template examples in flask mail-list. For the example your're asking for, there are many in github. 2012/2/1 Andy Parsons <andyparsons@gmail.com> > What is the consensus on the most solid template for a "large" Flask > project? I'm considering Flask for a large scale consumer app and find it a > great fit, but would like to see an example of a properly organized app > with multiple blueprints and routes separate from implementation. I've seen > the handful of starter apps on GitHub, but what is generally recommended? > -- "A arrogância é a arma dos fracos." =========================== Italo Moreira Campelo Maia Bacharel em Ciência da Computação - UECE Desenvolvedor WEB e Desktop (Java, Python, Lua) Coordenador do Pug-CE ----------------------------------------------------- http://www.italomaia.com/ http://twitter.com/italomaia/ http://eusouolobomau.blogspot.com/ ----------------------------------------------------- Turtle Linux 9.10 - http://tiny.cc/blogturtle910 Turtle Linux 10.10 - http://bit.ly/cEw4ET ===========================
ps: you could even take pieces from many project templates and make a starting point that pleases you. 2012/2/3 Italo Maia <italo.maia@gmail.com> > The best template is the one you took the time to read, understand and > measure to your needs. There is a topic with many project template examples > in flask mail-list. For the example your're asking for, there are many in > github. > > 2012/2/1 Andy Parsons <andyparsons@gmail.com> > >> What is the consensus on the most solid template for a "large" Flask >> project? I'm considering Flask for a large scale consumer app and find it a >> great fit, but would like to see an example of a properly organized app >> with multiple blueprints and routes separate from implementation. I've seen >> the handful of starter apps on GitHub, but what is generally recommended? >> > > > > -- > "A arrogância é a arma dos fracos." > > =========================== > Italo Moreira Campelo Maia > Bacharel em Ciência da Computação - UECE > Desenvolvedor WEB e Desktop (Java, Python, Lua) > Coordenador do Pug-CE > ----------------------------------------------------- > http://www.italomaia.com/ > http://twitter.com/italomaia/ > http://eusouolobomau.blogspot.com/ > ----------------------------------------------------- > Turtle Linux 9.10 - http://tiny.cc/blogturtle910 > Turtle Linux 10.10 - http://bit.ly/cEw4ET > =========================== > -- "A arrogância é a arma dos fracos." =========================== Italo Moreira Campelo Maia Bacharel em Ciência da Computação - UECE Desenvolvedor WEB e Desktop (Java, Python, Lua) Coordenador do Pug-CE ----------------------------------------------------- http://www.italomaia.com/ http://twitter.com/italomaia/ http://eusouolobomau.blogspot.com/ ----------------------------------------------------- Turtle Linux 9.10 - http://tiny.cc/blogturtle910 Turtle Linux 10.10 - http://bit.ly/cEw4ET ===========================
However having something official reduces the barrier of entry to large applications with Flask. Variation is good, but for newcomers it's an instance of the paradox of choice<http://en.wikipedia.org/wiki/The_Paradox_of_Choice:_Why_More_Is_Less> . Instead, when you have something official to begin with and test the waters with, you get a feel for how it works and can better predict how to use it for your needs. Not everyone wants to just read through code without seeing the end result. And there are superior ways building a large app. Exploring what's common and providing a starting point for people can save them days of research. I also argue it's helpful for those who have been around longer. Instead of wondering GitHub and stopping short when finding a solution that *almost *fits our needs for a large project, having good practices in one place can help tremendously. On Fri, Feb 3, 2012 at 12:56 PM, Italo Maia <italo.maia@gmail.com> wrote: > ps: you could even take pieces from many project templates and make a > starting point that pleases you. > > > 2012/2/3 Italo Maia <italo.maia@gmail.com> > >> The best template is the one you took the time to read, understand and >> measure to your needs. There is a topic with many project template examples >> in flask mail-list. For the example your're asking for, there are many in >> github. >> >> 2012/2/1 Andy Parsons <andyparsons@gmail.com> >> >>> What is the consensus on the most solid template for a "large" Flask >>> project? I'm considering Flask for a large scale consumer app and find it a >>> great fit, but would like to see an example of a properly organized app >>> with multiple blueprints and routes separate from implementation. I've seen >>> the handful of starter apps on GitHub, but what is generally recommended? >>> >> >> >> >> -- >> "A arrogância é a arma dos fracos." >> >> =========================== >> Italo Moreira Campelo Maia >> Bacharel em Ciência da Computação - UECE >> Desenvolvedor WEB e Desktop (Java, Python, Lua) >> Coordenador do Pug-CE >> ----------------------------------------------------- >> http://www.italomaia.com/ >> http://twitter.com/italomaia/ >> http://eusouolobomau.blogspot.com/ >> ----------------------------------------------------- >> Turtle Linux 9.10 - http://tiny.cc/blogturtle910 >> Turtle Linux 10.10 - http://bit.ly/cEw4ET >> =========================== >> > > > > -- > "A arrogância é a arma dos fracos." > > =========================== > Italo Moreira Campelo Maia > Bacharel em Ciência da Computação - UECE > Desenvolvedor WEB e Desktop (Java, Python, Lua) > Coordenador do Pug-CE > ----------------------------------------------------- > http://www.italomaia.com/ > http://twitter.com/italomaia/ > http://eusouolobomau.blogspot.com/ > ----------------------------------------------------- > Turtle Linux 9.10 - http://tiny.cc/blogturtle910 > Turtle Linux 10.10 - http://bit.ly/cEw4ET > =========================== >
I agree with Joe. While no one here want to see Flask turn into Django or Rails by any means, more recipes and project structure techniques can only help adoption. That's god for veterans and newcomers. On Friday, February 3, 2012 at 1:24 PM, Joe Esposito wrote: > However having something official reduces the barrier of entry to large applications with Flask. Variation is good, but for newcomers it's an instance of the paradox of choice (http://en.wikipedia.org/wiki/The_Paradox_of_Choice:_Why_More_Is_Less). > > Instead, when you have something official to begin with and test the waters with, you get a feel for how it works and can better predict how to use it for your needs. Not everyone wants to just read through code without seeing the end result. And there are superior ways building a large app. Exploring what's common and providing a starting point for people can save them days of research. > > I also argue it's helpful for those who have been around longer. Instead of wondering GitHub and stopping short when finding a solution that almost fits our needs for a large project, having good practices in one place can help tremendously. > > On Fri, Feb 3, 2012 at 12:56 PM, Italo Maia <italo.maia@gmail.com (mailto:italo.maia@gmail.com)> wrote: > > ps: you could even take pieces from many project templates and make a starting point that pleases you. > > > > > > 2012/2/3 Italo Maia <italo.maia@gmail.com (mailto:italo.maia@gmail.com)> > > > The best template is the one you took the time to read, understand and measure to your needs. There is a topic with many project template examples in flask mail-list. For the example your're asking for, there are many in github. > > > > > > 2012/2/1 Andy Parsons <andyparsons@gmail.com (mailto:andyparsons@gmail.com)> > > > > What is the consensus on the most solid template for a "large" Flask project? I'm considering Flask for a large scale consumer app and find it a great fit, but would like to see an example of a properly organized app with multiple blueprints and routes separate from implementation. I've seen the handful of starter apps on GitHub, but what is generally recommended? > > > > > > > > > -- > > > "A arrogância é a arma dos fracos." > > > > > > =========================== > > > Italo Moreira Campelo Maia > > > Bacharel em Ciência da Computação - UECE > > > Desenvolvedor WEB e Desktop (Java, Python, Lua) > > > Coordenador do Pug-CE > > > ----------------------------------------------------- > > > http://www.italomaia.com/ > > > http://twitter.com/italomaia/ > > > http://eusouolobomau.blogspot.com/ > > > ----------------------------------------------------- > > > Turtle Linux 9.10 - http://tiny.cc/blogturtle910 > > > Turtle Linux 10.10 - http://bit.ly/cEw4ET > > > =========================== > > > > > > > > -- > > "A arrogância é a arma dos fracos." > > > > =========================== > > Italo Moreira Campelo Maia > > Bacharel em Ciência da Computação - UECE > > Desenvolvedor WEB e Desktop (Java, Python, Lua) > > Coordenador do Pug-CE > > ----------------------------------------------------- > > http://www.italomaia.com/ > > http://twitter.com/italomaia/ > > http://eusouolobomau.blogspot.com/ > > ----------------------------------------------------- > > Turtle Linux 9.10 - http://tiny.cc/blogturtle910 > > Turtle Linux 10.10 - http://bit.ly/cEw4ET > > =========================== >
hi all, I am a newcomer and with no problems I can admit that I parked flask because the too many examples of a large project have confused my ideas. All this examples are personal interpretation of a large flask project. i know that the best way for learn is make my personal interpretation but i need the boilerplate for understand the basic concepts before go ahead. in another context, i learned a lot from this simple file<http://code.google.com/p/google-app-engine-samples/source/browse/trunk/tasks/tasks.py>. Why not in Flask? I hope not to hurt anyone, but it is just my experience Thanks to all for discussion. ps repo or wiki? repo and wiki. Ciao, -- Gianni
Hey folks! As a beginner to python web development who was encouraged to use Flask I can deifnitely say its not easy to start with. Sure the documentation is good and stuff, but for someone who wants to build a mid sized app and dive in, its really hard to find good guidelines and best practices on how to build and deploy a simple yet realistic app (that uses some libraries like WTF, SQLA etc) using Flask. Of course you can find stuff on GitHub but staring at and messing with code on github is totally different from actually having a cookbook like approach where the code is "explained" and you see why someone has done x instead of y (may not be the best way, but atleast it is SOME way!). Just my 2pence! Cheers, MK ------------------------------------------------- Mitul K. Jain On Fri, Feb 3, 2012 at 4:26 PM, Gianni <giannidn@gmail.com> wrote: > hi all, > I am a newcomer and with no problems I can admit that I parked flask > because the too many examples of a large project have confused my ideas. > All this examples are personal interpretation of a large flask project. i > know that the best way for learn is make my personal interpretation but i > need the boilerplate for understand the basic concepts before go ahead. > in another context, i learned a lot from this simple file<http://code.google.com/p/google-app-engine-samples/source/browse/trunk/tasks/tasks.py>. > Why not in Flask? > I hope not to hurt anyone, but it is just my experience > Thanks to all for discussion. > > ps repo or wiki? repo and wiki. > > Ciao, > -- Gianni >
Hello guys, I've been working on the wiki page at https://github.com/mitsuhiko/flask/wiki/Large-app-how-to . It's *very raw first version *(I have a very busy schedule) and it for sure need better pagination/organization, corrections, more descriptions and explanations etc... I don't have much time but will try to spend couple of hours this week on it to improve it. My main request is that, it's wiki, so please edit, update, add and fix what need to be fixed. As there is just one page, I'm worried about concurrent editing, so maybe having every section in different wiki pages could prevent this issue. I'll get back to it later today. PS: Adding one line on a wiki might seems like a too little contribution but it isn't :) Brice 2012/2/3 Mitul K. Jain <mituljain@gmail.com> > Hey folks! > > As a beginner to python web development who was encouraged to use Flask I > can deifnitely say its not easy to start with. Sure the documentation is > good and stuff, but for someone who wants to build a mid sized app and dive > in, its really hard to find good guidelines and best practices on how to > build and deploy a simple yet realistic app (that uses some libraries like > WTF, SQLA etc) using Flask. Of course you can find stuff on GitHub but > staring at and messing with code on github is totally different from > actually having a cookbook like approach where the code is "explained" and > you see why someone has done x instead of y (may not be the best way, but > atleast it is SOME way!). > > Just my 2pence! > > Cheers, > MK > > ------------------------------------------------- > Mitul K. Jain > > > > > On Fri, Feb 3, 2012 at 4:26 PM, Gianni <giannidn@gmail.com> wrote: > >> hi all, >> I am a newcomer and with no problems I can admit that I parked flask >> because the too many examples of a large project have confused my ideas. >> All this examples are personal interpretation of a large flask project. i >> know that the best way for learn is make my personal interpretation but i >> need the boilerplate for understand the basic concepts before go ahead. >> in another context, i learned a lot from this simple file<http://code.google.com/p/google-app-engine-samples/source/browse/trunk/tasks/tasks.py>. >> Why not in Flask? >> I hope not to hurt anyone, but it is just my experience >> Thanks to all for discussion. >> >> ps repo or wiki? repo and wiki. >> >> Ciao, >> -- Gianni >> > >
thank you Brice. -- Gianni
Thanks Brice! ------------------------------------------------- Mitul K. Jain On Sat, Feb 4, 2012 at 5:14 PM, Gianni <giannidn@gmail.com> wrote: > thank you Brice. > > -- Gianni >
I don't think people are looking for a one-sized-fits all template, I think that's why people are pushing for a wiki/discussion based approach. There are plenty of templates on git, but I personally (and my sense is others from the list), are really looking for some examples and best practices for building larger apps – effectively more guidance on why design decisions are made, so we can incorporate that learning as we start new projects. This is something current templates lack (you can't even really learn it just by looking at a skeleton), and the current official documentation doesn't really cover. On Fri, Feb 3, 2012 at 9:56 AM, Italo Maia <italo.maia@gmail.com> wrote: > ps: you could even take pieces from many project templates and make a > starting point that pleases you. > > > 2012/2/3 Italo Maia <italo.maia@gmail.com> > >> The best template is the one you took the time to read, understand and >> measure to your needs. There is a topic with many project template examples >> in flask mail-list. For the example your're asking for, there are many in >> github. >> >> 2012/2/1 Andy Parsons <andyparsons@gmail.com> >> >>> What is the consensus on the most solid template for a "large" Flask >>> project? I'm considering Flask for a large scale consumer app and find it a >>> great fit, but would like to see an example of a properly organized app >>> with multiple blueprints and routes separate from implementation. I've seen >>> the handful of starter apps on GitHub, but what is generally recommended? >>> >> >> >> >> -- >> "A arrogância é a arma dos fracos." >> >> =========================== >> Italo Moreira Campelo Maia >> Bacharel em Ciência da Computação - UECE >> Desenvolvedor WEB e Desktop (Java, Python, Lua) >> Coordenador do Pug-CE >> ----------------------------------------------------- >> http://www.italomaia.com/ >> http://twitter.com/italomaia/ >> http://eusouolobomau.blogspot.com/ >> ----------------------------------------------------- >> Turtle Linux 9.10 - http://tiny.cc/blogturtle910 >> Turtle Linux 10.10 - http://bit.ly/cEw4ET >> =========================== >> > > > > -- > "A arrogância é a arma dos fracos." > > =========================== > Italo Moreira Campelo Maia > Bacharel em Ciência da Computação - UECE > Desenvolvedor WEB e Desktop (Java, Python, Lua) > Coordenador do Pug-CE > ----------------------------------------------------- > http://www.italomaia.com/ > http://twitter.com/italomaia/ > http://eusouolobomau.blogspot.com/ > ----------------------------------------------------- > Turtle Linux 9.10 - http://tiny.cc/blogturtle910 > Turtle Linux 10.10 - http://bit.ly/cEw4ET > =========================== >
I might be wrong, but I think dev's want to know how and why you architect large project a certain way. Repository are without clear explanation and unless the code is beautiful and self explanatory, it's not the easiest way to learn. Later on, when you need to find solution to specific problem (search, ranking, mailing...) you can pick small pieces of code from snippets. 2012/2/3 Italo Maia <italo.maia@gmail.com> > ps: you could even take pieces from many project templates and make a > starting point that pleases you. > > > 2012/2/3 Italo Maia <italo.maia@gmail.com> > >> The best template is the one you took the time to read, understand and >> measure to your needs. There is a topic with many project template examples >> in flask mail-list. For the example your're asking for, there are many in >> github. >> >> 2012/2/1 Andy Parsons <andyparsons@gmail.com> >> >>> What is the consensus on the most solid template for a "large" Flask >>> project? I'm considering Flask for a large scale consumer app and find it a >>> great fit, but would like to see an example of a properly organized app >>> with multiple blueprints and routes separate from implementation. I've seen >>> the handful of starter apps on GitHub, but what is generally recommended? >>> >> >> >> >> -- >> "A arrogância é a arma dos fracos." >> >> =========================== >> Italo Moreira Campelo Maia >> Bacharel em Ciência da Computação - UECE >> Desenvolvedor WEB e Desktop (Java, Python, Lua) >> Coordenador do Pug-CE >> ----------------------------------------------------- >> http://www.italomaia.com/ >> http://twitter.com/italomaia/ >> http://eusouolobomau.blogspot.com/ >> ----------------------------------------------------- >> Turtle Linux 9.10 - http://tiny.cc/blogturtle910 >> Turtle Linux 10.10 - http://bit.ly/cEw4ET >> =========================== >> > > > > -- > "A arrogância é a arma dos fracos." > > =========================== > Italo Moreira Campelo Maia > Bacharel em Ciência da Computação - UECE > Desenvolvedor WEB e Desktop (Java, Python, Lua) > Coordenador do Pug-CE > ----------------------------------------------------- > http://www.italomaia.com/ > http://twitter.com/italomaia/ > http://eusouolobomau.blogspot.com/ > ----------------------------------------------------- > Turtle Linux 9.10 - http://tiny.cc/blogturtle910 > Turtle Linux 10.10 - http://bit.ly/cEw4ET > =========================== > -- blog: http://www.debrice.com Time tracking tool: http://alpha.kaaloo.com Django site generator: http://alpha.djangogenerator.com linkedin: http://www.linkedin.com/in/bricepleroy
+1 ------------------------------------------------- Mitul K. Jain On Wed, Feb 1, 2012 at 6:40 PM, Andy Parsons <andyparsons@gmail.com> wrote: > What is the consensus on the most solid template for a "large" Flask > project? I'm considering Flask for a large scale consumer app and find it a > great fit, but would like to see an example of a properly organized app > with multiple blueprints and routes separate from implementation. I've seen > the handful of starter apps on GitHub, but what is generally recommended? >
+1 - I know this discussion has been raised before - but it would be good for Flask to come with some basic app template generator(s). On Wed, Feb 1, 2012 at 9:55 PM, Mitul K. Jain <mituljain@gmail.com> wrote: > +1 > ------------------------------------------------- > Mitul K. Jain > > > > > On Wed, Feb 1, 2012 at 6:40 PM, Andy Parsons <andyparsons@gmail.com> wrote: >> >> What is the consensus on the most solid template for a "large" Flask >> project? I'm considering Flask for a large scale consumer app and find it a >> great fit, but would like to see an example of a properly organized app with >> multiple blueprints and routes separate from implementation. I've seen the >> handful of starter apps on GitHub, but what is generally recommended? > > -- Ben Hughes Change & Innovation Lead Bright Approach Ltd. Tel: +447427600266 Twitter: @bwghughes http://about.me/bwghughes
Could we go with a wiki page for that instead of a repository maybe? Brice Leroy Sent from my iPhone On Feb 1, 2012, at 10:37 PM, Ben Hughes <bwghughes@gmail.com> wrote: > +1 - I know this discussion has been raised before - but it would be > good for Flask to come with some basic app template generator(s). > > > > On Wed, Feb 1, 2012 at 9:55 PM, Mitul K. Jain <mituljain@gmail.com> wrote: >> +1 >> ------------------------------------------------- >> Mitul K. Jain >> >> >> >> >> On Wed, Feb 1, 2012 at 6:40 PM, Andy Parsons <andyparsons@gmail.com> wrote: >>> >>> What is the consensus on the most solid template for a "large" Flask >>> project? I'm considering Flask for a large scale consumer app and find it a >>> great fit, but would like to see an example of a properly organized app with >>> multiple blueprints and routes separate from implementation. I've seen the >>> handful of starter apps on GitHub, but what is generally recommended? >> >> > > > > -- > Ben Hughes > Change & Innovation Lead > Bright Approach Ltd. > Tel: +447427600266 > Twitter: @bwghughes > http://about.me/bwghughes
+1. That would be incredibly helpful On Thursday, February 2, 2012 at 6:57 PM, Brice Leroy wrote: > Could we go with a wiki page for that instead of a repository maybe? > > Brice Leroy > Sent from my iPhone > > On Feb 1, 2012, at 10:37 PM, Ben Hughes <bwghughes@gmail.com (mailto:bwghughes@gmail.com)> wrote: > > > +1 - I know this discussion has been raised before - but it would be > > good for Flask to come with some basic app template generator(s). > > > > > > > > On Wed, Feb 1, 2012 at 9:55 PM, Mitul K. Jain <mituljain@gmail.com (mailto:mituljain@gmail.com)> wrote: > > > +1 > > > ------------------------------------------------- > > > Mitul K. Jain > > > > > > > > > > > > > > > On Wed, Feb 1, 2012 at 6:40 PM, Andy Parsons <andyparsons@gmail.com (mailto:andyparsons@gmail.com)> wrote: > > > > > > > > What is the consensus on the most solid template for a "large" Flask > > > > project? I'm considering Flask for a large scale consumer app and find it a > > > > great fit, but would like to see an example of a properly organized app with > > > > multiple blueprints and routes separate from implementation. I've seen the > > > > handful of starter apps on GitHub, but what is generally recommended? > > > > > > > > > > > > > > > > > > > > -- > > Ben Hughes > > Change & Innovation Lead > > Bright Approach Ltd. > > Tel: +447427600266 > > Twitter: @bwghughes > > http://about.me/bwghughes > > > > >
I can put the basics structure of a blueprint driven app with sqlalchemy and WTF. Only thing is... Where? Brice Leroy Sent from my iPhone On Feb 2, 2012, at 7:00 PM, Paul Gibbs <psgibbs@gmail.com> wrote: > +1. That would be incredibly helpful > On Thursday, February 2, 2012 at 6:57 PM, Brice Leroy wrote: > >> Could we go with a wiki page for that instead of a repository maybe? >> >> Brice Leroy >> Sent from my iPhone >> >> On Feb 1, 2012, at 10:37 PM, Ben Hughes <bwghughes@gmail.com> wrote: >> >>> +1 - I know this discussion has been raised before - but it would be >>> good for Flask to come with some basic app template generator(s). >>> >>> >>> >>> On Wed, Feb 1, 2012 at 9:55 PM, Mitul K. Jain <mituljain@gmail.com> wrote: >>>> +1 >>>> ------------------------------------------------- >>>> Mitul K. Jain >>>> >>>> >>>> >>>> >>>> On Wed, Feb 1, 2012 at 6:40 PM, Andy Parsons <andyparsons @gmail.com> wrote: >>>>> >>>>> What is the consensus on the most solid template for a "large" Flask >>>>> project? I'm considering Flask for a large scale consumer app and find it a >>>>> great fit, but would like to see an example of a properly organized app with >>>>> multiple blueprints and routes separate from implementation. I've seen the >>>>> handful of starter apps on GitHub, but what is generally recommended? >>> >>> >>> >>> -- >>> Ben Hughes >>> Change & Innovation Lead >>> Bright Approach Ltd. >>> Tel: +447427600266 >>> Twitter: @bwghughes >>> http://about.me/bwghughes >
Github- with a link on http://flask.pocoo.org/? Thanks On Thursday, February 2, 2012 at 10:16 PM, Brice Leroy wrote: > I can put the basics structure of a blueprint driven app with sqlalchemy and WTF. Only thing is... Where? > > Brice Leroy > Sent from my iPhone > > > On Feb 2, 2012, at 7:00 PM, Paul Gibbs <psgibbs@gmail.com (mailto:psgibbs@gmail.com)> wrote: > > > +1. That would be incredibly helpful > > > > On Thursday, February 2, 2012 at 6:57 PM, Brice Leroy wrote: > > > > > Could we go with a wiki page for that instead of a repository maybe? > > > > > > Brice Leroy > > > Sent from my iPhone > > > > > > On Feb 1, 2012, at 10:37 PM, Ben Hughes <bwghughes@gmail.com (mailto:bwghughes@gmail.com)> wrote: > > > > > > > +1 - I know this discussion has been raised before - but it would be > > > > good for Flask to come with some basic app template generator(s). > > > > > > > > > > > > > > > > On Wed, Feb 1, 2012 at 9:55 PM, Mitul K. Jain <mituljain@gmail.com (mailto:mituljain@gmail.com)> wrote: > > > > > +1 > > > > > ------------------------------------------------- > > > > > Mitul K. Jain > > > > > > > > > > > > > > > > > > > > > > > > > On Wed, Feb 1, 2012 at 6:40 PM, Andy Parsons <andyparsons @gmail.com (mailto:andyparsons@gmail.com)> wrote: > > > > > > > > > > > > What is the consensus on the most solid template for a "large" Flask > > > > > > project? I'm considering Flask for a large scale consumer app and find it a > > > > > > great fit, but would like to see an example of a properly organized app with > > > > > > multiple blueprints and routes separate from implementation. I've seen the > > > > > > handful of starter apps on GitHub, but what is generally recommended? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Ben Hughes > > > > Change & Innovation Lead > > > > Bright Approach Ltd. > > > > Tel: +447427600266 > > > > Twitter: @bwghughes > > > > http://about.me/bwghughes > > > > > > > > > > > > > > > > > > > >
There is already plenty of project on Github. I recommended a wiki because of the pedagogic side of this code and it would allow everybody to quickly comment and improve it... I'm not sure being able to clone a basic repository is the key here, but explaining the steps to get to a basic large project would have a better value (has small project are already covered)... the flask community seems pretty active, I'm sure a wiki would give the opportunity for everybody to contribute quickly and easily. We could Brice Leroy Sent from my iPhone On Feb 2, 2012, at 7:23 PM, Andy Parsons <andyparsons@gmail.com> wrote: > Github- with a link on http://flask.pocoo.org/? > > Thanks > On Thursday, February 2, 2012 at 10:16 PM, Brice Leroy wrote: > >> I can put the basics structure of a blueprint driven app with sqlalchemy and WTF. Only thing is... Where? >> >> Brice Leroy >> Sent from my iPhone >> >> On Feb 2, 2012, at 7:00 PM, Paul Gibbs <psgibbs@gmail.com> wrote: >> >>> +1. That would be incredibly helpful >>> On Thursday, February 2, 2012 at 6:57 PM, Brice Leroy wrote: >>> >>>> Could we go with a wiki page for that instead of a repository maybe? >>>> >>>> Brice Leroy >>>> Sent from my iPhone >>>> >>>> On Feb 1, 2012, at 10:37 PM, Ben Hughes <bwghughes@gmail.com> wrote: >>>> >>>>> +1 - I know this discussion has been raised before - but it would be >>>>> good for Flask to come with some basic app template generator(s). >>>>> >>>>> >>>>> >>>>> On Wed, Feb 1, 2012 at 9:55 PM, Mitul K. Jain <mituljain@gmail.com> wrote: >>>>>> +1 >>>>>> ------------------------------------------------- >>>>>> Mitul K. Jain >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Wed, Feb 1, 2012 at 6:40 PM, Andy Parsons <andyparsons @gmail.com> wrote: >>>>>>> >>>>>>> What is the consensus on the most solid template for a "large" Flask >>>>>>> project? I'm considering Flask for a large scale consumer app and find it a >>>>>>> great fit, but would like to see an example of a properly organized app with >>>>>>> multiple blueprints and routes separate from implementation. I've seen the >>>>>>> handful of starter apps on GitHub, but what is generally recommended? >>>>> >>>>> >>>>> >>>>> -- >>>>> Ben Hughes >>>>> Change & Innovation Lead >>>>> Bright Approach Ltd. >>>>> Tel: +447427600266 >>>>> Twitter: @bwghughes >>>>> http://about.me/bwghughes >>> >
If this is supposed to be "the recommended way" this should be part of the documentation. Given the information already contained within it would certainly fit content wise, it would add a certain authority to the information and there is a certain guarantee that it will be kept up-to-date. Sure it makes contribution somewhat more difficult than a Wiki but Github makes review and commenting fairly comfortable and creating a pull request is not really that much of an issue. On Feb 3, 2012, at 4:47 AM, Brice Leroy wrote: > There is already plenty of project on Github. I recommended a wiki because of the pedagogic side of this code and it would allow everybody to quickly comment and improve it... I'm not sure being able to clone a basic repository is the key here, but explaining the steps to get to a basic large project would have a better value (has small project are already covered)... the flask community seems pretty active, I'm sure a wiki would give the opportunity for everybody to contribute quickly and easily. > > We could > > Brice Leroy > Sent from my iPhone > > On Feb 2, 2012, at 7:23 PM, Andy Parsons <andyparsons@gmail.com> wrote: > >> Github- with a link on http://flask.pocoo.org/? >> >> Thanks >> On Thursday, February 2, 2012 at 10:16 PM, Brice Leroy wrote: >> >>> I can put the basics structure of a blueprint driven app with sqlalchemy and WTF. Only thing is... Where? >>> >>> Brice Leroy >>> Sent from my iPhone >>> >>> On Feb 2, 2012, at 7:00 PM, Paul Gibbs <psgibbs@gmail.com> wrote: >>> >>>> +1. That would be incredibly helpful >>>> On Thursday, February 2, 2012 at 6:57 PM, Brice Leroy wrote: >>>> >>>>> Could we go with a wiki page for that instead of a repository maybe? >>>>> >>>>> Brice Leroy >>>>> Sent from my iPhone >>>>> >>>>> On Feb 1, 2012, at 10:37 PM, Ben Hughes <bwghughes@gmail.com> wrote: >>>>> >>>>>> +1 - I know this discussion has been raised before - but it would be >>>>>> good for Flask to come with some basic app template generator(s). >>>>>> >>>>>> >>>>>> >>>>>> On Wed, Feb 1, 2012 at 9:55 PM, Mitul K. Jain <mituljain@gmail.com> wrote: >>>>>>> +1 >>>>>>> ------------------------------------------------- >>>>>>> Mitul K. Jain >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Wed, Feb 1, 2012 at 6:40 PM, Andy Parsons <andyparsons @gmail.com> wrote: >>>>>>>> >>>>>>>> What is the consensus on the most solid template for a "large" Flask >>>>>>>> project? I'm considering Flask for a large scale consumer app and find it a >>>>>>>> great fit, but would like to see an example of a properly organized app with >>>>>>>> multiple blueprints and routes separate from implementation. I've seen the >>>>>>>> handful of starter apps on GitHub, but what is generally recommended? >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Ben Hughes >>>>>> Change & Innovation Lead >>>>>> Bright Approach Ltd. >>>>>> Tel: +447427600266 >>>>>> Twitter: @bwghughes >>>>>> http://about.me/bwghughes >>>> >>
Having one recommended way for large applications is at odds with some of the philosophy behind Flask: http://flask.pocoo.org/docs/becomingbig/ I agree that we should expand the documentation with more patterns and composition, to help users grow their projects. The workflow for pull requests [open, discuss, pull or reject] imho does not fit for finding and discussing patterns. I would personally rather see a wiki than to have people dig through and comment on closed pull requests. I'm not sure where the balance is, but right now we have dozens of skeletons in the community, a frequent request for a project skeleton on the mailing list and IRC, and Flask core contributors effectively saying "No, you can't have a pony." :-) I almost never see GitHub wikis used, but this is the best case I've seen. Would a GitHub wiki work here? Use the snippets site instead? Ron 2012/2/3 Daniel Neuhäuser <dasdasich@googlemail.com>: > If this is supposed to be "the recommended way" this should be part of the > documentation. Given the information already contained within it would > certainly fit content wise, it would add a certain authority to the > information and there is a certain guarantee that it will be kept > up-to-date. > > Sure it makes contribution somewhat more difficult than a Wiki but Github > makes review and commenting fairly comfortable and creating a pull request > is not really that much of an issue. > > > On Feb 3, 2012, at 4:47 AM, Brice Leroy wrote: > > There is already plenty of project on Github. I recommended a wiki because > of the pedagogic side of this code and it would allow everybody to quickly > comment and improve it... I'm not sure b eing able to clone a basic > repository is the key here, but explaining the steps to get to a basic large > project would have a better value (has small project are already covered)... > the flask community seems pretty active, I'm sure a wiki would give the > opportunity for everybody to contribute quickly and easily. > > We could > > Brice Leroy > Sent from my iPhone > > On Feb 2, 2012, at 7:23 PM, Andy Parsons <andyparsons@gmail.com> wrote: > > Github- with a link on http://flask.pocoo.org/? > > Thanks > > On Thursday, February 2, 2012 at 10:16 PM, Brice Leroy wrote: > > I can put the basics structure of a blueprint driven app with sqlalchemy and > WTF. Only thing is... Where? > > Brice Leroy > Sent from my iPhone > > On Feb 2, 2012, at 7:00 PM, Paul Gibbs <psgibbs@gmail.com> wrote: > > +1. That would be incredibly helpful > > On Thursday, February 2, 2012 at 6:57 PM, Brice Leroy wrote: > > Could we go with a wiki page for that instead of a repository maybe? > > Brice Leroy > Sent from my iPhone > > On Feb 1, 2012, at 10:37 PM, Ben Hughes <bwghughes@gmail.com> wrote: > > +1 - I know this discussion has been raised before - but it would be > good for Flask to come with some basic app template generator(s). > > > > On Wed, Feb 1, 2012 at 9:55 PM, Mitul K. Jain <mituljain@gmail.com> wrote: > > +1 > ------------------------------------------------- > Mitul K. Jain > > > > > On Wed, Feb 1, 2012 at 6:40 PM, Andy Parsons <andyparsons @gmail.com> wrote: > > > What is the consensus on the most solid template for a "large" Flask > project? I'm considering Flask for a large scale consumer app and find it a > great fit, but would like to see an example of a properly organized app with > multiple blueprints and routes separate from implementation. I've seen the > handful of starter apps on GitHub, but what is generally recommended? > > > > > -- > Ben Hughes > Change & Innovation Lead > Bright Approach Ltd. > Tel: +447427600266 > Twitter: @bwghughes > http://about.me/bwghughes > > > >
I think a similar discussing with examples is the clearest way. + 1 On Feb 3, 2012 2:58 PM, "Ron DuPlain" <ron.duplain@gmail.com> wrote: > Having one recommended way for large applications is at odds with some > of the philosophy behind Flask: > http://flask.pocoo.org/docs/becomingbig/ > > I agree that we should expand the documentation with more patterns and > composition, to help users grow their projects. The workflow for pull > requests [open, discuss, pull or reject] imho does not fit for finding > and discussing patterns. I would personally rather see a wiki than to > have people dig through and comment on closed pull requests. > > I'm not sure where the balance is, but right now we have dozens of > skeletons in the community, a frequent request for a project skeleton > on the mailing list and IRC, and Flask core contributors effectively > saying "No, you can't have a pony." :-) > > I almost never see GitHub wikis used, but this is the best case I've > seen. Would a GitHub wiki work here? Use the snippets site instead? > > Ron > > > 2012/2/3 Daniel Neuhäuser <dasdasich@googlemail.com>: > > If this is supposed to be "the recommended way" this should be part of > the > > documentation. Given the information already contained within it would > > certainly fit content wise, it would add a certain authority to the > > information and there is a certain guarantee that it will be kept > > up-to-date. > > > > Sure it makes contribution somewhat more difficult than a Wiki but Github > > makes review and commenting fairly comfortable and creating a pull > request > > is not really that much of an issue. > > > > > > On Feb 3, 2012, at 4:47 AM, Brice Leroy wrote: > > > > There is already plenty of project on Github. I recommended a wiki > because > > of the pedagogic side of this code and it would allow everybody to > quickly > > comment and improve it... I'm not sure b eing able to clone a basic > > repository is the key here, but explaining the steps to get to a basic > large > > project would have a better value (has small project are already > covered)... > > the flask community seems pretty active, I'm sure a wiki would give the > > opportunity for everybody to contribute quickly and easily. > > > > We could > > > > Brice Leroy > > Sent from my iPhone > > > > On Feb 2, 2012, at 7:23 PM, Andy Parsons <andyparsons@gmail.com> wrote: > > > > Github- with a link on http://flask.pocoo.org/? > > > > Thanks > > > > On Thursday, February 2, 2012 at 10:16 PM, Brice Leroy wrote: > > > > I can put the basics structure of a blueprint driven app with sqlalchemy > and > > WTF. Only thing is... Where? > > > > Brice Leroy > > Sent from my iPhone > > > > On Feb 2, 2012, at 7:00 PM, Paul Gibbs <psgibbs@gmail.com> wrote: > > > > +1. That would be incredibly helpful > > > > On Thursday, February 2, 2012 at 6:57 PM, Brice Leroy wrote: > > > > Could we go with a wiki page for that instead of a repository maybe? > > > > Brice Leroy > > Sent from my iPhone > > > > On Feb 1, 2012, at 10:37 PM, Ben Hughes <bwghughes@gmail.com> wrote: > > > > +1 - I know this discussion has been raised before - but it would be > > good for Flask to come with some basic app template generator(s). > > > > > > > > On Wed, Feb 1, 2012 at 9:55 PM, Mitul K. Jain <mituljain@gmail.com> > wrote: > > > > +1 > > ------------------------------------------------- > > Mitul K. Jain > > > > > > > > > > On Wed, Feb 1, 2012 at 6:40 PM, Andy Parsons <andyparsons @gmail.com> > wrote: > > > > > > What is the consensus on the most solid template for a "large" Flask > > project? I'm considering Flask for a large scale consumer app and find > it a > > great fit, but would like to see an example of a properly organized app > with > > multiple blueprints and routes separate from implementation. I've seen > the > > handful of starter apps on GitHub, but what is generally recommended? > > > > > > > > > > -- > > Ben Hughes > > Change & Innovation Lead > > Bright Approach Ltd. > > Tel: +447427600266 > > Twitter: @bwghughes > > http://about.me/bwghughes > > > > > > > > >
As the guy who instigated the thread :) I concur and reverse my recommendation for a repo. I wonder if we can split the difference- either GitHub wiki or the snippets site would work IMHO, with the community free to take inspiration and build GitHub repos based on recommendations. The snippets option gives it a bit of a more "official" flavor to it. For my purposes, I'm far less interested in a single Pocoo-blessed skeleton than in the common patterns emerging as folks develop best practices. I'm doing exactly that right now with my new startup, and find myself second guessing my project org decisions quite frequently. On Friday, February 3, 2012 at 9:57 AM, Ron DuPlain wrote: > Having one recommended way for large applications is at odds with some > of the philosophy behind Flask: > http://flask.pocoo.org/docs/becomingbig/ > > I agree that we should expand the documentation with more patterns and > composition, to help users grow their projects. The workflow for pull > requests [open, discuss, pull or reject] imho does not fit for finding > and discussing patterns. I would personally rather see a wiki than to > have people dig through and comment on closed pull requests. > > I'm not sure where the balance is, but right now we have dozens of > skeletons in the community, a frequent request for a project skeleton > on the mailing list and IRC, and Flask core contributors effectively > saying "No, you can't have a pony." :-) > > I almost never see GitHub wikis used, but this is the best case I've > seen. Would a GitHub wiki work here? Use the snippets site instead? > > Ron > > > 2012/2/3 Daniel Neuhäuser <dasdasich@googlemail.com (mailto:dasdasich@googlemail.com)>: > > If this is supposed to be "the recommended way" this should be part of the > > documentation. Given the information already contained within it would > > certainly fit content wise, it would add a certain authority to the > > information and there is a certain guarantee that it will be kept > > up-to-date. > > > > Sure it makes contribution somewhat more difficult than a Wiki but Github > > makes review and commenting fairly comfortable and creating a pull request > > is not really that much of an issue. > > > > > > On Feb 3, 2012, at 4:47 AM, Brice Leroy wrote: > > > > There is already plenty of project on Github. I recommended a wiki because > > of the pedagogic side of this code and it would allow everybody to quickly > > comment and improve it... I'm not sure b eing able to clone a basic > > repository is the key here, but explaining the steps to get to a basic large > > project would have a better value (has small project are already covered)... > > the flask community seems pretty active, I'm sure a wiki would give the > > opportunity for everybody to contribute quickly and easily. > > > > We could > > > > Brice Leroy > > Sent from my iPhone > > > > On Feb 2, 2012, at 7:23 PM, Andy Parsons <andyparsons@gmail.com (mailto:andyparsons@gmail.com)> wrote: > > > > Github- with a link on http://flask.pocoo.org/? > > > > Thanks > > > > On Thursday, February 2, 2012 at 10:16 PM, Brice Leroy wrote: > > > > I can put the basics structure of a blueprint driven app with sqlalchemy and > > WTF. Only thing is... Where? > > > > Brice Leroy > > Sent from my iPhone > > > > On Feb 2, 2012, at 7:00 PM, Paul Gibbs <psgibbs@gmail.com (mailto:psgibbs@gmail.com)> wrote: > > > > +1. That would be incredibly helpful > > > > On Thursday, February 2, 2012 at 6:57 PM, Brice Leroy wrote: > > > > Could we go with a wiki page for that instead of a repository maybe? > > > > Brice Leroy > > Sent from my iPhone > > > > On Feb 1, 2012, at 10:37 PM, Ben Hughes <bwghughes@gmail.com (mailto:bwghughes@gmail.com)> wrote: > > > > +1 - I know this discussion has been raised before - but it would be > > good for Flask to come with some basic app template generator(s). > > > > > > > > On Wed, Feb 1, 2012 at 9:55 PM, Mitul K. Jain <mituljain@gmail.com (mailto:mituljain@gmail.com)> wrote: > > > > +1 > > ------------------------------------------------- > > Mitul K. Jain > > > > > > > > > > On Wed, Feb 1, 2012 at 6:40 PM, Andy Parsons <andyparsons @gmail.com (http://gmail.com)> wrote: > > > > > > What is the consensus on the most solid template for a "large" Flask > > project? I'm considering Flask for a large scale consumer app and find it a > > great fit, but would like to see an example of a properly organized app with > > multiple blueprints and routes separate from implementation. I've seen the > > handful of starter apps on GitHub, but what is generally recommended? > > > > > > > > > > -- > > Ben Hughes > > Change & Innovation Lead > > Bright Approach Ltd. > > Tel: +447427600266 > > Twitter: @bwghughes > > http://about.me/bwghughes > > > > >
Yeah Andy, this was exactly where I was coming from too. Having that 'official' feel but from the community instead of a single source. I think a wiki could capture this quite well. Skeleton repos are sure to follow, based off the wiki content. They'll have some personal touches, of course. Then newcomers will be able to see more consistency in skeleton projects. On Fri, Feb 3, 2012 at 10:27 AM, Andy Parsons <andyparsons@gmail.com> wrote: > As the guy who instigated the thread :) I concur and reverse my > recommendation for a repo. I wonder if we can split the difference- either > GitHub wiki or the snippets site would work IMHO, with the community free > to take inspiration and build GitHub repos based on recommendations. The > snippets option gives it a bit of a more "official" flavor to it. For my > purposes, I'm far less interested in a single Pocoo-blessed skeleton than > in the common patterns emerging as folks develop best practices. I'm doing > exactly that right now with my new startup, and find myself second guessing > my project org decisions quite frequently. > > On Friday, February 3, 2012 at 9:57 AM, Ron DuPlain wrote: > > Having one recommended way for large applications is at odds with some > of the philosophy behind Flask: > http://flask.pocoo.org/docs/becomingbig/ > > I agree that we should expand the documentation with more patterns and > composition, to help users grow their projects. The workflow for pull > requests [open, discuss, pull or reject] imho does not fit for finding > and discussing patterns. I would personally rather see a wiki than to > have people dig through and comment on closed pull requests. > > I'm not sure where the balance is, but right now we have dozens of > skeletons in the community, a frequent request for a project skeleton > on the mailing list and IRC, and Flask core contributors effectively > saying "No, you can't have a pony." :-) > > I almost never see GitHub wikis used, but this is the best case I've > seen. Would a GitHub wiki work here? Use the snippets site instead? > > Ron > > > 2012/2/3 Daniel Neuhäuser <dasdasich@googlemail.com>: > > If this is supposed to be "the recommended way" this should be part of the > documentation. Given the information already contained within it would > certainly fit content wise, it would add a certain authority to the > information and there is a certain guarantee that it will be kept > up-to-date. > > Sure it makes contribution somewhat more difficult than a Wiki but Github > makes review and commenting fairly comfortable and creating a pull request > is not really that much of an issue. > > > On Feb 3, 2012, at 4:47 AM, Brice Leroy wrote: > > There is already plenty of project on Github. I recommended a wiki because > of the pedagogic side of this code and it would allow everybody to quickly > comment and improve it... I'm not sure b eing able to clone a basic > repository is the key here, but explaining the steps to get to a basic > large > project would have a better value (has small project are already > covered)... > the flask community seems pretty active, I'm sure a wiki would give the > opportunity for everybody to contribute quickly and easily. > > We could > > Brice Leroy > Sent from my iPhone > > On Feb 2, 2012, at 7:23 PM, Andy Parsons <andyparsons@gmail.com> wrote: > > Github- with a link on http://flask.pocoo.org/? > > Thanks > > On Thursday, February 2, 2012 at 10:16 PM, Brice Leroy wrote: > > I can put the basics structure of a blueprint driven app with sqlalchemy > and > WTF. Only thing is... Where? > > Brice Leroy > Sent from my iPhone > > On Feb 2, 2012, at 7:00 PM, Paul Gibbs <psgibbs@gmail.com> wrote: > > +1. That would be incredibly helpful > > On Thursday, February 2, 2012 at 6:57 PM, Brice Leroy wrote: > > Could we go with a wiki page for that instead of a repository maybe? > > Brice Leroy > Sent from my iPhone > > On Feb 1, 2012, at 10:37 PM, Ben Hughes <bwghughes@gmail.com> wrote: > > +1 - I know this discussion has been raised before - but it would be > good for Flask to come with some basic app template generator(s). > > > > On Wed, Feb 1, 2012 at 9:55 PM, Mitul K. Jain <mituljain@gmail.com> wrote: > > +1 > ------------------------------------------------- > Mitul K. Jain > > > > > On Wed, Feb 1, 2012 at 6:40 PM, Andy Parsons <andyparsons @gmail.com> > wrote: > > > What is the consensus on the most solid template for a "large" Flask > project? I'm considering Flask for a large scale consumer app and find it a > great fit, but would like to see an example of a properly organized app > with > multiple blueprints and routes separate from implementation. I've seen the > handful of starter apps on GitHub, but what is generally recommended? > > > > > -- > Ben Hughes > Change & Innovation Lead > Bright Approach Ltd. > Tel: +447427600266 > Twitter: @bwghughes > http://about.me/bwghughes > > >
+1 that I was not sure how to start the wiki. My idea was to describe the first step of a large project with enough complexity To demonstrate how we resolve those issue (generic relation, 1to1, 1toM and MtoM, mailing solution, unit testing, test suites...) Keeping the large project concept in mind, another thing I would personally like to see in it is unit-testing and how to develop from them (instead of back testing). Scaling should also be a part of it (caching, noSQL, clustering, database partitioning) And I also like the wiki idea for it forgiveness :) Brice On Feb 3, 2012, at 7:36 AM, Joe Esposito <espo58@gmail.com> wrote: > Yeah Andy, this was exactly where I was coming from too. Having that 'official' feel but from the community instead of a single source. I think a wiki could capture this quite well. > > Skeleton repos are sure to follow, based off the wiki content. They'll have some personal touches, of course. Then newcomers will be able to see more consistency in skeleton projects. > > On Fri, Feb 3, 2012 at 10:27 AM, Andy Parsons <andyparsons@gmail.com> wrote: > As the guy who instigated the thread :) I concur and reverse my recommendation for a repo. I wonder if we can split the difference- either GitHub wiki or the snippets site would work IMHO, with the community free to take inspiration and build GitHub repos based on recommendations. The snippets option gives it a bit of a more "official" flavor to it. For my purposes, I'm far less interested in a single Pocoo-blessed skeleton than in the common patterns emerging as folks develop best practices. I'm doing exactly that right now with my new startup, and find myself second guessing my project org decisions quite frequently. > On Friday, February 3, 2012 at 9:57 AM, Ron DuPlain wrote: > >> Having one recommended way for large applications is at odds with some >> of the philosophy behind Flask: >> http://flask.pocoo.org/docs/becomingbig/ >> >> I agree that we should expand the documentation with more patterns and >> composition, to help users grow their projects. The workflow for pull >> requests [open, discuss, pull or reject] imho does not fit for finding >> and discussing patterns. I would personally rather see a wiki than to >> have people dig through and comment on closed pull requests. >> >> I'm not sure where the balance is, but right now we have dozens of >> skeletons in the community, a frequent request for a project skeleton >> on the mailing list and IRC, and Flask core contributors effectively >> saying "No, you can't have a pony." :-) >> >> I almost never see GitHub wikis used, but this is the best case I've >> seen. Would a GitHub wiki work here? Use the snippets site instead? >> >> Ron >> >> >> 2012/2/3 Daniel Neuhäuser <dasdasich@googlemail.com>: >>> If this is supposed to be "the recommended way" this should be part of the >>> documentation. Given the information already contained within it would >>> certainly fit content wise, it would add a certain authority to the >>> information and there is a certain guarantee that it will be kept >>> up-to-date. >>> >>> Sure it makes contribution somewhat more difficult than a Wiki but Github >>> makes review and commenting fairly comfortable and creating a pull request >>> is not really that much of an issue. >>> >>> >>> On Feb 3, 2012, at 4:47 AM, Brice Leroy wrote: >>> >>> There is already plenty of project on Github. I recommended a wiki because >>> of the pedagogic side of this code and it would allow everybody to quickly >>> comment and improve it... I'm not sure b eing able to clone a basic >>> repository is the key here, but explaining the steps to get to a basic large >>> project would have a better value (has small project are already covered)... >>> the flask community seems pretty active, I'm sure a wiki would give the >>> opportunity for everybody to contribute quickly and easily. >>> >>> We could >>> >>> Brice Leroy >>> Sent from my iPhone >>> >>> On Feb 2, 2012, at 7:23 PM, Andy Parsons <andyparsons@gmail.com> wrote: >>> >>> Github- with a link on http://flask.pocoo.org/? >>> >>> Thanks >>> >>> On Thursday, February 2, 2012 at 10:16 PM, Brice Leroy wrote: >>> >>> I can put the basics structure of a blueprint driven app with sqlalchemy and >>> WTF. Only thing is... Where? >>> >>> Brice Leroy >>> Sent from my iPhone >>> >>> On Feb 2, 2012, at 7:00 PM, Paul Gibbs <psgibbs@gmail.com> wrote: >>> >>> +1. That would be incredibly helpful >>> >>> On Thursday, February 2, 2012 at 6:57 PM, Brice Leroy wrote: >>> >>> Could we go with a wiki page for that instead of a repository maybe? >>> >>> Brice Leroy >>> Sent from my iPhone >>> >>> On Feb 1, 2012, at 10:37 PM, Ben Hughes <bwghughes@gmail.com> wrote: >>> >>> +1 - I know this discussion has been raised before - but it would be >>> good for Flask to come with some basic app template generator(s). >>> >>> >>> >>> On Wed, Feb 1, 2012 at 9:55 PM, Mitul K. Jain <mituljain@gmail.com> wrote: >>> >>> +1 >>> ------------------------------------------------- >>> Mitul K. Jain >>> >>> >>> >>> >>> On Wed, Feb 1, 2012 at 6:40 PM, Andy Parsons <andyparsons @gmail.com> wrote: >>> >>> >>> What is the consensus on the most solid template for a "large" Flask >>> project? I'm considering Flask for a large scale consumer app and find it a >>> great fit, but would like to see an example of a properly organized app with >>> multiple blueprints and routes separate from implementation. I've seen the >>> handful of starter apps on GitHub, but what is generally recommended? >>> >>> >>> >>> >>> -- >>> Ben Hughes >>> Change & Innovation Lead >>> Bright Approach Ltd. >>> Tel: +447427600266 >>> Twitter: @bwghughes >>> http://about.me/bwghughes > >
maybe it ins just me, but i think there should not be an "official" boilerplate. Flask is a microframework, you can just start with a single file. There are different ways how you can extend your app, with different advantages or disadvantages. I choose flask now for projects because I can do stuff my way. It might not be the best way, but I know how it is working and why. I don't like frameworks like django, rails or symfony where your project has already many files before you even start. I have nothing against the idea of different project templates, but there should be not one that is called the correct or official one.
+1 The documentation should be clear and provide examples but Flask is awesome because it is so small. Adding a boilerplate would, I feel, change the nature of the project itself. On Feb 3, 2012, at 12:47, Bastian Hoyer <dafire@gmail.com> wrote: maybe it ins just me, but i think there should not be an "official" boilerplate. Flask is a microframework, you can just start with a single file. There are different ways how you can extend your app, with different advantages or disadvantages. I choose flask now for projects because I can do stuff my way. It might not be the best way, but I know how it is working and why. I don't like frameworks like django, rails or symfony where your project has already many files before you even start. I have nothing against the idea of different project templates, but there should be not one that is called the correct or official one.
+1 Le 3 févr. 2012 19:14, "Todd Kennedy" <todd.kennedy@gmail.com> a écrit : > +1 > > The documentation should be clear and provide examples but Flask is > awesome because it is so small. Adding a boilerplate would, I feel, change > the nature of the project itself. > > On Feb 3, 2012, at 12:47, Bastian Hoyer <dafire@gmail.com> wrote: > > maybe it ins just me, but i think there should not be an "official" > boilerplate. Flask is a microframework, you can just start with a single > file. There are different ways how you can extend your app, with different > advantages or disadvantages. > I choose flask now for projects because I can do stuff my way. It might > not be the best way, but I know how it is working and why. I don't like > frameworks like django, rails or symfony where your project has already > many files before you even start. > I have nothing against the idea of different project templates, but there > should be not one that is called the correct or official one. > >
+1 Agree. On 2012-02-03, at 01:08 PM, Todd Kennedy wrote: > +1 > > The documentation should be clear and provide examples but Flask is awesome because it is so small. Adding a boilerplate would, I feel, change the nature of the project itself. > > On Feb 3, 2012, at 12:47, Bastian Hoyer <dafire@gmail.com> wrote: > >> maybe it ins just me, but i think there should not be an "official" boilerplate. Flask is a microframework, you can just start with a single file. There are different ways how you can extend your app, with different advantages or disadvantages. >> I choose flask now for projects because I can do stuff my way. It might not be the best way, but I know how it is working and why. I don't like frameworks like django, rails or symfony where your project has already many files before you even start. >> I have nothing against the idea of different project templates, but there should be not one that is called the correct or official one. >>
Dear people, I recommend to create this Flask HOW-TO based on Flask-Empty and use Blueprints for modules. You can also use some patterns from http://flask.pocoo.org/docs/patterns/ We changed our app structure in order to use a create_app() function, since we need to create new empty app instances for unit tests. I also would like to get some suggestions to organize flask extensions, like cache and mail, since they have a lazy app initialization. Kind regards, *Osvaldo Matos Júnior* Tuπ da Bahia! tupy@jusbrasil.com.br www.jusbrasil.com.br 2012/2/3 Daniel Neuhäuser <dasdasich@googlemail.com> > If this is supposed to be "the recommended way" this should be part of the > documentation. Given the information already contained within it would > certainly fit content wise, it would add a certain authority to the > information and there is a certain guarantee that it will be kept > up-to-date. > > Sure it makes contribution somewhat more difficult than a Wiki but Github > makes review and commenting fairly comfortable and creating a pull request > is not really that much of an issue. > > > On Feb 3, 2012, at 4:47 AM, Brice Leroy wrote: > > There is already plenty of project on Github. I recommended a wiki because > of the pedagogic side of this code and it would allow everybody to quickly > comment and improve it... I'm not sure b eing able to clone a basic > repository is the key here, but explaining the steps to get to a basic > large project would have a better value (has small project are already > covered)... the flask community seems pretty active, I'm sure a wiki would > give the opportunity for everybody to contribute quickly and easily. > > We could > > Brice Leroy > Sent from my iPhone > > On Feb 2, 2012, at 7:23 PM, Andy Parsons <andyparsons@gmail.com> wrote: > > Github- with a link on http://flask.pocoo.org/? > > Thanks > > On Thursday, February 2, 2012 at 10:16 PM, Brice Leroy wrote: > > I can put the basics structure of a blueprint driven app with sqlalchemy > and WTF. Only thing is... Where? > > Brice Leroy > Sent from my iPhone > > On Feb 2, 2012, at 7:00 PM, Paul Gibbs <psgibbs@gmail.com> wrote: > > +1. That would be incredibly helpful > > On Thursday, February 2, 2012 at 6:57 PM, Brice Leroy wrote: > > Could we go with a wiki page for that instead of a repository maybe? > > Brice Leroy > Sent from my iPhone > > On Feb 1, 2012, at 10:37 PM, Ben Hughes <bwghughes@gmail.com> wrote: > > +1 - I know this discussion has been raised before - but it would be > good for Flask to come with some basic app template generator(s). > > > > On Wed, Feb 1, 2012 at 9:55 PM, Mitul K. Jain <mituljain@gmail.com> wrote: > > +1 > ------------------------------------------------- > Mitul K. Jain > > > > > On Wed, Feb 1, 2012 at 6:40 PM, Andy Parsons <andyparsons @gmail.com<andyparsons@gmail.com>> > wrote: > > > What is the consensus on the most solid template for a "large" Flask > project? I'm considering Flask for a large scale consumer app and find it a > great fit, but would like to see an example of a properly organized app > with > multiple blueprints and routes separate from implementation. I've seen the > handful of starter apps on GitHub, but what is generally recommended? > > > > > -- > Ben Hughes > Change & Innovation Lead > Bright Approach Ltd. > Tel: +447427600266 > Twitter: @bwghughes > http://about.me/bwghughes > > > > >
Yes, organizing/initializing extensions is a good example of a place I could use some recommendations as well. On Friday, February 3, 2012 at 7:28 AM, Tupy wrote: > Dear people, > > I recommend to create this Flask HOW-TO based on Flask-Empty and use Blueprints for modules. > You can also use some patterns from http://flask.pocoo.org/docs/patterns/ > We changed our app structure in order to use a create_app() function, since we need to create new empty app instances for unit tests. > I also would like to get some suggestions to organize flask extensions, like cache and mail, since they have a lazy app initialization. > > Kind regards, > > > Osvaldo Matos Júnior > Tuπ da Bahia! > tupy@jusbrasil.com.br (mailto:tupy@jusbrasil.com.br) > www.jusbrasil.com.br (http://www.jusbrasil.com.br) > > > > > 2012/2/3 Daniel Neuhäuser <dasdasich@googlemail.com (mailto:dasdasich@googlemail.com)> > > If this is supposed to be "the recommended way" this should be part of the documentation. Given the information already contained within it would certainly fit content wise, it would add a certain authority to the information and there is a certain guarantee that it will be kept up-to-date. > > > > Sure it makes contribution somewhat more difficult than a Wiki but Github makes review and commenting fairly comfortable and creating a pull request is not really that much of an issue. > > > > > > On Feb 3, 2012, at 4:47 AM, Brice Leroy wrote: > > > There is already plenty of project on Github. I recommended a wiki because of the pedagogic side of this code and it would allow everybody to quickly comment and improve it... I'm not sure b eing able to clone a basic repository is the key here, but explaining the steps to get to a basic large project would have a better value (has small project are already covered)... the flask community seems pretty active, I'm sure a wiki would give the opportunity for everybody to contribute quickly and easily. > > > > > > We could > > > > > > Brice Leroy > > > Sent from my iPhone > > > > > > > > > On Feb 2, 2012, at 7:23 PM, Andy Parsons <andyparsons@gmail.com (mailto:andyparsons@gmail.com)> wrote: > > > > > > > Github- with a link on http://flask.pocoo.org/? > > > > > > > > Thanks > > > > > > > > On Thursday, February 2, 2012 at 10:16 PM, Brice Leroy wrote: > > > > > > > > > I can put the basics structure of a blueprint driven app with sqlalchemy and WTF. Only thing is... Where? > > > > > > > > > > Brice Leroy > > > > > Sent from my iPhone > > > > > > > > > > > > > > > On Feb 2, 2012, at 7:00 PM, Paul Gibbs <psgibbs@gmail.com (mailto:psgibbs@gmail.com)> wrote: > > > > > > > > > > > +1. That would be incredibly helpful > > > > > > > > > > > > On Thursday, February 2, 2012 at 6:57 PM, Brice Leroy wrote: > > > > > > > > > > > > > Could we go with a wiki page for that instead of a repository maybe? > > > > > > > > > > > > > > Brice Leroy > > > > > > > Sent from my iPhone > > > > > > > > > > > > > > On Feb 1, 2012, at 10:37 PM, Ben Hughes <bwghughes@gmail.com (mailto:bwghughes@gmail.com)> wrote: > > > > > > > > > > > > > > > +1 - I know this discussion has been raised before - but it would be > > > > > > > > good for Flask to come with some basic app template generator(s). > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Wed, Feb 1, 2012 at 9:55 PM, Mitul K. Jain <mituljain@gmail.com (mailto:mituljain@gmail.com)> wrote: > > > > > > > > > +1 > > > > > > > > > ------------------------------------------------- > > > > > > > > > Mitul K. Jain > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Wed, Feb 1, 2012 at 6:40 PM, Andy Parsons <andyparsons @gmail.com (mailto:andyparsons@gmail.com)> wrote: > > > > > > > > > > > > > > > > > > > > What is the consensus on the most solid template for a "large" Flask > > > > > > > > > > project? I'm considering Flask for a large scale consumer app and find it a > > > > > > > > > > great fit, but would like to see an example of a properly organized app with > > > > > > > > > > multiple blueprints and routes separate from implementation. I've seen the > > > > > > > > > > handful of starter apps on GitHub, but what is generally recommended? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > Ben Hughes > > > > > > > > Change & Innovation Lead > > > > > > > > Bright Approach Ltd. > > > > > > > > Tel: +447427600266 (tel:%2B447427600266) > > > > > > > > Twitter: @bwghughes > > > > > > > > http://about.me/bwghughes > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
If a wiki is the way to go: https://github.com/mitsuhiko/flask/wiki It *might* be better served as something next to: http://flask.pocoo.org/snippets/ But Armin hasn't turned off the wiki on github. :-) -Ron On Thu, Feb 2, 2012 at 10:47 PM, Brice Leroy <bbrriiccee@gmail.com> wrote: > There is already plenty of project on Github. I recommended a wiki because > of the pedagogic side of this code and it would allow everybody to quickly > comment and improve it... I'm not sure being able to clone a basic > repository is the key here, but explaining the steps to get to a basic large > project would have a better value (has small project are already covered)... > the flask community seems pretty active, I'm sure a wiki would give the > opportunity for everybody to contribute quickly and easily. > > We could > > > Brice Leroy > Sent from my iPhone > > On Feb 2, 2012, at 7:23 PM, Andy Parsons <andyparsons@gmail.com> wrote: > > Github- with a link on http://flask.pocoo.org/? > > Thanks > > On Thursday, February 2, 2012 at 10:16 PM, Brice Leroy wrote: > > I can put the basics structure of a blueprint driven app with sqlalchemy and > WTF. Only thing is... Where? > > Brice Leroy > Sent from my iPhone > > On Feb 2, 2012, at 7:00 PM, Paul Gibbs <psgibbs@gmail.com> wrote: > > +1. That would be incredibly helpful > > On Thursday, February 2, 2012 at 6:57 PM, Brice Leroy wrote: > > Could we go with a wiki page for that instead of a repository maybe? > > Brice Leroy > Sent from my iPhone > > On Feb 1, 2012, at 10:37 PM, Ben Hughes <bwghughes@gmail.com> wrote: > > +1 - I know this discussion has been raised before - but it would be > good for Flask to come with some basic app template generator(s). > > > > On Wed, Feb 1, 2012 at 9:55 PM, Mitul K. Jain <mituljain@gmail.com> wrote: > > +1 > ------------------------------------------------- > Mitul K. Jain > > > > > On Wed, Feb 1, 2012 at 6:40 PM, Andy Parsons <andyparsons @gmail.com> wrote: > > > What is the consensus on the most solid template for a "large" Flask > project? I'm considering Flask for a large scale consumer app and find it a > great fit, but would like to see an example of a properly organized app with > multiple blueprints and routes separate from implementation. I've seen the > handful of starter apps on GitHub, but what is generally recommended? > > > > > -- > Ben Hughes > Change & Innovation Lead > Bright Approach Ltd. > Tel: +447427600266 > Twitter: @bwghughes > http://about.me/bwghughes > > >
I started it at https://github.com/mitsuhiko/flask/wiki/Large-app-how-to 2012/2/2 Ron DuPlain <ron.duplain@gmail.com> > If a wiki is the way to go: > https://github.com/mitsuhiko/flask/wiki > > It *might* be better served as something next to: > http://flask.pocoo.org/snippets/ > > But Armin hasn't turned off the wiki on github. :-) > > -Ron > > > On Thu, Feb 2, 2012 at 10:47 PM, Brice Leroy <bbrriiccee@gmail.com> wrote: > > There is already plenty of project on Github. I recommended a wiki > because > > of the pedagogic side of this code and it would allow everybody to > quickly > > comment and improve it... I'm not sure being able to clone a basic > > repository is the key here, but explaining the steps to get to a basic > large > > project would have a better value (has small project are already > covered)... > > the flask community seems pretty active, I'm sure a wiki would give the > > opportunity for everybody to contribute quickly and easily. > > > > We could > > > > > > Brice Leroy > > Sent from my iPhone > > > > On Feb 2, 2012, at 7:23 PM, Andy Parsons <andyparsons@gmail.com> wrote: > > > > Github- with a link on http://flask.pocoo.org/? > > > > Thanks > > > > On Thursday, February 2, 2012 at 10:16 PM, Brice Leroy wrote: > > > > I can put the basics structure of a blueprint driven app with sqlalchemy > and > > WTF. Only thing is... Where? > > > > Brice Leroy > > Sent from my iPhone > > > > On Feb 2, 2012, at 7:00 PM, Paul Gibbs <psgibbs@gmail.com> wrote: > > > > +1. That would be incredibly helpful > > > > On Thursday, February 2, 2012 at 6:57 PM, Brice Leroy wrote: > > > > Could we go with a wiki page for that instead of a repository maybe? > > > > Brice Leroy > > Sent from my iPhone > > > > On Feb 1, 2012, at 10:37 PM, Ben Hughes <bwghughes@gmail.com> wrote: > > > > +1 - I know this discussion has been raised before - but it would be > > good for Flask to come with some basic app template generator(s). > > > > > > > > On Wed, Feb 1, 2012 at 9:55 PM, Mitul K. Jain <mituljain@gmail.com> > wrote: > > > > +1 > > ------------------------------------------------- > > Mitul K. Jain > > > > > > > > > > On Wed, Feb 1, 2012 at 6:40 PM, Andy Parsons <andyparsons @gmail.com> > wrote: > > > > > > What is the consensus on the most solid template for a "large" Flask > > project? I'm considering Flask for a large scale consumer app and find > it a > > great fit, but would like to see an example of a properly organized app > with > > multiple blueprints and routes separate from implementation. I've seen > the > > handful of starter apps on GitHub, but what is generally recommended? > > > > > > > > > > -- > > Ben Hughes > > Change & Innovation Lead > > Bright Approach Ltd. > > Tel: +447427600266 > > Twitter: @bwghughes > > http://about.me/bwghughes > > > > > > > -- blog: http://www.debrice.com Time tracking tool: http://alpha.kaaloo.com Django site generator: http://alpha.djangogenerator.com linkedin: http://www.linkedin.com/in/bricepleroy
Hi I don't think armin will like this concept of boiler plate. Some one can create a repo, and we can add the details under snippet section pointing to repo at the end. -- * Thanks & Regards "Talk is cheap, show me the code" -- Linus Torvalds kracekumar www.kracekumar.com *