Browsing Spanish translation

34.

Alternatively, you may also specify explicitly the PDF command to use to display PDF files in the OpenERP configuration file, normally located in your HOME directory, and named ``'.openerprc'``. Find the ``[printer]`` section and edit the ``softpath`` parameter. For example: ::

46.

For **other Linux distributions** and for those who prefer a **manual installation**, there are only two steps to deploy OpenERP under Linux: install PostgreSQL, the database engine used by OpenERP, then install OpenERP itself. These steps are described in the following sections:

63.

Make this new user a superuser. Only then you can create a database using OpenERP Client. In short, **openerp** is the new user created in PostgreSQL for OpenERP. This user is the owner of all the tables created by OpenERP Client.

98.

:guilabel:`reportlab` : The ReportLab Toolkit is the time-proven, ultra-robust, open-source engine for programmatically creating PDF documents and forms the foundation of RML. It also contains a library for creating platform-independent vector graphics. It is a fast, flexible, cross-platform solution written in Python. ::

117.

You can start the OpenERP server with the ``-s`` option to create a configuration file with default options, then modify it. The configuration parameters are similar to the server startup parameters, so have a look at the output of ``openerp -h`` if you're not sure what a given parameter does::

119.

The default OpenERP configuration file is located in ``$HOME/.openerp_serverrc``, that is a file named ``.openerp_serverrc`` in the home directory of the system user under which OpenERP runs. This is the default value for the ``-c`` startup parameter.

124.

OpenERP's release policy states that minor/patch releases of the stable versions are usually published every month. These are recommended for production deployment, as they include the latest security updates and bugfixes, and do not require any migration process.

129.

You can skip minor versions, for example, you do not need to install all the intermediary versions between 6.0.6 and 6.0.15 if you need to upgrade an outdated installation, as long as you stay in the same version line (6.0 in this example).

138.

Start the server manually (directly call the executable you located above), with the following additional parameters, to trigger an update of all module data and views in the database, based on the new source files (include your usual startup parameters, if any, and replace ``DB_NAME`` with the name of the OpenERP database you wish to update)::

139.

Let the server complete its startup (watch the log for the final message that says ``OpenERP server is running, waiting for connections`` or wait until you can connect to that database with a GTK client), then stop the server with :kbd:`Ctrl+C` and repeat the previous step for each database on this OpenERP installation (any database not updated will use the latest business logic but might have errors or missing improvements in the views until you update it using this procedure).