This commit is contained in:
sobolevn 2021-06-26 16:58:27 +03:00
parent b65673cb4c
commit d79b5597f6
No known key found for this signature in database
GPG Key ID: FF672D568AE3C73E
8 changed files with 24 additions and 17 deletions

1
.gitignore vendored
View File

@ -137,4 +137,5 @@ build/
docs/man docs/man
docs/_posts docs/_posts
docs/_includes/install-*.sh docs/_includes/install-*.sh
docs/_includes/version.txt
CHANGELOG-RELEASE.md CHANGELOG-RELEASE.md

View File

@ -106,7 +106,7 @@ build-man: git-secret
.PHONY: build-docs .PHONY: build-docs
build-docs: build-man build-docs: build-man
${SHELL} docs/create_posts.sh ${SHELL} docs/build.sh
.PHONY: docs .PHONY: docs
docs: build-docs docs: build-docs

View File

@ -3,4 +3,5 @@ source "https://rubygems.org"
group :jekyll_plugins do group :jekyll_plugins do
gem "jekyll", ">= 3.6.3" gem "jekyll", ">= 3.6.3"
gem "jekyll-seo-tag", "~> 2.7.1" gem "jekyll-seo-tag", "~> 2.7.1"
gem "jekyll-environment-variables", ">= 1.0.1"
end end

View File

@ -29,6 +29,8 @@ GEM
rouge (~> 3.0) rouge (~> 3.0)
safe_yaml (~> 1.0) safe_yaml (~> 1.0)
terminal-table (~> 2.0) terminal-table (~> 2.0)
jekyll-environment-variables (1.0.1)
jekyll (>= 3.0, < 5.x)
jekyll-sass-converter (2.1.0) jekyll-sass-converter (2.1.0)
sassc (> 2.0.1, < 3.0) sassc (> 2.0.1, < 3.0)
jekyll-seo-tag (2.7.1) jekyll-seo-tag (2.7.1)
@ -61,9 +63,11 @@ GEM
PLATFORMS PLATFORMS
x86_64-linux x86_64-linux
x86_64-linux-musl
DEPENDENCIES DEPENDENCIES
jekyll (>= 3.6.3) jekyll (>= 3.6.3)
jekyll-environment-variables (>= 1.0.1)
jekyll-seo-tag (~> 2.7.1) jekyll-seo-tag (~> 2.7.1)
BUNDLED WITH BUNDLED WITH

View File

@ -1,15 +1,7 @@
# Welcome to Jekyll!
#
# This config file is meant for settings that affect your whole blog, values
# which you are expected to set up once and rarely need to edit after that.
# For technical reasons, this file is *NOT* reloaded automatically when you use
# 'jekyll serve'. If you change this file, please restart the server process.
# Site settings # Site settings
title: git-secret title: git-secret
email: mail@sobolevn.me email: mail@sobolevn.me
description: > # this means to ignore newlines until "baseurl:" description: A bash-tool to store your private data inside a git repository.
A bash-tool to store your private data inside a git repository.
baseurl: "" # the subpath of your site, e.g. /blog baseurl: "" # the subpath of your site, e.g. /blog
url: "git-secret.io" # the base hostname & protocol for your site url: "git-secret.io" # the base hostname & protocol for your site
@ -20,8 +12,9 @@ github_plugins: "https://github.com/sobolevn/git-secret/wiki/Third-party-plugins
github_using: "https://github.com/sobolevn/git-secret/wiki/Who-uses" github_using: "https://github.com/sobolevn/git-secret/wiki/Who-uses"
# Seo settings: # Seo settings:
gems: plugins:
- jekyll-seo-tag - jekyll-seo-tag
- jekyll-environment-variables
# Build settings # Build settings
markdown: kramdown markdown: kramdown

View File

@ -2,7 +2,9 @@
<div class="wrapper"> <div class="wrapper">
<a class="site-title" href="{{ site.baseurl }}/">{{ site.title }}</a> <a class="site-title" href="{{ site.baseurl }}/">
{{ site.title }} v{% include version.txt %}
</a>
<div class="site-nav"> <div class="site-nav">
<a href="#" class="menu-icon"> <a href="#" class="menu-icon">

View File

@ -15,4 +15,4 @@ There's a known problem in server configuration and deploying, when you have to
`git-secret` is a bash tool to store your private data inside a `git` repo. How's that? Basically, it just encrypts, using `gpg`, the tracked files with the public keys of all the users that you trust. So everyone of them can decrypt these files using only their personal secret key. Why deal with all this private-public keys stuff? Well, to make it easier for everyone to manage access rights. There are no passwords that change. When someone is out - just delete their public key, reencrypt the files, and they won't be able to decrypt secrets anymore. `git-secret` is a bash tool to store your private data inside a `git` repo. How's that? Basically, it just encrypts, using `gpg`, the tracked files with the public keys of all the users that you trust. So everyone of them can decrypt these files using only their personal secret key. Why deal with all this private-public keys stuff? Well, to make it easier for everyone to manage access rights. There are no passwords that change. When someone is out - just delete their public key, reencrypt the files, and they won't be able to decrypt secrets anymore.
[![git-secret terminal preview](git-secret.gif)](https://asciinema.org/a/41811?autoplay=1) [![git-secret terminal preview](https://raw.githubusercontent.com/sobolevn/git-secret/master/git-secret.gif)](https://asciinema.org/a/41811?autoplay=1)

View File

@ -34,8 +34,8 @@ function copy_to_posts {
short_name=$(echo "$com" | sed -n "s|$MAN_LOCATION/\(.*\)\.1\.md|\1|p") short_name=$(echo "$com" | sed -n "s|$MAN_LOCATION/\(.*\)\.1\.md|\1|p")
local command_header="--- local command_header="---
layout: post layout: post
title: '${short_name}' title: '${short_name}'
date: ${timestamp} date: ${timestamp}
permalink: ${short_name} permalink: ${short_name}
categories: command categories: command
---" ---"
@ -48,8 +48,8 @@ categories: command
# Creating main usage file: # Creating main usage file:
local usage_header="--- local usage_header="---
layout: post layout: post
title: 'git-secret' title: 'git-secret'
date: ${timestamp} date: ${timestamp}
permalink: git-secret permalink: git-secret
categories: usage categories: usage
---" ---"
@ -68,6 +68,12 @@ function copy_install_scripts {
} }
function copy_version {
echo "$(./git-secret --version)" > docs/_includes/version.txt
}
checkout_manuals checkout_manuals
copy_to_posts copy_to_posts
copy_install_scripts copy_install_scripts
copy_version