flask/examples/flaskr/README

                         / Flaskr /

                 a minimal blog application


    ~ What is Flaskr?

      A sqlite powered thumble blog application

    ~ How do I use it?

      1. edit the configuration in the flaskr.py file or
         export an FLASKR_SETTINGS environment variable
         pointing to a configuration file.

      2. install the app from the root of the project directory

         pip install --editable .

      3. Instruct flask to use the right application

         export FLASK_APP=flaskr.flaskr

      4. initialize the database with this command:

         flask initdb

      5. now you can run flaskr:

         flask run

         the application will greet you on
         http://localhost:5000/

    ~ Is it tested?

      You betcha.  Run `python setup.py test` to see
      the tests pass.
Removed useless imports and added README 15 years ago			`/ Flaskr /`

			`a minimal blog application`


Fixed a typo 15 years ago			`~ What is Flaskr?`
Removed useless imports and added README 15 years ago
			`A sqlite powered thumble blog application`

			`~ How do I use it?`

Ported examples over to new config. documented upgrading 15 years ago			`1. edit the configuration in the flaskr.py file or`
			`export an FLASKR_SETTINGS environment variable`
			`pointing to a configuration file.`
Removed useless imports and added README 15 years ago
Address #1902: Converts example/flaskr to have a setup.py (#1945) * Converts example/flaskr to have a setup.py Makes the flaskr app easier to run, ex. workflow: - pip install --editable . - export FLASK_APP=flaskr.flaskr - flask initdb - flask run Testing is also easier now: - python setup.py test * Fixed an import error in flaskr/tests - the statement `import flaskr` caused errors in python3 - `from . import flaskr` fixes the issue in 2.7.11 and 3.5.1 * Better project structure and updates the docs - Re-factors flaskr's project structure a bit - Updates docs to make sense with the new structure - Adds a new step about installing Flask apps with setuptools - Switches first-person style writing to second-person (reads better IMO) - Adds segments in testing.rst for running tests with setuptools * Remove __init__.py from tests - py.test recommends not using __init__.py * Fix testing import errors 8 years ago			`2. install the app from the root of the project directory`
Updated the examples to be cli based 11 years ago
Address #1902: Converts example/flaskr to have a setup.py (#1945) * Converts example/flaskr to have a setup.py Makes the flaskr app easier to run, ex. workflow: - pip install --editable . - export FLASK_APP=flaskr.flaskr - flask initdb - flask run Testing is also easier now: - python setup.py test * Fixed an import error in flaskr/tests - the statement `import flaskr` caused errors in python3 - `from . import flaskr` fixes the issue in 2.7.11 and 3.5.1 * Better project structure and updates the docs - Re-factors flaskr's project structure a bit - Updates docs to make sense with the new structure - Adds a new step about installing Flask apps with setuptools - Switches first-person style writing to second-person (reads better IMO) - Adds segments in testing.rst for running tests with setuptools * Remove __init__.py from tests - py.test recommends not using __init__.py * Fix testing import errors 8 years ago			`pip install --editable .`
Updated the examples to be cli based 11 years ago
Address #1902: Converts example/flaskr to have a setup.py (#1945) * Converts example/flaskr to have a setup.py Makes the flaskr app easier to run, ex. workflow: - pip install --editable . - export FLASK_APP=flaskr.flaskr - flask initdb - flask run Testing is also easier now: - python setup.py test * Fixed an import error in flaskr/tests - the statement `import flaskr` caused errors in python3 - `from . import flaskr` fixes the issue in 2.7.11 and 3.5.1 * Better project structure and updates the docs - Re-factors flaskr's project structure a bit - Updates docs to make sense with the new structure - Adds a new step about installing Flask apps with setuptools - Switches first-person style writing to second-person (reads better IMO) - Adds segments in testing.rst for running tests with setuptools * Remove __init__.py from tests - py.test recommends not using __init__.py * Fix testing import errors 8 years ago			`3. Instruct flask to use the right application`

			`export FLASK_APP=flaskr.flaskr`

			`4. initialize the database with this command:`
Updated the examples to be cli based 11 years ago
Update docs to the new CLI patterns 9 years ago			`flask initdb`

Address #1902: Converts example/flaskr to have a setup.py (#1945) * Converts example/flaskr to have a setup.py Makes the flaskr app easier to run, ex. workflow: - pip install --editable . - export FLASK_APP=flaskr.flaskr - flask initdb - flask run Testing is also easier now: - python setup.py test * Fixed an import error in flaskr/tests - the statement `import flaskr` caused errors in python3 - `from . import flaskr` fixes the issue in 2.7.11 and 3.5.1 * Better project structure and updates the docs - Re-factors flaskr's project structure a bit - Updates docs to make sense with the new structure - Adds a new step about installing Flask apps with setuptools - Switches first-person style writing to second-person (reads better IMO) - Adds segments in testing.rst for running tests with setuptools * Remove __init__.py from tests - py.test recommends not using __init__.py * Fix testing import errors 8 years ago			`5. now you can run flaskr:`
Update docs to the new CLI patterns 9 years ago
			`flask run`
Updated the examples to be cli based 11 years ago
			`the application will greet you on`
			`http://localhost:5000/`
docs: :file:`app.py`, :file:`yourapp/templates` 10 years ago
Removed useless imports and added README 15 years ago			`~ Is it tested?`

Address #1902: Converts example/flaskr to have a setup.py (#1945) * Converts example/flaskr to have a setup.py Makes the flaskr app easier to run, ex. workflow: - pip install --editable . - export FLASK_APP=flaskr.flaskr - flask initdb - flask run Testing is also easier now: - python setup.py test * Fixed an import error in flaskr/tests - the statement `import flaskr` caused errors in python3 - `from . import flaskr` fixes the issue in 2.7.11 and 3.5.1 * Better project structure and updates the docs - Re-factors flaskr's project structure a bit - Updates docs to make sense with the new structure - Adds a new step about installing Flask apps with setuptools - Switches first-person style writing to second-person (reads better IMO) - Adds segments in testing.rst for running tests with setuptools * Remove __init__.py from tests - py.test recommends not using __init__.py * Fix testing import errors 8 years ago			You betcha. Run `python setup.py test` to see
Removed useless imports and added README 15 years ago			`the tests pass.`