| | |
| | | Previously (in Pyramid 1.0, 1.1 and 1.2), you created a Pyramid application |
| | | using ``paster create``, like so:: |
| | | |
| | | $myvenv/bin/paster create -t pyramid_starter foo |
| | | $ myvenv/bin/paster create -t pyramid_starter foo |
| | | |
| | | You're now instead required to create an application using ``pcreate`` like |
| | | so:: |
| | | |
| | | $myvenv/bin/pcreate -s starter foo |
| | | $ myvenv/bin/pcreate -s starter foo |
| | | |
| | | Note that the names of available scaffolds have changed the and flags |
| | | Note that the names of available scaffolds have changed and the flags |
| | | supported by ``pcreate`` are different than those that were supported by |
| | | ``paster create``. |
| | | |
| | |
| | | exist under the respective console script names ``pshell``, ``pviews``, and |
| | | ``ptweens``. |
| | | |
| | | We've replaced use of the Paste http server with the ``wsgiref`` server in |
| | | We've replaced use of the Paste ``httpserver`` with the ``wsgiref`` server in |
| | | the scaffolds, so once you create a project from a scaffold, its |
| | | ``development.ini`` and ``production.ini`` will have the following line:: |
| | | |
| | | use = egg:pyramid#wsgref |
| | | use = egg:pyramid#wsgiref |
| | | |
| | | Instead of this (which was the default in older versions):: |
| | | |
| | |
| | | Using ``wsgiref`` as the default WSGI server is purely a default to make it |
| | | possible to use the same scaffolding under Python 2 and Python 3; people |
| | | running Pyramid under Python 2 can still manually install ``Paste`` and use |
| | | the Paste httpserver by replacing the former line with the latter. This is |
| | | the Paste ``httpserver`` by replacing the former line with the latter. This is |
| | | actually recommended if you rely on proxying from Apache or Nginx to a |
| | | ``pserve`` -invoked application. **The wsgiref server is not a production |
| | | quality server.** See :ref:`alternate_wsgi_server` for more information. |