Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Deleting this code feels strange. This project has been around for a
decade, and despite occasionally needing a bunch of tweaks it had aged
well and worked fine for a very long time.
I've reached a strange point where I don't really feel like using
Haskell anymore, and every interaction with this project in recent
years has been fighting dependency management tooling for Haskell, or
dealing with strange build problems.
The simple fact is that the service never really did anything other
than render Markdown dynamically, and at this point I can do that much
better with //tools/cheddar instead.
So, tazblog-hs, it's time to say goodbye. Rest in peace!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Adds the actual insertion of entries into the homepage, subtly
colour-coding different types of entries.
|
|
Shuffles around the nginx locations that are served to ensure that all
static content will be served from tazj.in/static (including for the
blog).
|
|
Adds the Jetbrains Mono font and the WIP CSS file for the homepage
and (soon) the blog.
|
|
This is not yet fully functional, but going in the right direction.
Some concepts are introduced:
* There is a light theme (used for blog entry pages) and a dark
theme (used for the homepage itself)
* Entries can be either blog posts, projects or miscellaneous things
that I want to link people to (possibly with a comment)
It might be interesting to add pages that filter to specific types, or
some such, which should be relatively easy to do.
Note that the layouts of entries are not actually done yet.
|
|
The homepage is going to be the landing page for all content, whether
it be blog posts or other stuff.
|
|
This lets me easily create an ordered list of entries if the homepage
is designed to list both blog posts and other content.
|
|
|
|
This introduces a derivation which builds an instance of nginx
statically serving my blog posts, though as of now no indexes are
being generated and no XML feed is available.
This is just the initial draft of this setup and not yet what shall be
yielded in the end.
|
|
|
|
|
|
The URLs served on the /about page are relative to the path's dirname,
which is tree/nix not tree/nix/yants.
|
|
|
|
This version of EXWM fixes some issues with binding keys in EXWM as
well as other minor annoyances.
|
|
|
|
It now has vterm-mode support, which has finally convinced me to try it.
|
|
|
|
unix-opts, imported into buildLisp.nix in the previous commit,
provides an implementation independent way of parsing command line
arguments.
|
|
|
|
|
|
The fact that this works is just an implementation-specific detail. In
theory, 'eq' will only compare object instance equality and not value.
Thanks to /u/patrec from HN for pointing this out.
|
|
|
|
|
|
Prompted by this thread:
https://lobste.rs/s/zntyeq/wc_d_712_characters_without_single_branch
|
|
This is mostly equivalent to the Haskell implementation, with the
primary difference that the Lisp DNS library does not support caching
yet.
|
|
|
|
|
|
|
|
|
|
|
|
Deprecates derivations for:
* sb-bsd-sockets
* sb-posix
* sb-rotate-byte
* uiop
|
|
Makes it possible to add virtual dependencies on built-in libraries,
e.g. `buildLisp.bundled "sb-posix"`.
|
|
|
|
|
|
|
|
Adds some of the most common DNS types in the enum (others TBD), and
starts decoding RDATA for TXT and A.
|
|
|
|
This enables arbitrary DNS lookups (with the caveat that RRDATAs are
currently not deserialised into a record-type-specific format).
An error condition has been defined for error-responses from the HTTP
server which provides interactive restarts for attempting a new call
with different parameters.
|
|
|
|
Implements support for the compresion scheme used in binary DNS
messages.
This makes it possible to decode messages entirely, but not yet
actually resolve the labels to their "real" values.
All qnames are stored with file-offsets pointing at the position at
which their reading started, which enables the implementation of a
function to resolve pointers internally.
|
|
Adds a struct that represents QNAMEs, tracks the stream offset at
which the QNAME parsing began and makes it possible to resolve
pointers inside of the QNAME.
Note that resolving pointers needs to happen *after* the call to
lisp-binary currently. It might be possible to implement this inside
of lisp-binary in the future by switching on the top two bits of the
qname field, but since this is happening *inside* of a reader function
I'm not currently sure how to implement it.
|
|
This uses lisp-binary to define serialisation types for the DNS
messages defined by RFC 1035.
Currently the compression scheme used for QNAMEs is not supported,
hence deserialisation of even simple records fails after the header
and question sections are read.
|