Apycot_ is an Automated Python Code Testing platform built on narval_ and cubicweb_.
.. _Apycot: http://www.cubicweb.org/project/apycot .. _narval: http://www.cubicweb.org/project/narval .. _cubicweb: http://www.cubicweb.org/project/cubicweb
Installation and configuration
Apycot_ is based on narval_, so make sure you have a working narval_
setup. Please refer to narval's documentation for help on installing a
narval setup.
Once you have a properly functionning narval setup, you have to
install Apycot elements on both the website part and the narval-bot
side.
On the web/data server host
---------------------------
* Install the `cubicweb-apycot` package (more info in the
`cubicweb book`_).
* Modify password for the narval user for better security.
On the bot host
---------------
* Install the `narval-apycot` package.
* Edit `/etc/narval/narval.ini`, is neccessary (or `~/etc/narval.ini`
when running code from hg) to adjust the bot configuration. You can
also generate a stub configuration file using `narval rcfile >
/etc/narval/narval.ini`.
* Indicate the connection informations for each instance in the
`/etc/narval/narval-cw-sources.ini` file (makesure this file is not
world readable), for instance::
[cwo]
url=https://www.cubicweb.org/
token_id=The Token Name
secret=<generated secret>
[elo]
url=https://www.logilab.org/
token_id=The Other Token Name
secret=<generated secret>
where each section is the configuration for a cubicweb
application.
* For those running from source, `narval/bin/narval` **must** be in
`PATH` (since the `narval` daemon spawns subprocess via the `narval`
command).
.. _`cubicweb book`: http://www.cubicweb.org/
You may check the bot can connect to the cubicweb instances by
watching the narval bot's logs (usually in `/var/log/narval/`).
More documentation
``````````````````
Beside low-level installation (described here), all the documentation to setup your
continuous integration environment is available online through your instance at
`http://<your instance url>/doc/apycot`
You should read this documentation in order to be able to create all
the required objects to build your own testing and continuous
integration platform.
Feedbacks, bug reports
``````````````````````
Comments and bug reports are welcome on the
python-projects@list.logilab.org mailing-list.
FAQs
Continuous testing / integration tool for the CubicWeb framework
We found that apycot demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.
Security News
Research
Socket researchers found a malicious Maven package impersonating the legitimate ‘XZ for Java’ library, introducing a backdoor for remote code execution.