paulin/bonobo
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Refactoring API, writing docs.

Browse Source
This commit is contained in:
Romain Dorgueil
2017-12-27 11:32:47 +01:00
parent 018289dad6
commit 46a8fd192e
12 changed files with 91 additions and 91 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/tutorial/5-packaging.rst
View File

@ -1,7 +1,20 @@
Part 5: Projects and Packaging
==============================
Until then, we worked with one file managing a job. But real life is about set of jobs working together within a project.
Until then, we worked with one file managing a job.
Real life often involves more complicated setups, with relations and imports between different files.
This section will describe the options available to move this file into a package, either a new one or something
that already exists in your own project.
Data processing is something a wide variety of tools may want to include, and thus |bonobo| does not enforce any
kind of project structure, as the targert structure will be dicated by the hosting project. For example, a `pipelines`
sub-package would perfectly fit a django or flask project, or even a regular package, but it's up to you to chose the
structure of your project.
about using |bonobo| in a pyt
is about set of jobs working together within a project.
Let's see how to move from the current status to a package.