the day before you specify a due date. I can imagine scenarios where this is
nice, but it is very counterintuitive to me. Trello also doesn't have webhooks
associated with due dates, so services like IFTTT or Zapier are unable to
accomplish the functionality I want: add todoist tasks from Trello on the day
they are due.
`trello-todoist` is a hack to add trello cards to todoist on the day that they
are due. It is intended to be set up as a cronjob with a crontab entry like:
```
53 3 * * * trello-todoist 'trello board' 'trello username' 'todoist project'
```
which runs `trello-todoist` every morning at 3:53 a.m. By default, this adds
all trello cards that are due today from board `trello board` of which `trello
username` is a member as a task to the corresponding `todoist project`.
Depending on the version of `requests` that is installed via python
dependencies, you may also want to use `PYTHONWARNINGS=ignore` somewhere in
your crontab to avoid being sent warnings every time the script is run.
## quick start
1. install `trello-todoist` from pypi:
```sh
pip install trello-todoist
```
1. get your trello api key and secret [from here](https://trello.com/app-key)
and get your oauth tokens:
```sh
export TRELLO_API_KEY=your-key
export TRELLO_API_SECRET=your-secret
export TRELLO_EXPIRATION=never
python -m trello.util
# follow instructions
```
1. get your todoist api token from the todoist `Settings` > `Account` > `API
token`.
1. place your trello credentials in a `trello.json` file in the repository root
that looks like this:
```json
{
"api_key": "your-key",
"api_secret": "your-secret",
"token": "your-oauth-token-key",
"token_secret": "your-oauth-token-secret"
}
```
1. place your todoist api token in a `todoist.json` file in the repository root
that looks like this:
```json
{
"token": "your-token"
}
```
1. :boom: For usage instructions, see
```sh
trello-todoist -h
```
## development
1. instantiate virtual environment
```sh
mkvirtualenv trello-todoist
pip install -r requirements/python-dev
```
1. follow the quick start instructions above to get your trello and todoist
credentials.
Metadata
Release files for trello-todoist 0.2.0
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 |
|---|---|---|---|---|
| trello-todoist-0.2.0.tar.gz | 4.8 kB | Without provenance | Details for trello-todoist-0.2.0.tar.gz |
Release files / trello-todoist-0.2.0.tar.gz
| Download URL | trello-todoist-0.2.0.tar.gz |
|---|---|
| Size | 4.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f83141e674609f79124d400a58acb140c7d15c7d5fefa089cb7e9cefb190706e
|
|
BLAKE2b-256 checksum How to use checksums |
9005f2db1222fc75b6138d7310d03af9cc67e29f99584b17bf873466f87badbe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for trello-todoist 0.2.0
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.