nixpkgs/pkgs/tools/misc/3llo/default.nix

{ lib, ruby_3_0, bundlerApp, fetchpatch }:

bundlerApp {
  pname = "3llo";
  ruby = ruby_3_0;

  gemdir  = ./.;

  exes = [ "3llo" ];

  meta = with lib; {
    description = "Trello interactive CLI on terminal";
    license = licenses.mit;
    homepage = "https://github.com/qcam/3llo";
    maintainers = with maintainers; [ ];
  };
}
3llo: 0.3.0 -> 1.3.1 2022-04-28 12:01:18 +00:00			`{ lib, ruby_3_0, bundlerApp, fetchpatch }:`
_3llo: init at 0.3.0 Simple CLI client for `trello.com`. It can be used like this: ``` $ export TRELLO_USER=your_username $ export TRELLO_KEY=your_key $ export TRELLO_TOKEN=your_token $ ./result/bin/3llo ``` I didn't create a module for this as I don't think that those secrets should live in the Nix store. Ideally `3llo` can be used from a script which retrieves secrets from some kind of password store like this: ``` export TRELLO_KEY=$(pass show trello/key) export TRELLO_TOKEN=$(pass show trello/token) 3llo $@ ``` 2019-07-25 11:38:50 +00:00
			`bundlerApp {`
			`pname = "3llo";`
3llo: 0.3.0 -> 1.3.1 2022-04-28 12:01:18 +00:00			`ruby = ruby_3_0;`
_3llo: init at 0.3.0 Simple CLI client for `trello.com`. It can be used like this: ``` $ export TRELLO_USER=your_username $ export TRELLO_KEY=your_key $ export TRELLO_TOKEN=your_token $ ./result/bin/3llo ``` I didn't create a module for this as I don't think that those secrets should live in the Nix store. Ideally `3llo` can be used from a script which retrieves secrets from some kind of password store like this: ``` export TRELLO_KEY=$(pass show trello/key) export TRELLO_TOKEN=$(pass show trello/token) 3llo $@ ``` 2019-07-25 11:38:50 +00:00
3llo: 0.3.0 -> 1.3.1 2022-04-28 12:01:18 +00:00			`gemdir = ./.;`
_3llo: init at 0.3.0 Simple CLI client for `trello.com`. It can be used like this: ``` $ export TRELLO_USER=your_username $ export TRELLO_KEY=your_key $ export TRELLO_TOKEN=your_token $ ./result/bin/3llo ``` I didn't create a module for this as I don't think that those secrets should live in the Nix store. Ideally `3llo` can be used from a script which retrieves secrets from some kind of password store like this: ``` export TRELLO_KEY=$(pass show trello/key) export TRELLO_TOKEN=$(pass show trello/token) 3llo $@ ``` 2019-07-25 11:38:50 +00:00
			`exes = [ "3llo" ];`

			`meta = with lib; {`
			`description = "Trello interactive CLI on terminal";`
			`license = licenses.mit;`
treewide: Per RFC45, remove all unquoted URLs 2020-04-01 01:11:51 +00:00			`homepage = "https://github.com/qcam/3llo";`
treewide: update which packages I'm currently maintaining Idea shamelessly stolen from 4e60b0efae56cc8e1a8a606a5a89462c38aba305. I realized that I don't really know anymore where I'm listed as maintainer and what I'm actually (co)-maintaining which means that I can't proactively take care of packages I officially maintain. As I don't have the time, energy and motivation to take care of stuff I was interested in 1 or 2 years ago (or packaged for someone else in the past), I decided that I make this explicit by removing myself from several packages and adding myself in some other stuff I'm now interested in. I've seen it several times now that people remove themselves from a package without removing the package if it's unmaintained after that which is why I figured that it's fine in my case as the affected pkgs are rather low-prio and were pretty easy to maintain. 2019-12-26 14:13:48 +00:00			`maintainers = with maintainers; [ ];`
_3llo: init at 0.3.0 Simple CLI client for `trello.com`. It can be used like this: ``` $ export TRELLO_USER=your_username $ export TRELLO_KEY=your_key $ export TRELLO_TOKEN=your_token $ ./result/bin/3llo ``` I didn't create a module for this as I don't think that those secrets should live in the Nix store. Ideally `3llo` can be used from a script which retrieves secrets from some kind of password store like this: ``` export TRELLO_KEY=$(pass show trello/key) export TRELLO_TOKEN=$(pass show trello/token) 3llo $@ ``` 2019-07-25 11:38:50 +00:00			`};`
			`}`