This project has been archived by its maintainers, and is no longer receiving any updates.
micoo: quick access to mise-cookbooks
[!WARNING]
micoois deprecated and no longer maintained. It has been superseded bycobo, a generic boilerplate fetcher that supports mise cookbooks, gitignore templates, and any user-configured source. See Migrating tocobobelow for the migration guide.
micoo (short for mise cookbooks) is a :zap: command-line tool that makes it easy to access mise configuration files from mise-cookbooks :books:.
Migrating to cobo
micoo is no longer maintained — v0.6.0 is the final release. Prior releases stay installable for reproducibility but receive no fixes.
Swap the tool
uv tool uninstall micoo
uv tool install cobo
(Using pipx or mise install pipx:micoo? Substitute the equivalent uninstall/install commands.)
Then use it exactly as before, under the mise source:
cobo mise update
cobo mise dump python > mise.local.toml
Command mapping
Old (micoo) |
New (cobo) |
|---|---|
micoo dump python |
cobo mise dump python |
micoo list |
cobo mise list |
micoo search foo |
cobo mise search foo |
micoo update |
cobo mise update (single source) or cobo update (all sources) |
micoo root |
cobo mise root (single source) or cobo root (cache root) |
micoo remote |
cobo mise remote |
micoo info |
cobo info |
micoo log |
(dropped — cobo has no log command; cobo info reports the cache root) |
micoo version |
cobo version |
micoo interactive |
(dropped — use shell redirection: cobo mise dump python > mise.local.toml) |
Why?
micoo only fetched mise cookbooks. cobo generalizes the same pattern (clone a repo, list templates, dump one to stdout) to any boilerplate source — with built-in support for mise, gitignore, gitattributes, editorconfig, and licenses, plus user-defined sources via a single TOML config.
New issues should be filed against cobo rather than this repository.
Typical Usage :rocket:
# List available cookbooks
micoo list
# Create a new mise.toml with a cookbook
micoo dump python > mise.toml
Features :sparkles:
- 🚀 Quick access to mise-cookbooks
- 📚 Easy cookbook listing and content viewing
- 💾 Simple dumping of cookbooks to mise.toml
- 🔄 Repository cloning and updating
- 🌐 Browser integration for quick repository access
- 🎯 Interactive mode for cookbook selection and generation
Installation :package:
There are several ways to install micoo! :rocket: I recommend using (obviously) mise :hammer_and_wrench:. Here's how to do it:
mise install pipx:micoo
Alternatively, you can install it using uv tool install micoo :jigsaw:
uv tool install micoo
Command Reference :book:
Here is the output of the micoo --help command:
Usage: micoo [OPTIONS] COMMAND [ARGS]...
╭─ Options ──────────────────────────────────────────────────────────────────────────────────────────╮
│ --install-completion Install completion for the current shell. │
│ --show-completion Show completion for the current shell, to copy it or customize the │
│ installation. │
│ --help Show this message and exit. │
╰────────────────────────────────────────────────────────────────────────────────────────────────────╯
╭─ Commands ─────────────────────────────────────────────────────────────────────────────────────────╮
│ update Clone or fetch the `mise-cookbooks` repository. │
│ list List the available mise cookbooks. │
│ search Search for a mise cookbook. │
│ dump Dump a mise cookbook. │
│ root Show the path to the micoo boilerplates directory. │
│ log Show the path to the micoo log file. │
│ remote Show the URL to the remote repository. │
│ version Show the current version number of micoo. │
│ info Display information about the micoo application. │
│ interactive Start interactive mode for cookbook selection and generation. │
╰────────────────────────────────────────────────────────────────────────────────────────────────────╯
Usage :hammer_and_wrench:
You can use the micoo command to interact with mise-cookbooks. Here are some common commands:
List all available cookbooks:
micoo list
This will output:
Available cookbooks:
- terraform
- python
- cpp
- pnpm
- node
- ruby-on-rails
- opentofu
Dump a specific cookbook to a mise.toml file:
micoo dump python > mise.toml
Open the mise-cookbooks repository in the default application:
open $(micoo remote)
Open the cloned repository in the default application:
open $(micoo root)
Open the log file in the default application:
open $(micoo log)
Show the current version of micoo:
micoo version
Show the information about the micoo application:
micoo info
Start interactive mode for cookbook selection and generation:
micoo interactive
The interactive mode supports multiple output locations:
mise.toml- Standard configuration filemise.local.toml- Local config (not committed to source control)mise/config.toml- Configuration in mise subdirectory.config/mise.toml- Configuration in .config directory.config/mise/config.toml- Configuration in .config/mise subdirectory.config/mise/conf.d/custom.toml- Configuration in conf.d directory (alphabetical loading)
Support :heart:
If you have any questions or need help, feel free to open an issue on the GitHub repository.
Author :person_with_crown:
This project is maintained by Hasan Sezer Taşan, It's me :wave:
Contributing :heart:
Any contributions are welcome! Please follow the Contributing Guidelines to contribute to this project.
Tasks
Clone the repository and cd into the project directory:
git clone https://github.com/hasansezertasan/micoo
cd micoo
The commands below can also be executed using the xc task runner, which combines the usage instructions with the actual commands. Simply run xc, it will pop up an interactive menu with all available tasks.
install
Install the dependencies:
uv sync
style
Run the style checks:
uv run --locked tox run -e style
ci
Run the CI pipeline:
uv run --locked tox run
Related Projects :chains:
- mise - The official mise project
- mise-cookbooks - Collection of mise cookbooks
License :scroll:
This project is licensed under the MIT License.
Changelog :memo:
Please check the Releases page for the changelog.
Metadata
Release files for micoo 0.6.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| micoo-0.6.0.tar.gz | 71.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| micoo-0.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 82.8 kB
Release files / micoo-0.6.0.tar.gz
| Download URL | micoo-0.6.0.tar.gz |
|---|---|
| Size | 71.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
26a4d169581c9e96a51b5405de046c69a1740fb0eb16fb3c2bc8b33e3ae79ac3
|
|
BLAKE2b-256 checksum How to use checksums |
b3c2273c1b2467a957cb7024e6bcc74da5050fc4452630faa51bd3af9c1d7feb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.11.23 {"installer":{"name":"uv","version":"0.11.23","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / micoo-0.6.0-py3-none-any.whl
| Download URL | micoo-0.6.0-py3-none-any.whl |
|---|---|
| Size | 11.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b6b366b29e4343415cc4a92e6f2d4ac609128b0f6bb940cc3482091de0b367f9
|
|
BLAKE2b-256 checksum How to use checksums |
b115026d38c6d22b2d96e8c294b9385547adfeff6a09a61dbc944854e07b7494
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.11.23 {"installer":{"name":"uv","version":"0.11.23","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for micoo 0.6.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.