Manages Homebrew.
Table of Contents
Applying tool_brew will make sure brew is configured as specified.
The general configuration structure is in line with all other formulae from the tool suite, for details see :ref:`toolsuite`. An example pillar is provided, see :ref:`pillar.example`. Note that you do not need to specify everything by pillar. Often, it's much easier and less resource-heavy to use the parameters/<grain>/<value>.yaml files for non-sensitive settings. The underlying logic is explained in :ref:`map.jinja`.
The following shows an example of tool_brew per-user configuration. If provided by pillar, namespace it to tool_global:users and/or tool_brew:users. For the parameters YAML file variant, it needs to be nested under a values parent key. The YAML files are expected to be found in
salt://tool_brew/parameters/<grain>/<value>.yamlorsalt://tool_global/parameters/<grain>/<value>.yaml.
user:
# Persist environment variables used by this formula for this
# user to this file (will be appended to a file relative to $HOME)
persistenv: '.config/zsh/zshenv'
# Add runcom hooks specific to this formula to this file
# for this user (will be appended to a file relative to $HOME)
rchook: '.config/zsh/zshrc'tool_brew:
# Specify configuration env vars to be used during salt run.
config:
- HOMEBREW_NO_ANALYTICS
- HOMEBREW_NO_INSECURE_REDIRECT
- HOMEBREW_CASK_OPTS:
- --require-sha
- --no-quarantine
# Ensure brew bin dir is globally in/absent from `$PATH`.
globalpath: true
# Helper to automatically install packages.
packages:
- git
- gpg
- wget
taps:
# List of taps that should not be available.
absent:
- unwanted/tap
# By default, taps not hosted on Github are not updated automatically
# (for performance reasons). Force automatic updates for taps managed
# with this formula, either by default or only for specific ones.
# This formula forces autoupdate for mirrors of offical taps automatically.
autoupdate:
default: false
my/customtap: true
# Force override of existing remotes with specified ones
# (not necessary for mirrors of official taps).
forced: false
# homebrew-cask* mirrors and custom taps go here:
wanted:
# If you specify the name of an official tap, the remote will be matched.
# If you specify the name of an existing non-official tap and
# taps_forced is set to true, the remote will be matched.
- homebrew/cask: https://mygit.example.com/my/homebrew-cask
- homebrew/cask-versions: https://mygit.example.com/my/homebrew-cask-versions
- homebrew/cask-drivers: https://mygit.example.com/my/homebrew-cask-drivers
- homebrew/cask-fonts: https://mygit.example.com/my/homebrew-cask-fonts
# brew tap short syntax works as well
# (mapped to github.com/<first>/homebrew-<second>)
- blacktop/tap
- my/customtap: https://mygit.example.com/my/custom-tapCommit message formatting is significant.
Please see How to contribute for more details.
pre-commit is configured for this formula, which you may optionally use to ease the steps involved in submitting your changes.
First install the pre-commit package manager using the appropriate method, then run bin/install-hooks and
now pre-commit will run automatically on each git commit.
$ bin/install-hooks
pre-commit installed at .git/hooks/pre-commit
pre-commit installed at .git/hooks/commit-msgThere is a script that semi-autodocuments available states: bin/slsdoc.
If a .sls file begins with a Jinja comment, it will dump that into the docs. It can be configured differently depending on the formula. See the script source code for details currently.
This means if you feel a state should be documented, make sure to write a comment explaining it.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent