M posts/git_server_centos.md => posts/git_server_centos.md +0 -7
@@ 155,10 155,3 @@ If you are playing with the configuration options, you may need to remove the
cache as cgit will cache the output it sends to the browser:
$ sudo rm -f /var/cache/cgit/*
* **2019-08-08**: make sure permission of `/var/lib/git` is correct
* **2019-07-22**: `adduser` also takes the `-m` parameter to create the
* **2019-04-11**: CentOS now has Python 3.6 in EPEL
M posts/git_sign.md => posts/git_sign.md +0 -2
@@ 20,5 20,3 @@ As my keyring only works with `gpg2` and not with `gpg` you also have to set
command = xz -c
**UPDATE** (2018-06-18): add the `tar "tar.xz"` section.
M posts/git_signed_releases.md => posts/git_signed_releases.md +0 -10
@@ 88,13 88,3 @@ You can verify the signature:
gpg: Good signature from "François Kooman <email@example.com>" [ultimate]
Easy peasy ;-)
**UPDATE** (2018-06-09): the `git archive` command got a `--prefix` now as to
put the contents in a directory containing the name and version of the
**UPDATE** (2018-06-26): add the `--yes` flag to `gpg2` to avoid it asking
to overwrite the signature file
**UPDATE** (2019-04-23): do not overwrite existing release(s), remove the
`--yes` flag again, add `make_release_all` script, fix `release` path
M posts/minisign.md => posts/minisign.md +0 -4
@@ 93,7 93,3 @@ communication channel with the signer of the source code.
Another step closer to a world without PGP! And maybe packaging Minisign is
a first step in moving RPM package signatures to use Minisign as well!
* **2019-08-08**: link to EPEL 8 bodhi for Minisign package
M posts/php_database_migrations.md => posts/php_database_migrations.md +0 -2
@@ 70,5 70,3 @@ make it cleaner to add to your code as you don't need to embed the SQL
queries in the source code.
Let [me](../about.html) know what you think!
**UPDATE** (2018-06-25): use `;` now in example migration.