Hi all, I think there is a project enables to create an flask application with a template ? Add a new script called flask in a bin directory, this script could generate a skeleton of a flask app. For example, > flask -d flask_demo This command will create a flask_demo with some basic files for a flask app. > find flask_demo > flask_demo/README > flask_demo/LICENSE > flask_demo/flask_demo.wsgi Will contain a basic configuration but will have a commente code if we use virtualenv > flask_demo/setup.py > flask_demo/manage.py > flask_demo/flask_demo/__init__.py > flask_demo/flask_demo/static/style.css > flask_demo/flask_demo/static/logo.png > flask_demo/flask_demo/templates/frontend/index.html > flask_demo/flask_demo/views/frontend.py > flask_demo/doc/server/apache.conf > flask_demo/doc/server/gunicorn.conf > ... What do you think about that ? Regards, Stephane
Hi, On 2010-09-01 1:55 PM, Stephane Wirtel wrote: > I think there is a project enables to create an flask application > with a template ? I think someone wrote a paster template. > Add a new script called flask in a bin directory, this script could > generate a skeleton of a flask app. If you want to implement something like that, please use a different name for the script. At one point flask might ship a command line script for a different purpose and then the name should not be taken. Regards, Armin
On 09/01/2010 01:57 PM, Armin Ronacher wrote: > Hi, > > On 2010-09-01 1:55 PM, Stephane Wirtel wrote: >> I think there is a project enables to create an flask application >> with a template ? > I think someone wrote a paster template. I think it's Dan, but not sure. the project is on github or bitbucket > >> Add a new script called flask in a bin directory, this script could >> generate a skeleton of a flask app. > If you want to implement something like that, please use a different > name for the script. At one point flask might ship a command line > script for a different purpose and then the name should not be taken. Ok, If there is a paster template, this script won't be useful and will be redundant with the paster template. Thanks Stephane > > > Regards, > Armin
I wrote a general paster template for a Werkzeug app some time ago, but abandoned it when Flask came along. It might be easier to implement a template without paster - using Jinja2 for example to generate code. However I'm not sure how useful it would be, as Flask apps tend to vary so much and require so little code to get started with. On 1 September 2010 13:00, Stephane Wirtel <stephane@wirtel.be> wrote: > On 09/01/2010 01:57 PM, Armin Ronacher wrote: >> Hi, >> >> On 2010-09-01 1:55 PM, Stephane Wirtel wrote: >>> I think there is a project enables to create an flask application >>> with a template ? >> I think someone wrote a paster template. > I think it's Dan, but not sure. the project is on github or bitbucket >> >>> Add a new script called flask in a bin directory, this script could >>> generate a skeleton of a flask app. >> If you want to implement something like that, please use a different >> name for the script. At one point flask might ship a command line >> script for a different purpose and then the name should not be taken. > Ok, If there is a paster template, this script won't be useful and will be redundant with the paster template. > > Thanks > > Stephane > >> >> >> Regards, >> Armin > >
On 09/01/2010 02:07 PM, Dan Jacob wrote: > I wrote a general paster template for a Werkzeug app some time ago, > but abandoned it when Flask came along. > > It might be easier to implement a template without paster - using > Jinja2 for example to generate code. However I'm not sure how useful > it would be, as Flask apps tend to vary so much and require so little > code to get started with. Not sure, in my case, the flask apps don't change every time. I use the same layout, a logical layout based on the code of Flask-Website and Newsmeme.
Hi, On 2010-09-01 2:07 PM, Dan Jacob wrote: > I wrote a general paster template for a Werkzeug app some time ago, > but abandoned it when Flask came along. > > It might be easier to implement a template without paster - using > Jinja2 for example to generate code. However I'm not sure how useful > it would be, as Flask apps tend to vary so much and require so little > code to get started with. What I like about the tipfy project is that they have a form on the website that you can fill out and it generates a tarball for a new extension with a setup.py and everything. I think that might be interesting to have for both Flask projects and Flask extensions. The flask-extension-wizard is okayish but not that nice, especially because everybody misses it. Regards, Armin
On 09/01/2010 02:09 PM, Armin Ronacher wrote: > Hi, > > On 2010-09-01 2:07 PM, Dan Jacob wrote: >> I wrote a general paster template for a Werkzeug app some time ago, >> but abandoned it when Flask came along. >> >> It might be easier to implement a template without paster - using >> Jinja2 for example to generate code. However I'm not sure how useful >> it would be, as Flask apps tend to vary so much and require so little >> code to get started with. > What I like about the tipfy project is that they have a form on the > website that you can fill out and it generates a tarball for a new > extension with a setup.py and everything. > > I think that might be interesting to have for both Flask projects and > Flask extensions. The flask-extension-wizard is okayish but not that > nice, especially because everybody misses it. > > > Regards, > Armin Two templates, first one for the extension, the second one for a flask app. It's the fourth time where I use flask and it's the same thing, define a setup.py, a readme, a license, a doc for Apache and WSGI, a frontend and the same modules. software-template is a dummy name and this software will be maintained by the team. software-template -t flask-extension -d my_flask_extension software-template -t flask-app -d my_flask_app Regards, Stéphane
I have one here http://bitbucket.org/danjac/flask-projectmaker but it's quite opinionated (e.g. includes certain extensions). It's really just for my own use but feel free to copy what you need. On 1 September 2010 13:14, Stephane Wirtel <stephane@wirtel.be> wrote: > On 09/01/2010 02:09 PM, Armin Ronacher wrote: >> Hi, >> >> On 2010-09-01 2:07 PM, Dan Jacob wrote: >>> I wrote a general paster template for a Werkzeug app some time ago, >>> but abandoned it when Flask came along. >>> >>> It might be easier to implement a template without paster - using >>> Jinja2 for example to generate code. However I'm not sure how useful >>> it would be, as Flask apps tend to vary so much and require so little >>> code to get started with. >> What I like about the tipfy project is that they have a form on the >> website that you can fill out and it generates a tarball for a new >> extension with a setup.py and everything. >> >> I think that might be interesting to have for both Flask projects and >> Flask extensions. The flask-extension-wizard is okayish but not that >> nice, especially because everybody misses it. >> >> >> Regards, >> Armin > > Two templates, first one for the extension, the second one for a flask app. > > It's the fourth time where I use flask and it's the same thing, > define a setup.py, a readme, a license, a doc for Apache and WSGI, > a frontend and the same modules. > > software-template is a dummy name and this software will be maintained by the team. > > software-template -t flask-extension -d my_flask_extension > > software-template -t flask-app -d my_flask_app > > Regards, > > Stéphane >
I like your project, it's very useful. very specific but very useful. Do you believe we can create a a generic tool ? Regards, Stéphane On 09/01/2010 02:17 PM, Dan Jacob wrote: > I have one here http://bitbucket.org/danjac/flask-projectmaker but > it's quite opinionated (e.g. includes certain extensions). It's really > just for my own use but feel free to copy what you need. > > On 1 September 2010 13:14, Stephane Wirtel <stephane@wirtel.be> wrote: >> On 09/01/2010 02:09 PM, Armin Ronacher wrote: >>> Hi, >>> >>> On 2010-09-01 2:07 PM, Dan Jacob wrote: >>>> I wrote a general paster template for a Werkzeug app some time ago, >>>> but abandoned it when Flask came along. >>>> >>>> It might be easier to implement a template without paster - using >>>> Jinja2 for example to generate code. However I'm not sure how useful >>>> it would be, as Flask apps tend to vary so much and require so little >>>> code to get started with. >>> What I like about the tipfy project is that they have a form on the >>> website that you can fill out and it generates a tarball for a new >>> extension with a setup.py and everything. >>> >>> I think that might be interesting to have for both Flask projects and >>> Flask extensions. The flask-extension-wizard is okayish but not that >>> nice, especially because everybody misses it. >>> >>> >>> Regards, >>> Armin >> >> Two templates, first one for the extension, the second one for a flask app. >> >> It's the fourth time where I use flask and it's the same thing, >> define a setup.py, a readme, a license, a doc for Apache and WSGI, >> a frontend and the same modules. >> >> software-template is a dummy name and this software will be maintained by the team. >> >> software-template -t flask-extension -d my_flask_extension >> >> software-template -t flask-app -d my_flask_app >> >> Regards, >> >> Stéphane >>
I'm not sure. What might work is not so much a generic tool, but something like "Flask Recipes", i.e.different templates for different requirements. On 1 September 2010 13:21, Stephane Wirtel <stephane@wirtel.be> wrote: > I like your project, it's very useful. very specific but very useful. > > Do you believe we can create a a generic tool ? > > Regards, > > Stéphane > On 09/01/2010 02:17 PM, Dan Jacob wrote: >> I have one here http://bitbucket.org/danjac/flask-projectmaker but >> it's quite opinionated (e.g. includes certain extensions). It's really >> just for my own use but feel free to copy what you need. >> >> On 1 September 2010 13:14, Stephane Wirtel <stephane@wirtel.be> wrote: >>> On 09/01/2010 02:09 PM, Armin Ronacher wrote: >>>> Hi, >>>> >>>> On 2010-09-01 2:07 PM, Dan Jacob wrote: >>>>> I wrote a general paster template for a Werkzeug app some time ago, >>>>> but abandoned it when Flask came along. >>>>> >>>>> It might be easier to implement a template without paster - using >>>>> Jinja2 for example to generate code. However I'm not sure how useful >>>>> it would be, as Flask apps tend to vary so much and require so little >>>>> code to get started with. >>>> What I like about the tipfy project is that they have a form on the >>>> website that you can fill out and it generates a tarball for a new >>>> extension with a setup.py and everything. >>>> >>>> I think that might be interesting to have for both Flask projects and >>>> Flask extensions. The flask-extension-wizard is okayish but not that >>>> nice, especially because everybody misses it. >>>> >>>> >>>> Regards, >>>> Armin >>> >>> Two templates, first one for the extension, the second one for a flask app. >>> >>> It's the fourth time where I use flask and it's the same thing, >>> define a setup.py, a readme, a license, a doc for Apache and WSGI, >>> a frontend and the same modules. >>> >>> software-template is a dummy name and this software will be maintained by the team. >>> >>> software-template -t flask-extension -d my_flask_extension >>> >>> software-template -t flask-app -d my_flask_app >>> >>> Regards, >>> >>> Stéphane >>> > >
And don't forget flask-testing ;-)