modify architecture to make starting a custom site easy

[peta15]

handler file has become large and should be split into an 'auth_handlers' file and a handlers file where users can add their own handlers for their own custom needs.

models file should be renamed 'auth_models' and another models file should be created for users to add their own models for uses other than authentication.

also style.css should really be renamed to html5bp.css to reflect that it is html5bp css library.

we should add to the docs the names of common files for users to start working with for custom sites: main.css, script.js, models.py, handlers.py.

[coto]

agree with you, even we should create a folder gae-boilerplate with everything, and outside people can create their websites.... IMO

[peta15]

that's also a good idea. i'm not sure which is better so i'll let you make the call. certainly it is important that users of the boilerplate can easily merge in updates and whichever makes this easiest should probably be the route we take.

On Tue, Jul 31, 2012 at 9:50 PM, Rodrigo Augosto < reply@reply.github.com

wrote:

agree with you, even we should create a folder gae-boilerplate with everything, and outside people can create their websites.... IMO

---

Reply to this email directly or view it on GitHub: https://github.com/coto/gae-boilerplate/issues/106#issuecomment-7416223

[mooose]

How about using a dir apptemplate and putting main.py config.py routes.py and app.yaml into this dir and deleting it from the main dir. Inserting a new target app into the Makefile and creating the app by using: $ make app

This way to start the boilerplate demo someone has just to use "make app" and the boilerplate is ready and from there all these files can be customized for the new project.

in the Makefile:

APPTEMPLATE=$(wildcard apptemplate/.py \ apptemplate/.yaml \ )

app: $(APPTEMPLATE) cp $(APPTEMPLATE) .

[coto]

Yes, that's the idea!!!