herms alternatives and similar packages
Based on the "CLI" category.
Alternatively, view herms alternatives based on common mentions on social networks and blogs.
unused9.9 1.0 herms VS unusedA command line tool to identify unused code.
cli7.4 0.0 herms VS cliCommand Line Interface Utility (Printing, Formatting, Options parsing) for Haskell
harg7.1 0.0 herms VS hargHaskell program configuration using higher kinded data
otp-authenticator5.0 0.0 herms VS otp-authenticatorOTP Authenticator (ala Google Authenticator) cli app
ploton3.6 0.0 herms VS plotonA useful cli tool to draw figures
rob3.4 0.0 herms VS robPersonal projects generator written in haskell
gli2.5 0.0 herms VS glitiny git"lab/hub" cli wrapper
translate-cli2.1 0.0 herms VS translate-cliCommand Line Interface to translate words
file-templates1.8 0.0 herms VS file-templatesUse templates for files and directories
platinum-parsing1.5 0.0 herms VS platinum-parsingAll-around tools for compilation development
gen-passwd1.2 0.0 herms VS gen-passwdGenerate a wordlist-based password easily
optparse-applicative-simpleSimple command line interface arguments parser
morpheus-graphql-cliMorpheus GraphQL CLI
Static code analysis for 29 languages.
Do you think we are missing an alternative of herms or a related project?
HeRM's: a Haskell-based Recipe Manager (yes, food recipes) for the command line.
Table of Contents
- Add recipes! :)
- Look at recipes! :D
- Edit recipes! :DD
- Serving size adjustment! :DDD
- Remove recipes :(
- View metric recipes in imperial units and vice-versa
- Import and export recipes as JSON or YAML
- Generate shopping lists
- Keep track of recipes with tags
- Set default unit systems, serving sizes, language, and recipe (see the section on configuration)
Version v2.0 is out! This is the first release for which pre-built binaries are available to download on Github. There were many, many great changes in 2.0, so thanks to everyone for the contributions!
See [the changelog](./CHANGELOG.md) for more details.
- Español (Spanish)
- Français (French)
Herms is very actively maintained and welcomes new contributions, whether in code, issues, documentation, translations, or feature suggestions!
Please see [Contributing.md](./Contributing.md) for more information.
At the moment, Herm's can only be installed via stack or cabal, but standalone binaries are in the works!
If you're interested developing/hacking Herm's instead of just using it, see [Contributing.md](./Contributing.md) instead.
stack update stack install herms
Manually cloning and installing from source with Stack
git clone https://github.com/JackKiefer/herms cd herms stack update stack install
Via Hackage and Cabal
Note: Your mileage may vary with dependency resolution
cabal update cabal install herms
Manually with Cabal
git clone https://github.com/JackKiefer/herms cd herms cabal update cabal install
Manually with Nix
Herm's has a command-line interface!
Below is the exhaustive list of all commands and their functionalities. Take a gander!
Usage: herms [-v|--version] COMMAND HeRM's: a Haskell-based Recipe Manager. Type "herms --help" for options Available options: -h,--help Show this help text -v,--version Show version Available commands: list list recipes view view the particular recipes add add a new recipe (interactively) edit edit a recipe import import a recipe file export export recipes to stdout remove remove the particular recipes shopping generate a shopping list for given recipes datadir show locations of recipe and config files find find all matching strings within recipe book (supports extended regex)
Configuring Herm's and managing recipe files
Herm's stores files in the following locations:
The configuration file,
config.hsin the XDG configuration directory, typically
~/.config/hermson most Linux systems
The recipes file,
recipes.yamlin the XDG data directory, typically
~/.local/share/hermson most Linux systems
To see where these are stored on your system, run
config.hs is a pseudo-Haskell-source-code file with several options for
configuring the behaviour of Herm's. It currently supports the following
defaultUnit: The default unit system to show recipes in. Options:
None. Setting to
Nonewill simply show recipes in whatever unit system they're stored in.
defaultServingSize: Default serving size to calculate when showing recipes. Can be any non-negative integer; set to
0for no default. This can be useful when you're always cooking for the same number of people!
recipesFile: The recipes file to use. This option currently supports relative (but not absolute) location, as well; if your data directory is
~/herms/data, for example, and you want a recipe file in your home directory called
~/GrandmasHugeCookbook.yaml, set this option to
language: Human language to use. Currently supported:
In honor of Logan, Utah's greatest Breakfast & Brunch.