Neat!
I think the “classic” darcs way to handle what’s in the static site would be to use a full branch (repo) for that and actual darcs push to it.
I think a “unique” darcs way to handle it would be give it a list of two or more repos (branches) and let darcs compute the intersection of those branches in the static site build.
I used to have Python app (django app) that so heavily used static caches it probably should have been a static site generator. Maybe I should dig it out of storage and see if had any good ideas to pass along. (Though my recollection is that most of its good ideas were never actually implemented.)
Sent from my wireless telegraph. Full stop.
From: darcs-users <darcs-users-boun...@lists.darcs.net> on behalf of Tucker McKnight <tucker.mckni...@gmail.com>
Sent: Thursday, March 27, 2025 03:14
To: darcs-users@lists.darcs.net <darcs-users@lists.darcs.net>
Subject: [darcs-users] A static site repo viewer
Sent: Thursday, March 27, 2025 03:14
To: darcs-users@lists.darcs.net <darcs-users@lists.darcs.net>
Subject: [darcs-users] A static site repo viewer
Hi! Darcs newbie here. I've been enjoying learning about it.
I spent some time over the weekend working on a static site generator for displaying a darcs repository. It's very basic at the moment, but it does work, allowing you to browse files, view patches, clone, and pull a specific patch.
Since I only learned about darcs recently, I have a question about how a typical darcs user would "push" their work to a static website.
If you were working on multiple changes locally and only wanted one of those changes to show up on your website, how would you want to do that? I know that with "darcs push" you can specify which patch(es) you want to push. But in this case, with a static website, you aren't actually pushing to a remote repository. The idea here is that the plain HTML pages are generated locally on your computer, and then you copy those HTML pages to your web server. Would it make sense to have a config file where you list specific tags and patches that should show up on the site, with a default option of showing all available patches? That doesn't seem all that different from typing "darcs push" to either send all patches or send some specific ones. But maybe there is a more darcs-y way of doing this that I'm not familiar with.
Some other notes:
- It works on the darcs.net repository.
- It takes about a minute (on my computer, at least) to generate the site for darcs.net.
- The full output of "darcs log --verbose" alone is 87 megabytes.
- The resulting HTML pages are 300+ megabytes.
I plan to add features to this over the next few weekends. Would love to hear any suggestions people have!
-Tucker
_______________________________________________ darcs-users mailing list darcs-users@lists.darcs.net https://lists.darcs.net/mailman/listinfo/darcs-users
