-
Notifications
You must be signed in to change notification settings - Fork 13
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
site: fixed styles on how it works page
Signed-off-by: Alexey Igrychev <[email protected]>
- Loading branch information
1 parent
f7289ad
commit a8c16d0
Showing
12 changed files
with
189 additions
and
173 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
12 changes: 5 additions & 7 deletions
12
docs/_includes/documentation/how_it_works_en/how-work-trdl.html
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,9 +1,7 @@ | ||
| <section class="how-work__section"> | ||
| <div class="container"> | ||
| <div class="how-work__wrap"> | ||
| <div class="how-work__title block__title">How does trdl work?</div> | ||
| <div class="how-work__desc block__description">Let's look at how the project team uses trdl to continuously deliver updates to users. The process in its simplified form involves three main steps: pushing the release to the TUF repository, publishing the release channel, and delivering the release to the user via the published release channel.</div> | ||
| <!-- <p class="how-work__footnote">*To learn more about installing and configuring trdl, see <a href="">Getting started</a> section.</p> --> | ||
| </div> | ||
| <section class="how-work__section ignore-sidebar"> | ||
| <div class="how-work__wrap"> | ||
| <div class="how-work__title block__title">How does trdl work?</div> | ||
| <div class="how-work__desc block__description">Let's look at how the project team uses trdl to continuously deliver updates to users. The process in its simplified form involves three main steps: pushing the release to the TUF repository, publishing the release channel, and delivering the release to the user via the published release channel.</div> | ||
| <!-- <p class="how-work__footnote">*To learn more about installing and configuring trdl, see <a href="">Getting started</a> section.</p> --> | ||
| </div> | ||
| </section> |
56 changes: 27 additions & 29 deletions
56
docs/_includes/documentation/how_it_works_en/slider-release.html
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,32 +1,30 @@ | ||
| <section class="slider__section"> | ||
| <div class="container"> | ||
| <div class="slider__subtitle block__subtitle">Releasing</div> | ||
| <div class="slider__nav"></div> | ||
| <div class="slider__wrap"> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">The developer makes a commit and signs it with a GPG signature.</p> | ||
| <img src="/images/slider/release/1.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">The project quorum signs the commit with GPG signatures.</p> | ||
| <img src="/images/slider/release/2.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">The release build process commences. The CI system passes the Git tag to Vault.</p> | ||
| <img src="/images/slider/release/3.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">Vault checks to see if the Git tag contains the minimum set of allowed GPG signatures. If all the necessary signatures are there, Vault starts the build.</p> | ||
| <img src="/images/slider/release/4.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">Vault signs the resulting build (artifact). Note that Vault automatically generates keys to sign the build with. Those keys are stored in the Vault storage in encrypted form. No one can access those keys or use them.</p> | ||
| <img src="/images/slider/release/5.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">The resulting build (along with the metadata) gets pushed to the TUF repository.</p> | ||
| <img src="/images/slider/release/6.svg" alt=""> | ||
| </div> | ||
| <section class="slider__section ignore-sidebar"> | ||
| <div class="slider__subtitle block__subtitle">Releasing</div> | ||
| <div class="slider__nav"></div> | ||
| <div class="slider__wrap"> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">The developer makes a commit and signs it with a GPG signature.</p> | ||
| <img src="/images/slider/release/1.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">The project quorum signs the commit with GPG signatures.</p> | ||
| <img src="/images/slider/release/2.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">The release build process commences. The CI system passes the Git tag to Vault.</p> | ||
| <img src="/images/slider/release/3.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">Vault checks to see if the Git tag contains the minimum set of allowed GPG signatures. If all the necessary signatures are there, Vault starts the build.</p> | ||
| <img src="/images/slider/release/4.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">Vault signs the resulting build (artifact). Note that Vault automatically generates keys to sign the build with. Those keys are stored in the Vault storage in encrypted form. No one can access those keys or use them.</p> | ||
| <img src="/images/slider/release/5.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">The resulting build (along with the metadata) gets pushed to the TUF repository.</p> | ||
| <img src="/images/slider/release/6.svg" alt=""> | ||
| </div> | ||
| </div> | ||
| </section> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,36 +1,34 @@ | ||
| <section class="slider__section"> | ||
| <div class="container"> | ||
| <div class="slider__subtitle block__subtitle">Publishing the channels</div> | ||
| <div class="slider__navigation"></div> | ||
| <div class="slider__wrapper"> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">The developer makes changes to the release channels in Git and commits them while signing with a GPG signature.</p> | ||
| <img src="/images/slider/publish/1.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">The project quorum signs the commit with GPG signatures.</p> | ||
| <img src="/images/slider/publish/2.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">The channel publishing process begins. The CI system passes the commit to Vault.</p> | ||
| <img src="/images/slider/publish/3.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">Vault checks to see if the commit contains the minimum set of allowed GPG signatures. If all the necessary signatures are there, Vault forwards the release channels to the TUF repository.</p> | ||
| <img src="/images/slider/publish/4.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">Vault signs the updated list of channels and related releases. Note that Vault automatically generates keys to sign the build with. Those keys are stored in the Vault storage in encrypted form. No one can access them.</p> | ||
| <img src="/images/slider/publish/5.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">The updated channels (along with the metadata) get pushed to the TUF repository.</p> | ||
| <img src="/images/slider/publish/6.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">The trdl client pulls the update through the selected release channel. The previous artifact version becomes unavailable to the user.The trdl client pulls the update through the selected release channel. The previous artifact version becomes unavailable to the user.</p> | ||
| <img src="/images/slider/publish/7.svg" alt=""> | ||
| </div> | ||
| <section class="slider__section ignore-sidebar"> | ||
| <div class="slider__subtitle block__subtitle">Publishing the channels</div> | ||
| <div class="slider__navigation"></div> | ||
| <div class="slider__wrapper"> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">The developer makes changes to the release channels in Git and commits them while signing with a GPG signature.</p> | ||
| <img src="/images/slider/publish/1.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">The project quorum signs the commit with GPG signatures.</p> | ||
| <img src="/images/slider/publish/2.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">The channel publishing process begins. The CI system passes the commit to Vault.</p> | ||
| <img src="/images/slider/publish/3.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">Vault checks to see if the commit contains the minimum set of allowed GPG signatures. If all the necessary signatures are there, Vault forwards the release channels to the TUF repository.</p> | ||
| <img src="/images/slider/publish/4.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">Vault signs the updated list of channels and related releases. Note that Vault automatically generates keys to sign the build with. Those keys are stored in the Vault storage in encrypted form. No one can access them.</p> | ||
| <img src="/images/slider/publish/5.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">The updated channels (along with the metadata) get pushed to the TUF repository.</p> | ||
| <img src="/images/slider/publish/6.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">The trdl client pulls the update through the selected release channel. The previous artifact version becomes unavailable to the user.The trdl client pulls the update through the selected release channel. The previous artifact version becomes unavailable to the user.</p> | ||
| <img src="/images/slider/publish/7.svg" alt=""> | ||
| </div> | ||
| </div> | ||
| </section> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
10 changes: 4 additions & 6 deletions
10
docs/_includes/documentation/how_it_works_ru/how-work-trdl.html
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,8 +1,6 @@ | ||
| <section class="how-work__section"> | ||
| <div class="container"> | ||
| <div class="how-work__wrap"> | ||
| <div class="how-work__title block__title">Как работает trdl</div> | ||
| <!-- <p class="how-work__footnote">*Непосредственная установка и настройка trdl рассматриваются в <a href="">Getting started.</a></p> --> | ||
| </div> | ||
| <section class="how-work__section ignore-sidebar"> | ||
| <div class="how-work__wrap"> | ||
| <div class="how-work__title block__title">Как работает trdl</div> | ||
| <!-- <p class="how-work__footnote">*Непосредственная установка и настройка trdl рассматриваются в <a href="">Getting started.</a></p> --> | ||
| </div> | ||
| </section> |
56 changes: 27 additions & 29 deletions
56
docs/_includes/documentation/how_it_works_ru/slider-release.html
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,32 +1,30 @@ | ||
| <section class="slider__section"> | ||
| <div class="container"> | ||
| <div class="slider__subtitle block__subtitle">Релиз новой версии</div> | ||
| <div class="slider__nav"></div> | ||
| <div class="slider__wrap"> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">Разработчик создает Git-тег с новой версией ПО (v1.0.1) и подписывает его своей GPG-подписью.</p> | ||
| <img src="/images/slider/release/1.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">Кворум проекта подписывает Git-тег своими GPG-подписями.</p> | ||
| <img src="/images/slider/release/2.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">Инициируется процесс сборки релиза. Из CI-системы имя Git-тега поступает в Vault.</p> | ||
| <img src="/images/slider/release/3.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">Vault проверяет, содержит ли Git-тег минимальный набор разрешённых GPG-подписей. Если все необходимые подписи есть, Vault инициирует сборку.</p> | ||
| <img src="/images/slider/release/4.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">Vault подписывает результат сборки (артефакт). Для подписи используются ключи, которые Vault сам же автоматически генерирует и хранит в зашифрованном виде в своём хранилище. Никто не может получить доступ к этим ключам.</p> | ||
| <img src="/images/slider/release/5.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">Результат сборки вместе с метаданными загружаются в TUF-репозиторий. Однако клиент продолжает работать со старой версией ПО (v1.0.0) до тех пор, пока новая версия не будет опубликована в выбранном канале обновлений.</p> | ||
| <img src="/images/slider/release/6.svg" alt=""> | ||
| </div> | ||
| <section class="slider__section ignore-sidebar"> | ||
| <div class="slider__subtitle block__subtitle">Релиз новой версии</div> | ||
| <div class="slider__nav"></div> | ||
| <div class="slider__wrap"> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">Разработчик создает Git-тег с новой версией ПО (v1.0.1) и подписывает его своей GPG-подписью.</p> | ||
| <img src="/images/slider/release/1.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">Кворум проекта подписывает Git-тег своими GPG-подписями.</p> | ||
| <img src="/images/slider/release/2.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">Инициируется процесс сборки релиза. Из CI-системы имя Git-тега поступает в Vault.</p> | ||
| <img src="/images/slider/release/3.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">Vault проверяет, содержит ли Git-тег минимальный набор разрешённых GPG-подписей. Если все необходимые подписи есть, Vault инициирует сборку.</p> | ||
| <img src="/images/slider/release/4.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">Vault подписывает результат сборки (артефакт). Для подписи используются ключи, которые Vault сам же автоматически генерирует и хранит в зашифрованном виде в своём хранилище. Никто не может получить доступ к этим ключам.</p> | ||
| <img src="/images/slider/release/5.svg" alt=""> | ||
| </div> | ||
| <div class="slider__item"> | ||
| <p class="slide__text">Результат сборки вместе с метаданными загружаются в TUF-репозиторий. Однако клиент продолжает работать со старой версией ПО (v1.0.0) до тех пор, пока новая версия не будет опубликована в выбранном канале обновлений.</p> | ||
| <img src="/images/slider/release/6.svg" alt=""> | ||
| </div> | ||
| </div> | ||
| </section> |
Oops, something went wrong.