jordan

Not a problem, that's all done - thanks @jszwedko

We've been waiting for `option_layer` & `Either` to support services returning the same error to clean up some of the duplicate types/boxing in our server implementation, so many thanks for...

I suppose the implementation could be replaced with a `MapErr` on both sides of the `Either` so `option_layer` become something along the lines of: ```rust pub fn option_layer(layer: Option) ->...

Thanks for the report, an easy workaround could be using `CARGO_NET_GIT_FETCH_WITH_CLI` with `git` in the path pointing to a wrapper script calling `sshpass`

After a bit of experimentation, it looks like Cargo happily passes through `GIT_SSH_COMMAND` to the spawned command so that can be used instead of the wrapper script: ``` CARGO_NET_GIT_FETCH_WITH_CLI=true GIT_SSH_COMMAND="sshpass...

Actually, scratch all of that. [We expect the password to be in the username](https://github.com/w4/gitlab-cargo-shim/blob/bb203c01a9c931b6032978c0df751c51a85c584d/src/main.rs#L381) so modifications would be needed for the above. Maybe `.ssh/config` setting the `Username` to `gitlab-ci-token:$GITLAB-CI-TOKEN` for...

These days I'm thinking 'access tokens' like they're implemented in https://github.com/w4/gitlab-cargo-shim for CI could fit the bill

Hi, there's a flake included instead now: ```nix { inputs.paste-bin = { url = "github:w4/bin"; inputs.nixpkgs.follows = "nixpkgs"; }; outputs = { ... }: { nixosConfigurations.myBox = nixpkgs.lib.nixosSystem { modules...

No problem. If you're just using Nix imperatively you can use `nix run github:w4/bin`. I'd highly recommend checking out declarative flakes as it's the New Way(tm). It's a little bit...

That module is only for declarative usage of the service through your configuration.nix unfortunately. You'll have to pass the arguments manually like they're substituted into the systemd execstart ``` nix...