Azure
/
draft-classic
зеркало из https://github.com/Azure/draft-classic.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
draft-classic/packs/README.md

22 строки
461 B
Markdown
Исходник Обычный вид История

feat(packs): use go-bindata to pack builtin packs This replaces the hard-coded built-in packs with a generator that uses go-bindata to read the `packs/` directory and generate an internal representation that is compiled into the binary. It adds the make target `generate`, which is called by the build and cross-compile steps. Doing things this way has the following advantages: - Managing built-in packs is much easier (see #95) - The packed binaries are compressed, so overall memory footprint is smaller The main disadvantage is that it is harder to share files across the packs. However, it is likely that these paks would diverge over time anyway.
2017-06-03 18:31:59 +03:00
# Built-in Packs
add pack-repo plugin, install by default with `draft init` This bootstraps the client with the `draft pack-repo` plugin, then installs or updates the packs using that plugin. This removes the existing functionality on how packs are written to ~/.draft/packs, but the workflow is identical to the end-user.
2017-09-29 01:31:09 +03:00
This directory contains the built-in Draft packs which are installed via `draft init`.
feat(packs): use go-bindata to pack builtin packs This replaces the hard-coded built-in packs with a generator that uses go-bindata to read the `packs/` directory and generate an internal representation that is compiled into the binary. It adds the make target `generate`, which is called by the build and cross-compile steps. Doing things this way has the following advantages: - Managing built-in packs is much easier (see #95) - The packed binaries are compressed, so overall memory footprint is smaller The main disadvantage is that it is harder to share files across the packs. However, it is likely that these paks would diverge over time anyway.
2017-06-03 18:31:59 +03:00
add pack-repo plugin, install by default with `draft init` This bootstraps the client with the `draft pack-repo` plugin, then installs or updates the packs using that plugin. This removes the existing functionality on how packs are written to ~/.draft/packs, but the workflow is identical to the end-user.
2017-09-29 01:31:09 +03:00
_If you are interested in creating your own packs_, you can simply create those packs in your local `$(draft home)/packs` directory.
feat(packs): use go-bindata to pack builtin packs This replaces the hard-coded built-in packs with a generator that uses go-bindata to read the `packs/` directory and generate an internal representation that is compiled into the binary. It adds the make target `generate`, which is called by the build and cross-compile steps. Doing things this way has the following advantages: - Managing built-in packs is much easier (see #95) - The packed binaries are compressed, so overall memory footprint is smaller The main disadvantage is that it is harder to share files across the packs. However, it is likely that these paks would diverge over time anyway.
2017-06-03 18:31:59 +03:00
```
add pack-repo plugin, install by default with `draft init` This bootstraps the client with the `draft pack-repo` plugin, then installs or updates the packs using that plugin. This removes the existing functionality on how packs are written to ~/.draft/packs, but the workflow is identical to the end-user.
2017-09-29 01:31:09 +03:00
packs/github.com/Azure/draft/packs
feat(packs): use go-bindata to pack builtin packs This replaces the hard-coded built-in packs with a generator that uses go-bindata to read the `packs/` directory and generate an internal representation that is compiled into the binary. It adds the make target `generate`, which is called by the build and cross-compile steps. Doing things this way has the following advantages: - Managing built-in packs is much easier (see #95) - The packed binaries are compressed, so overall memory footprint is smaller The main disadvantage is that it is harder to share files across the packs. However, it is likely that these paks would diverge over time anyway.
2017-06-03 18:31:59 +03:00
|
|- PACKNAME
| |
rename chart/ to charts/
2017-10-17 01:23:29 +03:00
| |- charts/
feat(packs): use go-bindata to pack builtin packs This replaces the hard-coded built-in packs with a generator that uses go-bindata to read the `packs/` directory and generate an internal representation that is compiled into the binary. It adds the make target `generate`, which is called by the build and cross-compile steps. Doing things this way has the following advantages: - Managing built-in packs is much easier (see #95) - The packed binaries are compressed, so overall memory footprint is smaller The main disadvantage is that it is harder to share files across the packs. However, it is likely that these paks would diverge over time anyway.
2017-06-03 18:31:59 +03:00
| | |- Chart.yaml
| | |- ...
| |- Dockerfile
| |- detect
| |- ...
|
|- PACK2
|-...
```