Ability to configure API URL on a per-project basis

[muety]

A user of Wakapi has expressed a wish for being able to configure the API URL on a per-project basis to use WakaTime alongside, for instance, a self-hosted Wakapi in parallel. Some projects could be tracked in one service and some in another. Suggestions was to have something analogously to the .wakatime-project file in a project's folder.

I know that this would be quite a non-trivial change, so I'd like to ask you whether you even consider this an option for WakaTime CLI.

[muety]

Wakapi already supports forwarding heartbeats to WakaTime. However, "splitting" them per project is not an option right now. Let's move this discussion out of here, though, as we're getting out of scope of wakatime-cli.

[karolzlot]

@muety

Ok, moved.

[alanhamlett]

Closing now that conversion is at muety/wakapi#82 (comment)

[karolzlot]

@alanhamlett
This issue is about configuring backend per project.
Please reopen if this could be possible in wakatime-cli.

[alanhamlett]

It's possible, but I don't think it's likely to be implemented. It makes more sense to use the existing duplication so both local and cloud show the same total time instead of having a fragmented picture of the day.

[karolzlot]

@alanhamlett Ok, I agree with this argument.