summaryrefslogtreecommitdiff
path: root/docs/quick_tour.rst
diff options
context:
space:
mode:
authorStephen Martin <lockwood@opperline.com>2018-09-17 13:49:04 -0700
committerStephen Martin <lockwood@opperline.com>2018-09-17 13:49:04 -0700
commit28e688f1a41215cb6167f8e53de017ddb82b552f (patch)
tree5059546f20ad72990e1fa1a66fa9bcff96d41daa /docs/quick_tour.rst
parentdfd0697dca6b0431b7d8398d93169c57be5b316b (diff)
downloadpyramid-28e688f1a41215cb6167f8e53de017ddb82b552f.tar.gz
pyramid-28e688f1a41215cb6167f8e53de017ddb82b552f.tar.bz2
pyramid-28e688f1a41215cb6167f8e53de017ddb82b552f.zip
name change
Diffstat (limited to 'docs/quick_tour.rst')
-rw-r--r--docs/quick_tour.rst14
1 files changed, 7 insertions, 7 deletions
diff --git a/docs/quick_tour.rst b/docs/quick_tour.rst
index af114d3a2..ce0fed275 100644
--- a/docs/quick_tour.rst
+++ b/docs/quick_tour.rst
@@ -506,17 +506,17 @@ First you'll need to install cookiecutter.
$VENV/bin/pip install cookiecutter
-Let's use the cookiecutter ``pyramid-cookiecutter-theonecc`` to create a starter Pyramid project in the current directory, entering values at the prompts as shown below for the following command.
+Let's use the cookiecutter ``pyramid-cookiecutter-starter`` to create a starter Pyramid project in the current directory, entering values at the prompts as shown below for the following command.
.. code-block:: bash
- $VENV/bin/cookiecutter gh:Pylons/pyramid-cookiecutter-theonecc --checkout master
+ $VENV/bin/cookiecutter gh:Pylons/pyramid-cookiecutter-starter --checkout master
If prompted for the first item, accept the default ``yes`` by hitting return.
.. code-block:: text
- You've cloned ~/.cookiecutters/pyramid-cookiecutter-theonecc before.
+ You've cloned ~/.cookiecutters/pyramid-cookiecutter-starter before.
Is it okay to delete and re-clone it? [yes]: yes
project_name [Pyramid Scaffold]: hello_world
repo_name [hello_world]: hello_world
@@ -646,7 +646,7 @@ and earlier we showed ``--reload`` for application reloading.
available in your browser. Adding it to your project illustrates several points
about configuration.
-Our cookiecutter ``pyramid-cookiecutter-theonecc`` already configured our package to include the
+Our cookiecutter ``pyramid-cookiecutter-starter`` already configured our package to include the
add-on ``pyramid_debugtoolbar`` in its ``setup.py``:
.. literalinclude:: quick_tour/package/setup.py
@@ -687,7 +687,7 @@ Yikes! We got this far and we haven't yet discussed tests. This is particularly
egregious, as Pyramid has had a deep commitment to full test coverage since
before its release.
-Our ``pyramid-cookiecutter-theonecc`` cookiecutter generated a ``tests.py`` module with
+Our ``pyramid-cookiecutter-starter`` cookiecutter generated a ``tests.py`` module with
one unit test and one functional test in it. It also configured ``setup.py`` with test requirements:
``py.test`` as the test runner, ``WebTest`` for running view tests, and the
``pytest-cov`` tool which yells at us for code that isn't tested:
@@ -863,13 +863,13 @@ Pyramid and SQLAlchemy are great friends. That friendship includes a cookiecutte
.. code-block:: bash
cd ~
- env/bin/cookiecutter gh:Pylons/pyramid-cookiecutter-theonecc --checkout master
+ env/bin/cookiecutter gh:Pylons/pyramid-cookiecutter-starter --checkout master
If prompted for the first item, accept the default ``yes`` by hitting return.
.. code-block:: text
- You've cloned ~/.cookiecutters/pyramid-cookiecutter-theonecc before.
+ You've cloned ~/.cookiecutters/pyramid-cookiecutter-starter before.
Is it okay to delete and re-clone it? [yes]: yes
project_name [Pyramid Scaffold]: sqla_demo
repo_name [sqla_demo]: sqla_demo