Acanban
Acanban is an academic Kanban board. It aims to provide a collaboration platform for students and mentors, with first-class support for academic evaluation.
Prerequisites
Acanban runs on Python 3.7+ and requires RethinkDB and IPFS 0.7 or above.
Setup
The development version of Acanban can be installed from this git repository:
python -m pip install git+https://github.com/Huy-Ngo/acanban
Acanban can then be evoked via python -m acanban. In production,
it is typical to run it as a systemd service, configured like followed.
[Unit]
Description=The Acanban Server
After=network.target
[Service]
ExecStart=/path/to/venv/bin/python -m acanban
Restart=on-failure
[Install]
WantedBy=default.target
Configuration
Acanban's configuration files are looked for
in user and site config dir (in that order),
with acanban namespace.
With third-party configuration separated to dedicated files,
acanban.toml may define the following keys:
# Used for HTTP to HTTPS redirection if defined
domain = 'example.com'
Hypercorn
Hypercorn configuration is loaded from hypercorn.toml.
Acanban does not override any of the server's defaults.
RethinkDB
Values defined in rethinkdb.toml will be passed to the RethinkDB client.
Below are some of the fields that commonly need to be configured
and their default values:
host = 'localhost'
port = 28015
user = 'admin'
timeout = 20
db = 'test'
IPFS
Custom ipfs.toml must define the following keys,
whose default values are listed as follows:
[api]
base = 'http://127.0.0.1:5001/api/v0'
[gateway]
base = 'http://127.0.0.1:8080/ipfs'
fallback = 'https://ipfs.io'
Hacking
First clone the repository and install Acanban as editable:
git clone https://github.com/Huy-Ngo/acanban
cd acanban
python -m pip install flit
flit install --symlink
After playing around with the source code, one can use tox
to test the modified version:
python -m pip install tox
tox
Metadata
Release files for acanban 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| acanban-0.1.3.tar.gz | 58.8 kB | Without provenance | Details for acanban-0.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| acanban-0.1.3-py3-none-any.whl | Python 3 | none | any | Details for acanban-0.1.3-py3-none-any.whl |
Total release size: 148.7 kB
Release files / acanban-0.1.3.tar.gz
| Download URL | acanban-0.1.3.tar.gz |
|---|---|
| Size | 58.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ed13a35683761793c09c9d94edf79b44c80b8b3ef19c5e408decd8e427bd2daa
|
|
BLAKE2b-256 checksum How to use checksums |
d71ac61223d82f5dbbce3a951d17d7fcb0e13829aff670ef59aa8b2745db8b00
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/3.7.3 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/3.7.3
|
Release files / acanban-0.1.3-py3-none-any.whl
| Download URL | acanban-0.1.3-py3-none-any.whl |
|---|---|
| Size | 89.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2d720d4ec312c15bb52e9b5d74deb1a31073d29c4da8e342f369b14deb6b0e9c
|
|
BLAKE2b-256 checksum How to use checksums |
e3d87c8761dd4219096137bb2472f741b0ef8d5bd2470c114dc23f105766642b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/3.7.3 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/3.7.3
|
Security for acanban 0.1.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.