Go to file
Albert Cervera i Areny 359c518d53 Add new aeat reports. 2013-06-17 09:19:44 +02:00
utils Add utils directory with some scrits for helpping to take the rtyton repositories list 2012-12-26 09:19:17 +01:00
.hgignore [#8540] Add the hgingore file and remove the old gitignore 2013-03-30 10:58:03 +01:00
INSTALL Update buildout config adding some auto-checkout modules 2013-04-08 21:06:58 +02:00
README.rst move base repositories to base.cfg configuration file 2013-05-09 16:57:40 +02:00
VIRTUALENV update VIRTUALENV configuration 2013-03-30 00:39:25 +01:00
base.cfg Removed invalid 'sources-dir' in base.cfg and check virtualenv or root before try to install packages 2013-06-03 13:59:11 +02:00
bootstrap.py [#8541] Remove the symlink dependency and work on trytond/trytond/modules directly 2013-03-30 00:40:54 +01:00
buildout.cfg move base repositories to base.cfg configuration file 2013-05-09 16:57:40 +02:00
core.cfg Add new 2.8 core modules. 2013-04-02 14:05:25 +02:00
create-doc-symlinks.sh Don't put trytond-doc in 'modules' directory: updated userdoc.cfg and create-doc-symlinks.sh 2013-05-07 10:56:51 +02:00
local.cfg Add some modifications 2012-12-16 15:38:45 +01:00
nan-tic.cfg Add new aeat reports. 2013-06-17 09:19:44 +02:00
nereid.cfg Update nereid name after hg clone 2013-04-08 21:15:18 +02:00
requirements.txt requirements.txt: added buildout with pinned version 2013-05-31 21:16:20 +00:00
third-party.cfg Remove Zikzakmedia crm-related modules. 2013-05-21 08:43:18 +02:00
tryton-bootstrap.py Removed invalid 'sources-dir' in base.cfg and check virtualenv or root before try to install packages 2013-06-03 13:59:11 +02:00
trytonspain.cfg Add account_payment_type_move module. 2013-05-04 13:45:16 +02:00
userdoc.cfg improved buildout config files 2013-06-03 11:12:54 +02:00

README.rst

tryton-buildout
===============

This project supplies Buildout configuration files and some scripts to prepare
and mantain an instance of Tryton **based on repository sources** (by default,
development branches), providing facilities to manage large amount of source
repositories and different VCS (git, hg...).

Currently, it is not integrated with Virtualenv. It doesn't install required
libraries, it uses Python and libraries of the system.

It **install trytond and put the module sources in the trytond/modules
subdirectory**. Then, you have to launch *trytond* from corresponding
subdirectory and using the script in *bin*, to use the local/project *trytond*
and modules.

It also **requires an specific directory organization**:

* **PROJECT_DIRECTORY**: main directory. All sources and files are insite it.
  Typically, it is a repository.

  * **tryton-buildout**: clone of this repository. If main repository is also a
    *git* repo, you can define it as a submodule.
  * **trytond**: clone of *trytond* project repository. It is get automatically
    by buidlout.
  * **tryton**: clone of *tryton* project repository. It is get automatically
    by buildout.
  * **userdoc**: if you generate the Dynamic User's Manual (independent
    buildout configuration) it is created automatically.
  * **local.cfg**: Buildout configuration file with project specific modules
    and configurations. In *tryton-buildout* directory there is already a
    symlink to this file.


Prepare a Tryton instance
-------------------------

To prepare an instance of Tryton based on this project you can follow the next
commands (here is not included commands to set the PROJECT_DIRECTORY as a VCS
repository):

#. mkdir PROJECT_DIRECTORY
#. cd PROJECT_DIRECTORY
#. vi local.cfg::

    [buildout]
    auto-checkout += *
    parts =

    [sources]

#. git clone https://bitbucket.org/trytonspain/tryton-buildout.git
#. cd tryton-buildout
#. pip install -r requirements.txt
#. python bootstrap.py
#. ./build/bin/buildout -c base.cfg
#. ./build/bin/buildout -c buildout.cfg
#. ./create-symlinks.sh


Now, you can **launch the Tryton server** in two ways:

* with **supervisor**:::

  #. cd PROJECT_DIRECTORY/tryton-buildout
  #. ./build/bin/supervisord

* directly from sources:::

  #. cd PROJECT_DIRECTORY/trytond
  #. ./bin/trytond


To **launch the Tryton client (GTK)** do it from sources:::

  #. cd PROJECT_DIRECTORY/tryton
  #. ./bin/tryton


Prepare to generate User documentation
--------------------------------------

You will need the sources of Tryton server and modules because User
documentation sources are there. So, you need to do the previous step except
launch the Tryton server nor client.

After that, you can follow the next commands from 'tryton-buildout' directory:

#. ./build/bin/buildout -c userdoc.cfg
#. ./create-doc-symlinks.sh
#. cd ../userdoc
#. pip install -r requirements.txt
#. make

Now, you can point your navigator to *userdoc/_build/html/index.html* to view
the auto-generated **Users and Administrators manual**.

For more information about *userdoc*, see the README file of `tryton-doc
project`_ (you will find its sources in *trytond/trytond/modules/tryton-doc*
directory).

.. _tryton-doc project: https://bitbucket.org/trytonspain/trytond-doc