-
Updated
May 29, 2020
gnupg
Here are 180 public repositories matching this topic...
-
Updated
May 25, 2020 - Shell
-
Updated
Apr 30, 2020 - Vim script
-
Updated
May 25, 2020 - Shell
-
Updated
Jun 22, 2020 - Java
-
Updated
Jul 11, 2018 - Ruby
-
Updated
Apr 28, 2020 - PHP
-
Updated
Apr 4, 2020 - JavaScript
-
Updated
Oct 1, 2019 - Shell
-
Updated
Sep 24, 2019 - Python
Feature: Well written, clear and formatted documentation.
Recommended approaches
Currently, Most of the configuration files and yml files have well put variable names and functionality. Unfortunately, explaining each choice and option has not been done well enough and what has been written, is written by a mathematics researcher with her very little experience in writing nicely formatted d
-
Updated
May 4, 2019 - Python
-
Updated
May 15, 2020 - Shell
-
Updated
Feb 22, 2020 - HTML
-
Updated
Jun 5, 2018 - Perl
Files output by the tool do not maintain YAML comments.
One consequence is that trying to mask jinja code using comments will result in the jinja being stripped from the resulting file. As the tool will not parse files with naked jinja using comments would be the only good way to preserve it.
something like this should be allowed:
foo:
# {%- if grains['envtype'] == 'dev' %}
bar
-
Updated
Jun 18, 2020 - Nix
Improve this page
Add a description, image, and links to the gnupg topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the gnupg topic, visit your repo's landing page and select "manage topics."
It would be nice if the documentation would how
sheesydifferentiates itself from agit-crypt.So far as I can see currently:
gitMaybe it doesn't make sense to compare
sheesyto a tool likegit-cryptin the first place, since the scopes are somewhat different, if so I apologize! I think that sheezy could be super