todo. We will begin with a barebones template using the
cement generatetool, and build up from there to cover as much of the core features of the framework as possible.
cementthat includes tools to make our lives easier. This was introduced in Cement 3, and will continue to grow as feature requests are made for new and improved ways of streamlining the development process.
README.mdis populated with some starter info to help get more familiar with the layout and navigation of the project. You should read the
requirements.txtlists dependencies that are strictly required for deployment (production), where the additional
requirements-dev.txtincludes additional dependencies that are only required for development (running tests, building documentation, etc).
Dockerfilegives you a working Docker image out-of-the box, while the
Makefileincludes several helpers for common development tasks such as creating a virtualenv, running tests, building docker, etc.
config/todo.yml.exampleshould be updated to reflect them.
todo, with what should be an obvious breakdown of submodules that clearly separate code into relevant and organized buckets. Take a moment to briefly review all of the files provided in the generated project repository.
Makefilewith several helpers to streamline the development process. You can use these helpers, add your own, or do away with it and follow any other development process you are more familiar with.
./env/, and then runs
pipto install our dependencies. We activate the environment, and are ready to run our TODO application: