Skip to main content

tipee backend for Taxi

This is the Taxi backend for tipee. It exposes the tipee protocol to push entries as timechecks.

Installation

taxi plugin install tipee

Configuration

Run taxi config and use the tipee protocol for your backend :

[backends]
my_tipee_backend = tipee://[app_name]:[app_private_key]@[instance].tipee.net/api/?person=[person_id]

[taxi]
regroup_entries = false
  • [app_name] and [app_private_key] can be found in tipee's PHP configuration files, like $_CONFIG['PrivateKey']['timbreuse'] = 'fK19psLpm17u660fCiJ5s569bfeij2s800y'; for example, so here you would use timbreuse:fK19psLpm17u660fCiJ5s569bfeij2s800y
  • [instance] is tipee's instance name
  • [person_id] is the ID of your user, which can be found in the URL when editing your profile, like https://[instance].tipee.net/person/#/169

There is an extra scheme=http query string argument that can be useful when developing (using localhost:port as the hostname).

Usage

You can now add timesheet entries like :

19/05/2020 # Tuesday
tipee    08:00-09:00    Monitoring server
tipee         -10:30    Fixing bug
tipee         -?        Work in progress...

Things you should know

Duration as hours is not supported

As stated in Taxi's documentation :

duration can either be a time range or a duration in hours. If it’s a time range, it should be in the format start-end, where start can be left blank if the previous entry also used a time range and had a time defined, and end can be ? if the end time is not known yet, leading to the entry being ignored. Each part of the range should have the format HH:mm, or HHmm. If duration is a duration, it should just be a number, eg. 2 for 2 hours, or 1.75 for 1 hour and 45 minutes.

However, tipee requires timechecks to have specific time start and end, so a proper error will be thrown if you do not provide a time range.

Regrouping entries is not supported

By default, Taxi regroups entries to commit them. So if you have 3 different entries on a day with the same alias and description, it will push only one entry with the cumulated times. In tipee, this leads to timesheets overlapping each others, which are explicitly prohibited. So you need to set the option to false :

[taxi]
regroup_entries = false

Releasing

Publish a GitHub release with a new tag named after the version (like 1.0.11), from the web interface or with:

gh release create 1.0.11 --generate-notes

The release GitHub Actions workflow builds the package (the version comes from the tag, through setuptools-scm), publishes it to PyPI as a trusted publisher, so no API token is needed, and attaches the files to the release.

To build locally, nix develop (or direnv) provides Python and the tools: python -m build --no-isolation.

Metadata

Release files for taxi-tipee 1.0.11

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for taxi-tipee 1.0.11
File Size Uploaded
taxi_tipee-1.0.11.tar.gz 5.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for taxi-tipee 1.0.11
File Interpreter ABI Platform
taxi_tipee-1.0.11-py3-none-any.whl Python 3 none any Details

Total release size: 10.8 kB

Release files / taxi_tipee-1.0.11.tar.gz

Download URL taxi_tipee-1.0.11.tar.gz
Size 5.2 kB
Tags Source
SHA-256 checksum
How to use checksums
245d7a00082f6611188fed0be05588e242a882ef98acdf692b763b3f99859908
BLAKE2b-256 checksum
How to use checksums
40aea1797aba7e21c23df23dae76387a4411dbb5ae68d20ac6f33693e5c64c21
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 2, 2026.

Transparency log

Release files / taxi_tipee-1.0.11-py3-none-any.whl

Download URL taxi_tipee-1.0.11-py3-none-any.whl
Size 5.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d69fde5a9e712a7787bec576c90d82a7375adff136e6b3d8d7556b6a15fc28bf
BLAKE2b-256 checksum
How to use checksums
b04bdd8233be60b50230657a8b27cdbb77feebc78da58cf320ec428e657c90b5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 2, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.0.11 This release

2 release files

1.0.9

1 release file

1.0.8

1 release file

1.0.7

1 release file

1.0.6

1 release file

1.0.5

1 release file

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page