| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Also I need more repos...
|
|
|
|
Publicity is marked by the presences of the git-daemon-export-ok file.
|
|
|
|
This way I can develop on nixpkgs directly, and directly send patches upstream,
instead of trying to copy files back and forth and work with overlays.
Of course with private stuff that I will never publish, I should use overlays,
but that will probably not be very many things, I imagine.
|
|
|
|
Also adds a post-receive script that creates and publishes a git-archive of the
repo at that commit. This way I can depend on my own nixpkgs fork.
It took me forever but I finally figured out that I need --prefix in the git
archive. I also switched to using gzip instead of xz because its faster, and I
figured out how to get the sha256 that nix expects, so I can now just copy that
and paste it into Biz/Bild/Sources.json.
|
|
|
|
|
|
Don't exit on no-such-variable because we can just silently fail...
|
|
The correct way to do this would be to use my own nixpkgs fork published
at git.simatime.com, but to do that I need to setup a public git repo,
so until then I have to do it this way, which is fine.
|
|
I also upstreamed this to nixpkgs-dev
|
|
|
|
|
|
This allows us to use nix-build as a check that bild is working.
I think bild sometimes hangs because it doesn't get input from nix-build? I'm
not sure, but one workaround is to run nix-build on the target, and then bild
will just get the cached build.
|
|
|
|
|
|
|
|
|
|
|
|
My router's DNS service likes to die, then I can't lookup any names, so let's
just use the public ones.
|
|
|
|
|
|
Hopefully this will keep the service online, even if it drops connection with
the client or something occasionally.
|
|
|
|
|
|
The right way to show number of hotspots would be to find files in which commit
frequency is more than like 1 standard deviation from the norm.
I could even show a histogram instead of a flame graph...
|
|
This might not be very robust, but it works for now.
|
|
No build should take longer than 5 minutes; if it does then something is wrong
so let's just die and start over.
|
|
|
|
|
|
I think I should change the colors a bit... to be done later I suppose.
|
|
|
|
The strategy is to clone over https with the OAuth token:
git clone https://<user>:<oauth-token>@github.com/<user>/<repo>
|
|
|
|
|
|
Eventually I'll just upstream these to nixpkgs-dev. I also want to make z into a
gemini-compatible zettlekasten. All in due time.
|
|
|
|
This way I can attach page-specific CSS to the type for the page. I could make
this even tighter by combining HasCss with the HTML declaration, but that would
basically just be Lucid.ToHtml, so I'm not sure it is worth it.
|
|
|
|
Since we don't use a JavaScript frontend, we don't actually need any XSRF
protection. All of the requests will be coming from the browser, not from a
computer running inside the browser (js).
|
|
The design kinda sucks, but I will refresh it later. I just want to get this
shipped right now.
|
|
|
|
|
|
Perhaps this is not as performant as the wai-provided one, but it is *much*
simpler and follows my output format, which I think is much easier to quickly
read. Anyway I doubt logging will ever be a bottleneck, and if it is then I
should be able to create some instrument to detect that.
|
|
|
|
It would be good to have this as a general logging config, but I'm not sure how
to do that. I probably need a logging monad or something.
|
|
|
