https://github.com/python-bonobo/bonobo-devkit
A «meta» repository to work on bonobo.
https://github.com/python-bonobo/bonobo-devkit
bonobo so-meta
Last synced: 15 days ago
JSON representation
A «meta» repository to work on bonobo.
- Host: GitHub
- URL: https://github.com/python-bonobo/bonobo-devkit
- Owner: python-bonobo
- License: apache-2.0
- Created: 2017-05-05T06:59:45.000Z (about 8 years ago)
- Default Branch: master
- Last Pushed: 2025-04-26T18:29:45.000Z (24 days ago)
- Last Synced: 2025-04-26T19:31:31.849Z (24 days ago)
- Topics: bonobo, so-meta
- Language: Python
- Homepage: https://www.bonobo-project.org/
- Size: 55.7 KB
- Stars: 5
- Watchers: 1
- Forks: 4
- Open Issues: 15
-
Metadata Files:
- Readme: README.rst
- License: LICENSE
Awesome Lists containing this project
README
bonobo-devkit
=============
THIS REPOSITORY HELPS TO WORK ON THE BONOBO SOURCE CODE OR FUTURE VERSIONS OF BONOBO, IF YOU JUST WANT TO USE STABLE
VERSION AND WRITE ETL JOBS, LOOK AT https://www.bonobo-project.org/getting-started INSTEAD.
.. image:: https://travis-ci.org/python-bonobo/bonobo-devkit.svg?branch=master
:target: https://travis-ci.org/python-bonobo/bonobo-devkit
You may need this repository if:
* You want to submit patches to the bonobo core, or etensions.
* You want to try the future versions of bonobo.
Requirements
::::::::::::
* `virtualenv`, and at least one of `python3.5`, `python3.6` and `python3.7` should be accessible from path.
* Github access using ssl should be possible. You don't need r/w access to bonobo repository, but your ssh key should
allow some access to github so it can use ssh+git urls.
Setup
:::::
* Setup your github username in git config if not done yet: `git config --global github.user hartym`
* Run `make` (will create two virtualenv, clone the needed repositories, setup the correct remotes and install all
packages as editable in both virtualenvs).
Once this is done, a helper script is available in `bin/bdk` to work on multiple repositories at once:
* `bin/bdk init`: lightweight fetch used by `make install` to do the initial setup.
* `bin/bdk fetch`: will fetch all new objects from git remotes (both upstream and origin, and more if you setup more).
* `bin/bdk branch`: show which branch each repository is pointing at.
* `bin/bdk status`: show a `git status` like output on all repositories to have a quick overview of changes.
Tracked repositories are configured in `config.yml`, and optionnaly extended/overriden by `config.local.yml`. The file
content is parsed using jinja2, then should be valid yaml. Local version will extend yaml lists and the dicts will be
merged "deeply", so you can add new repositories, new remotes, or override a value in the local file.
Working
:::::::
`source activate3.5` or `source activate3.6` to activate a given virtualenv in your current shell.