1). Very, very, very minimalistic SQLAlchemy models made (Series and Chapter). The goal isn't to be comprehensive. Rather, it's meant to be a functional starting point so that other parts of the app can be worked on (e.g. API, auth) and toyed with tangible examples.
2). Refactored views.py -- namely, split up the application startup code to app.py. The actual views were moved to views/home.py for cleanliness. In addition, the directories for admin, api, and epub were moved into views as well (since these are technically views). Epub directory should probably be deleted because that should be an entirely separate app of its own.
3). config.py -- added because a lot of tutorials I checked had this. app.config.from_object() seems a lot more succinct to me, but it's a stylistic thing. I don't think we should have both a setup.json and a config.py.
4). README has instructions how to setup SQLAlchemy (dev with sqlite for now)
1). Very, very, very minimalistic SQLAlchemy models made (Series and Chapter). The goal isn't to be comprehensive. Rather, it's meant to be a functional starting point so that other parts of the app can be worked on (e.g. API, auth) and toyed with tangible examples.
2). Refactored views.py -- namely, split up the application startup code to app.py. The actual views were moved to views/home.py for cleanliness. In addition, the directories for admin, api, and epub were moved into views as well (since these are technically views). Epub directory should probably be deleted because that should be an entirely separate app of its own.
3). config.py -- added because a lot of tutorials I checked had this. app.config.from_object() seems a lot more succinct to me, but it's a stylistic thing. I don't think we should have both a setup.json and a config.py.
4). README has instructions how to setup SQLAlchemy (dev with sqlite for now)