File: UPGRADING

package info (click to toggle)
pylons 1.0.1-3
  • links: PTS, VCS
  • area: main
  • in suites: jessie, jessie-kfreebsd
  • size: 4,224 kB
  • ctags: 1,124
  • sloc: python: 6,224; makefile: 90
file content (45 lines) | stat: -rw-r--r-- 1,892 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Upgrading your Pylons Project
=============================

Pylons projects should be updated using the paster command create. In addition
to creating new projects, paster create when run over an existing project will
provide several ways to update the project template to the latest version. 

Using this tool properly can make upgrading a fairly minor task. For the 
purpose of this document, the project being upgraded will be called 'demoapp'
and all commands will use that name.

Running paster create to upgrade
--------------------------------

You'll first need to cd to the directory *above* your projects main directory.
The main directory is the one that contains your setup.py, setup.cfg, and
development.ini files.

.. code:: bash
    /home/joe/demoapp $ cd ..
    /home/joe $

Then run paster create on the project directory:

.. code:: bash
    /home/joe $ paster create demoapp -t pylons

paster will prompt you on how to handle conflicts and updates to the existing
project files. The options let you (hit the key in the parens to perform the
operation):

(d)iff them, and show you the changes between your projects file and the one
   that has changed in Pylons
(b)ackup the file, and copy the new version into its place. The old one will 
   end in .bak
(y)es to overwrite the existing file with the new one. *Not recommended* since
   you will then have no way to see your existing one, unless you have seen
   the diff first and know there is no changes you're losing.
(n)o to overwrite, and just keep your existing file. Also safe if you know 
   that nothing has changed.

It's recommended when upgrading your project that you always look at the diff
first to see whats changed. Then either overwrite your existing one if you are
not going to lose changes you want, or backup yours and write the new one in.
You can then manually compare and add your changes back in.