| Commit message (Collapse) | Author | Lines |
|
|
|
|
|
With [1] merged upstream and available starting with caddy 2.4.0,
tarballs from cgit will no longer be compressed, making this warning
obsolete.
[1] https://github.com/caddyserver/caddy/pull/4045
|
|
As we noted the lack of translations for the manual in this post, make
sure we update it with more relevant information now that 1.4.1 contains
a German translation of the manual.
|
|
|
|
|
|
Originally we hosted manuals on oriole.systems/man because we did not
yet have a git repository browser that could render manuals on the fly.
Now that we do, retire the old location and directly link to the repo's
about pages instead. This saves us from having to keep man/ up-to-date
as manuals on cgit are updated automatically.
|
|
|
|
|
|
Along with the new release, make sure to document new and changed
dependencies.
|
|
We consider this to be a better and more complete version of
git-send-email.io, so link to it first.
|
|
|
|
|
|
|
|
|
|
Sadly we'll have to move around the footnotes here, but the post is
young enough for that to hopefully not be an issue.
|
|
When generating archives, git-archive(1) puts the commit ID in the
global extended pax header. Therefore, an interesting side effect of
signing tarballs generated with git-archive(1) is that we also
implicitly sign a commit. Whilst we don't expect anyone to go through
the hurdles needed to verify such a commit signature, make sure to
document this case anyway.
|
|
freenode is no more [1][2][3][4].
[1] https://libera.chat/news/welcome-to-libera-chat
[2] https://fuchsnet.ch/privat/fn-resign-letter.txt
[3] https://www.kline.sh/
[4] https://mniip.com/freenode.txt
|
|
Since the previous commit already uses examples from this repository, go
all the way and use it for the rest of the post too.
|
|
This commit attempts to clarify what exactly a tree is, and how trees
used for notes relate to "regular" trees. To that end, include real-life
examples and output from commands run in a repository that is publicly
accessible (in this case, quarg). This allows people who are interested
in the internals to follow along and poke around in the repository
themselves.
Many thanks to V for initial feedback and motivation for this change.
|
|
These were here because the argument used to contain a glob, like so:
--notes='signatures/*'
Thanks to V for reporting this.
|
|
Commit 751da2c (posts: Update posts to reflect usage of cgit's signature
mechanism, 2021-05-06) updated the project pages as well as "Verifying
snapshots with signify" with information regarding the new cgit
signature mechanism, but neglected to mention that signatures can be
obtained directly through git.oriole.systems as well (the project pages
merely deeplink to that).
Furthermore, with commit 28c2473 (posts: Add a new post: "Hosting
signify signatures on cgit", 2021-05-16) we now have an explanatory
piece which we can link if people are interested in the underlying
infrastructure.
|
|
|
|
|
|
|
|
|
|
|
|
Let's hope that bug is fixed in the next 10 years!
|
|
|
|
cgit can host detached signatures using git-notes(1). Since we want to
make use of that going forward and have finally gotten around to setting
it up fully, we need to make some small changes to
verify-with-signify.md and the weltschmerz project page.
Specifically, we no longer host both the signature and the checksum
(since this would be too cumbersome to maintain with cgit), rendering
the choice explained in the post moot. Since the detached signature has
always contained the checksum, however, we can just fall back to a
slightly different invocation for verifying it.
|
|
|
|
|
|
|
|
Caddy supports implied file extensions in 1.0 via the 'ext' directive,
and in 2.0 via the 'try_files' directive. This feature has been enabled
in the upstream web server for quite a while now, but the links were
never updated to be cleaner.
|
|
|
|
These were skipped because the round borders would not be visible on a
white background. Now - with a dark colour scheme - they are, so make
them round.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
In light of the addition of the author metadata tag to <head>, we
decided to use our full name in the post tags.
|
|
|
|
Since my changes to the project got merged, and this link was always
pointing to master, the issue was not actually visible anymore. Fix this
by using a permalink to the code range from before the fix.
|
|
|
|
|
|
|
|
|