dotbins 0.1.0__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
dotbins-0.1.0/LICENSE ADDED
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright [yyyy] [name of copyright owner]
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
dotbins-0.1.0/PKG-INFO ADDED
@@ -0,0 +1,422 @@
1
+ Metadata-Version: 2.2
2
+ Name: dotbins
3
+ Version: 0.1.0
4
+ Summary: Keep updated binaries in your dotfiles
5
+ Author-email: Bas Nijholt <bas@nijho.lt>
6
+ Project-URL: Homepage, https://github.com/basnijholt/dotbins
7
+ Requires-Python: >=3.9
8
+ Description-Content-Type: text/markdown
9
+ License-File: LICENSE
10
+ Requires-Dist: requests
11
+ Requires-Dist: pyyaml
12
+ Requires-Dist: rich>=13.9.4
13
+ Provides-Extra: test
14
+ Requires-Dist: pytest; extra == "test"
15
+ Requires-Dist: pre-commit; extra == "test"
16
+ Requires-Dist: coverage; extra == "test"
17
+ Requires-Dist: pytest-cov; extra == "test"
18
+ Provides-Extra: docs
19
+
20
+ # dotbins 🧰
21
+
22
+ ![Build](https://github.com/basnijholt/dotbins/actions/workflows/pytest.yml/badge.svg)
23
+ [![Coverage](https://img.shields.io/codecov/c/github/basnijholt/dotbins)](https://codecov.io/gh/basnijholt/dotbins)
24
+ [![GitHub](https://img.shields.io/github/stars/basnijholt/dotbins.svg?style=social)](https://github.com/basnijholt/dotbins/stargazers)
25
+ [![PyPI](https://img.shields.io/pypi/v/dotbins.svg)](https://pypi.python.org/pypi/dotbins)
26
+ [![License](https://img.shields.io/github/license/basnijholt/dotbins)](https://github.com/basnijholt/dotbins/blob/main/LICENSE)
27
+ [![Downloads](https://img.shields.io/pypi/dm/dotbins)](https://pypi.python.org/pypi/dotbins)
28
+ ![Open Issues](https://img.shields.io/github/issues-raw/basnijholt/dotbins)
29
+
30
+ Introducing `dotbins` - a utility for managing CLI tool binaries in your dotfiles repository. It downloads and organizes binaries for popular tools across multiple platforms (macOS, Linux) and architectures (amd64, arm64), helping you maintain a consistent set of CLI utilities across all your environments.
31
+
32
+ Whether you work across multiple machines or just want a version-controlled setup for your essential command-line tools, dotbins makes it easy to keep everything synchronized and updated. 🚀
33
+
34
+ <details><summary><b><u>[ToC]</u></b> 📚</summary>
35
+
36
+ <!-- START doctoc generated TOC please keep comment here to allow auto update -->
37
+ <!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
38
+
39
+ - [:star2: Features](#star2-features)
40
+ - [:books: Usage](#books-usage)
41
+ - [Commands](#commands)
42
+ - [:hammer_and_wrench: Installation](#hammer_and_wrench-installation)
43
+ - [:gear: Configuration](#gear-configuration)
44
+ - [Basic Configuration](#basic-configuration)
45
+ - [Tool Configuration](#tool-configuration)
46
+ - [Platform and Architecture Mapping](#platform-and-architecture-mapping)
47
+ - [Pattern Variables](#pattern-variables)
48
+ - [Multiple Binaries](#multiple-binaries)
49
+ - [Configuration Examples](#configuration-examples)
50
+ - [Standard Tool](#standard-tool)
51
+ - [Tool with Multiple Binaries](#tool-with-multiple-binaries)
52
+ - [Platform-Specific Tool](#platform-specific-tool)
53
+ - [Full Configuration Example](#full-configuration-example)
54
+ - [:bulb: Examples](#bulb-examples)
55
+ - [:computer: Shell Integration](#computer-shell-integration)
56
+ - [:mag: Finding Tool Patterns](#mag-finding-tool-patterns)
57
+ - [:heart: Support and Contributions](#heart-support-and-contributions)
58
+
59
+ <!-- END doctoc generated TOC please keep comment here to allow auto update -->
60
+
61
+ </details>
62
+
63
+ ## :star2: Features
64
+
65
+ * 🌐 Supports multiple platforms (macOS, Linux) and architectures (amd64, arm64)
66
+ * 📦 Downloads and organizes binaries from GitHub releases
67
+ * 🔄 Updates tools to their latest versions with a single command
68
+ * 🧩 Extracts binaries from various archive formats (zip, tar.gz)
69
+ * 📂 Organizes tools by platform and architecture for easy access
70
+ * 🔍 Includes a tool to analyze GitHub releases to help configure new tools
71
+ * 🐙 Easy integration with your dotfiles repository for version control
72
+
73
+ ## :books: Usage
74
+
75
+ To use `dotbins`, you'll need to familiarize yourself with its commands:
76
+
77
+ ```bash
78
+ dotbins --help
79
+ ```
80
+
81
+ <!-- CODE:BASH:START -->
82
+ <!-- echo '```bash' -->
83
+ <!-- dotbins --help -->
84
+ <!-- echo '```' -->
85
+ <!-- CODE:END -->
86
+
87
+ <!-- OUTPUT:START -->
88
+ <!-- ⚠️ This content is auto-generated by `markdown-code-runner`. -->
89
+ ```bash
90
+ usage: dotbins [-h] [-v] [--tools-dir TOOLS_DIR] [--config-file CONFIG_FILE]
91
+ {list,update,init,analyze,version} ...
92
+
93
+ dotbins - Manage CLI tool binaries in your dotfiles repository
94
+
95
+ positional arguments:
96
+ {list,update,init,analyze,version}
97
+ Command to execute
98
+ list List available tools
99
+ update Update tools
100
+ init Initialize directory structure
101
+ analyze Analyze GitHub releases for a tool
102
+ version Print version information
103
+
104
+ options:
105
+ -h, --help show this help message and exit
106
+ -v, --verbose Enable verbose output (default: False)
107
+ --tools-dir TOOLS_DIR
108
+ Tools directory (default: None)
109
+ --config-file CONFIG_FILE
110
+ Path to configuration file (default: None)
111
+ ```
112
+
113
+ <!-- OUTPUT:END -->
114
+
115
+ ### Commands
116
+
117
+ 1. **init** - Initialize the tools directory structure
118
+ 2. **list** - List available tools defined in your configuration
119
+ 3. **update** - Download or update tools
120
+ 4. **analyze** - Analyze GitHub releases to help configure new tools
121
+
122
+ ## :hammer_and_wrench: Installation
123
+
124
+ To install `dotbins`, simply use pip:
125
+
126
+ ```bash
127
+ pip install dotbins
128
+ ```
129
+
130
+ You'll also need to create or update your `tools.yaml` configuration file either in the same directory as the script or at a custom location specified with `--tools-dir`.
131
+
132
+ ## :gear: Configuration
133
+
134
+ dotbins uses a YAML configuration file (`tools.yaml`) to define the tools and settings.
135
+
136
+ ### Basic Configuration
137
+
138
+ ```yaml
139
+ # Basic settings
140
+ dotfiles_dir: ~/.dotfiles
141
+ tools_dir: ~/.dotfiles/tools
142
+
143
+ # Target platforms and architectures
144
+ platforms:
145
+ - linux
146
+ - macos
147
+ architectures:
148
+ - amd64
149
+ - arm64
150
+
151
+ # Tool definitions
152
+ tools:
153
+ # Tool configuration entries
154
+ ```
155
+
156
+ ### Tool Configuration
157
+
158
+ Each tool must be configured with these fields:
159
+
160
+ ```yaml
161
+ tool-name:
162
+ repo: owner/repo # Required: GitHub repository
163
+ extract_binary: true # Whether to extract from archive (true) or direct download (false)
164
+ binary_name: executable-name # Name of the resulting binary(ies)
165
+ binary_path: path/to/binary # Path to the binary within the archive
166
+ # Option 1: Platform-specific patterns
167
+ asset_patterns: # Required: Asset patterns for each platform
168
+ linux: pattern-for-linux.tar.gz
169
+ macos: pattern-for-macos.tar.gz
170
+ # Option 2: Single pattern for all platforms
171
+ asset_patterns: pattern-for-all-platforms.tar.gz # Global pattern for all platforms
172
+ ```
173
+
174
+ ### Platform and Architecture Mapping
175
+
176
+ If the tool uses different naming for platforms or architectures:
177
+
178
+ ```yaml
179
+ tool-name:
180
+ # Basic fields...
181
+ platform_map: # Optional: Platform name mapping
182
+ macos: darwin # Converts "macos" to "darwin" in patterns
183
+ arch_map: # Optional: Architecture name mapping
184
+ amd64: x86_64 # Converts "amd64" to "x86_64" in patterns
185
+ arm64: aarch64 # Converts "arm64" to "aarch64" in patterns
186
+ ```
187
+
188
+ ### Pattern Variables
189
+
190
+ In asset patterns, you can use these variables:
191
+ - `{version}` - Release version (without 'v' prefix)
192
+ - `{platform}` - Platform name (after applying platform_map)
193
+ - `{arch}` - Architecture name (after applying arch_map)
194
+
195
+ ### Multiple Binaries
196
+
197
+ For tools that provide multiple binaries:
198
+
199
+ ```yaml
200
+ tool-name:
201
+ # Other fields...
202
+ binary_name: [main-binary, additional-binary]
203
+ binary_path: [path/to/main, path/to/additional]
204
+ ```
205
+
206
+ ### Configuration Examples
207
+
208
+ #### Standard Tool
209
+
210
+ ```yaml
211
+ ripgrep:
212
+ repo: BurntSushi/ripgrep
213
+ extract_binary: true
214
+ binary_name: rg
215
+ binary_path: rg
216
+ asset_patterns:
217
+ linux: ripgrep-{version}-x86_64-unknown-linux-musl.tar.gz
218
+ macos: ripgrep-{version}-x86_64-apple-darwin.tar.gz
219
+ arch_map:
220
+ amd64: x86_64
221
+ arm64: aarch64
222
+ ```
223
+
224
+ #### Tool with Multiple Binaries
225
+
226
+ ```yaml
227
+ uv:
228
+ repo: astral-sh/uv
229
+ extract_binary: true
230
+ binary_name: [uv, uvx]
231
+ binary_path: [uv-*/uv, uv-*/uvx]
232
+ asset_patterns:
233
+ linux: uv-{arch}-unknown-linux-gnu.tar.gz
234
+ macos: uv-{arch}-apple-darwin.tar.gz
235
+ arch_map:
236
+ amd64: x86_64
237
+ arm64: aarch64
238
+ ```
239
+
240
+ #### Platform-Specific Tool
241
+
242
+ ```yaml
243
+ linux-only-tool:
244
+ repo: owner/linux-tool
245
+ extract_binary: true
246
+ binary_name: linux-tool
247
+ binary_path: bin/linux-tool
248
+ asset_patterns:
249
+ linux: linux-tool-{version}-{arch}.tar.gz
250
+ macos: null # No macOS version available
251
+ ```
252
+
253
+ ### Full Configuration Example
254
+
255
+ <!-- CODE:BASH:START -->
256
+ <!-- echo '```yaml' -->
257
+ <!-- cat tools.yaml -->
258
+ <!-- echo '```' -->
259
+ <!-- CODE:END -->
260
+
261
+ <!-- OUTPUT:START -->
262
+ <!-- ⚠️ This content is auto-generated by `markdown-code-runner`. -->
263
+ ```yaml
264
+ # Configuration
265
+ dotfiles_dir: ~/.dotfiles
266
+ tools_dir: ~/.dotfiles/tools
267
+
268
+ # Target platforms and architectures
269
+ platforms:
270
+ - linux
271
+ - macos
272
+ architectures:
273
+ - amd64
274
+ - arm64
275
+
276
+ # Tool definitions
277
+ tools:
278
+ fzf:
279
+ repo: junegunn/fzf
280
+ extract_binary: true
281
+ binary_name: fzf
282
+ binary_path: fzf
283
+ asset_patterns: fzf-{version}-{platform}_{arch}.tar.gz
284
+ platform_map:
285
+ macos: darwin
286
+
287
+ bat:
288
+ repo: sharkdp/bat
289
+ extract_binary: true
290
+ binary_name: bat
291
+ binary_path: bat-v{version}-{arch}-*/bat
292
+ arch_map:
293
+ amd64: x86_64
294
+ arm64: aarch64
295
+ asset_patterns:
296
+ linux: bat-v{version}-{arch}-unknown-linux-gnu.tar.gz
297
+ macos: bat-v{version}-{arch}-apple-darwin.tar.gz
298
+
299
+ eza:
300
+ repo: eza-community/eza
301
+ extract_binary: true
302
+ binary_name: eza
303
+ binary_path: eza
304
+ arch_map:
305
+ amd64: x86_64
306
+ arm64: aarch64
307
+ asset_patterns:
308
+ linux: eza_{arch}-unknown-linux-gnu.tar.gz
309
+ macos: null # No macOS binaries available as of now
310
+
311
+ zoxide:
312
+ repo: ajeetdsouza/zoxide
313
+ extract_binary: true
314
+ binary_name: zoxide
315
+ binary_path: zoxide
316
+ arch_map:
317
+ amd64: x86_64
318
+ arm64: aarch64
319
+ asset_patterns:
320
+ linux: zoxide-{version}-{arch}-unknown-linux-musl.tar.gz
321
+ macos: zoxide-{version}-{arch}-apple-darwin.tar.gz
322
+
323
+ delta:
324
+ repo: dandavison/delta
325
+ extract_binary: true
326
+ binary_name: delta
327
+ binary_path: delta-{version}-{arch}-*/delta
328
+ arch_map:
329
+ amd64: x86_64
330
+ arm64: aarch64
331
+ asset_patterns:
332
+ linux: delta-{version}-{arch}-unknown-linux-gnu.tar.gz
333
+ macos: delta-{version}-{arch}-apple-darwin.tar.gz
334
+
335
+ uv:
336
+ repo: astral-sh/uv
337
+ extract_binary: true
338
+ binary_name: [uv, uvx]
339
+ binary_path: [uv-*/uv, uv-*/uvx]
340
+ arch_map:
341
+ amd64: x86_64
342
+ arm64: aarch64
343
+ asset_patterns:
344
+ linux: uv-{arch}-unknown-linux-gnu.tar.gz
345
+ macos: uv-{arch}-apple-darwin.tar.gz
346
+ ```
347
+
348
+ <!-- OUTPUT:END -->
349
+
350
+ ## :bulb: Examples
351
+
352
+ List available tools:
353
+ ```bash
354
+ dotbins list
355
+ ```
356
+
357
+ Update all tools for all platforms:
358
+ ```bash
359
+ dotbins update
360
+ ```
361
+
362
+ Update specific tools only:
363
+ ```bash
364
+ dotbins update fzf bat
365
+ ```
366
+
367
+ Update tools for a specific platform/architecture:
368
+ ```bash
369
+ dotbins update -p macos -a arm64
370
+ ```
371
+
372
+ Analyze a GitHub repository to help configure a new tool:
373
+ ```bash
374
+ dotbins analyze owner/repo
375
+ ```
376
+
377
+ ## :computer: Shell Integration
378
+
379
+ Add this to your shell configuration file (e.g., .bashrc, .zshrc) to use the platform-specific binaries:
380
+
381
+ <!-- CODE:BASH:START -->
382
+ <!-- echo '```bash' -->
383
+ <!-- dotbins init -->
384
+ <!-- echo '```' -->
385
+ <!-- CODE:END -->
386
+
387
+ <!-- OUTPUT:START -->
388
+ <!-- ⚠️ This content is auto-generated by `markdown-code-runner`. -->
389
+ ```bash
390
+ # 🛠️ dotbins initialized tools directory structure
391
+
392
+ # Add this to your shell configuration file (e.g., .bashrc, .zshrc):
393
+
394
+ # dotbins - Add platform-specific binaries to PATH
395
+ _os=$(uname -s | tr '[:upper:]' '[:lower:]')
396
+ [[ "$_os" == "darwin" ]] && _os="macos"
397
+
398
+ _arch=$(uname -m)
399
+ [[ "$_arch" == "x86_64" ]] && _arch="amd64"
400
+ [[ "$_arch" == "aarch64" || "$_arch" == "arm64" ]] && _arch="arm64"
401
+
402
+ export PATH="$HOME/.dotfiles/tools/$_os/$_arch/bin:$PATH"
403
+
404
+ ```
405
+
406
+ <!-- OUTPUT:END -->
407
+
408
+ ## :mag: Finding Tool Patterns
409
+
410
+ To add a new tool, you can use the `analyze` command to examine GitHub release assets:
411
+
412
+ ```bash
413
+ dotbins analyze sharkdp/bat
414
+ ```
415
+
416
+ This will suggest a configuration for the tool based on its release assets.
417
+
418
+ ## :heart: Support and Contributions
419
+
420
+ We appreciate your feedback and contributions! If you encounter any issues or have suggestions for improvements, please file an issue on the GitHub repository. We also welcome pull requests for bug fixes or new features.
421
+
422
+ Happy tooling! 🧰🛠️🎉