Skip to main content

Gammadia's tipee backend for Taxi

This is the Taxi backend for Gammadia's 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://gammadia.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

With Nix installed (the flake provides Python and the release tools):

./release.sh 1.0.10

It bumps the version, builds and checks the distributions, then commits, tags and pushes. The tag triggers the release GitHub Actions workflow, which publishes to PyPI as a trusted publisher, so no API token is needed.

Metadata

Release files for taxi-tipee 1.0.10

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.10
File Size Uploaded
taxi_tipee-1.0.10.tar.gz 4.9 kB Details

Built distribution (wheel)

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

Total release size: 10.4 kB

Release files / taxi_tipee-1.0.10.tar.gz

Download URL taxi_tipee-1.0.10.tar.gz
Size 4.9 kB
Tags Source
SHA-256 checksum
How to use checksums
77442a8027bc7b03a18615c0a07f2e1974c5e9d493ed17f7cf4629b5815d5627
BLAKE2b-256 checksum
How to use checksums
5b20882e29e169f2e227c1bcd200020a5f37e801be9ae26b1017e2e07f976203
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.10-py3-none-any.whl

Download URL taxi_tipee-1.0.10-py3-none-any.whl
Size 5.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d573a096f1153a4f848c14f4b7df9eb63a6147808bc03bce40d431d8b0eb51e3
BLAKE2b-256 checksum
How to use checksums
a6e0dc6e2d9dceadd09203ea6258fb718ea18c1045a6063198c99cd31c557786
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.10 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