Shikanime Deva

@bertwin Yes, I thought about this a while ago too, but it would require a lot of unusual things, such as changes to the revset, named options or the ordering...

It's simply an edge case of flake. Devenv needs to know the current directory (aka PWD) in order to set up the tools, cache, and other configuration files.

No guarantee, but I may work on an implementation in the near future, as I would like to be able to share TCP and HTTP traffic under the same endpoint...

Just a quick update: I have tried to implement the Gateway API in the Tailscale Operator. However, cleanly synchronising the XXXRoute, the Gateway, and the different CRDs using the current...

Here's a quick and dirty MVP: https://github.com/shikanime/tailscale-gateway. It could certainly be improved, but hear me out: there are several upstream issues that need to be addressed. For example, see https://github.com/tailscale/tailscale/issues/17754....

OK, never mind. I've found the `tsnet` package. I'll re-implement the different Gateway API features in a clean single image custom proxy designed specifically for that purpose.

## `nixpkgs-review` result Generated using [`nixpkgs-review`](https://github.com/Mic92/nixpkgs-review). Command: `nixpkgs-review pr 459586` Commit: `52d6e944334fdd2db4b23582db2a6d8812869efc` --- ### `aarch64-darwin` :white_check_mark: 2 packages built: sapling sapling.dist

## `nixpkgs-review` result Generated using [`nixpkgs-review`](https://github.com/Mic92/nixpkgs-review). Command: `nixpkgs-review pr 459586` Commit: `52d6e944334fdd2db4b23582db2a6d8812869efc` --- ### `x86_64-linux` :white_check_mark: 2 packages built: sapling sapling.dist

@pbar1 @thoughtpolice Hello, would it be possible to review this pull request? Thank you! 💜

## `nixpkgs-review` result Generated using [`nixpkgs-review`](https://github.com/Mic92/nixpkgs-review). Command: `nixpkgs-review pr 459586` Commit: `9360baba2a2136f55b66164dc932d5d134b49dc5` --- ### `x86_64-linux` :white_check_mark: 2 packages built: sapling sapling.dist